User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 18 min ago. Last stored result reached it in 495 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 484 ms | 0 |
| Nov 7 | 0 | 0.0 | 440 ms | 0 |
| Nov 7 | 0 | 0.0 | 484 ms | 0 |
| Nov 7 | 0 | 0.0 | 470 ms | 0 |
| Nov 8 | 0 | 0.0 | 467 ms | 0 |
| Nov 8 | 0 | 0.0 | 478 ms | 0 |
| Nov 8 | 0 | 0.0 | 463 ms | 0 |
| Nov 8 | 0 | 0.0 | 499 ms | 0 |
| Nov 9 | 0 | 0.0 | 543 ms | 0 |
| Nov 9 | 0 | 0.0 | 441 ms | 0 |
| Nov 9 | 0 | 0.0 | 473 ms | 0 |
| Nov 9 | 0 | 0.0 | 469 ms | 0 |
| Nov 10 | 0 | 0.0 | 472 ms | 0 |
| Nov 10 | 0 | 0.0 | 456 ms | 0 |
| Nov 10 | 0 | 0.0 | 502 ms | 0 |
| Nov 10 | 0 | 0.0 | 437 ms | 0 |
| Nov 11 | 0 | 0.0 | 495 ms | 0 |
| Nov 11 | 0 | 0.0 | 415 ms | 0 |
| Nov 11 | 0 | 0.0 | 512 ms | 0 |
| Nov 11 | 0 | 0.0 | 476 ms | 0 |
| Nov 12 | 0 | 0.0 | 521 ms | 0 |
| Nov 12 | 0 | 0.0 | 497 ms | 0 |
| Nov 12 | 0 | 0.0 | 410 ms | 0 |
| Nov 12 | 0 | 0.0 | 512 ms | 0 |
| Nov 13 | 0 | 0.0 | 474 ms | 0 |
| Nov 13 | 0 | 0.0 | 450 ms | 0 |
| Nov 13 | 0 | 0.0 | 473 ms | 0 |
| Nov 13 | 0 | 0.0 | 491 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for put.io yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when put.io goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send put.io alerts to Slack, Discord or a webhook — free.
put.io, at put.io, is one of the Cloud & developer services we monitor. put.io fetches files from the web to your own storage in seconds, then streams them anywhere. Fast, private, since 2009.
put.io publishes an official status page at status.put.io; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 480 ms average, 438–591 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public put.io incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
480 ms on average over the last 24 hours (438–591 ms).
Yes, at https://status.put.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report put.io here at once, the problem is on put.io's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with put.io. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.