User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is put.io down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → put.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 31 min ago. Last stored result reached it in 486 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 473 ms | 0 |
| Mon 17 | 0 | 0.0 | 548 ms | 0 |
| Mon 19 | 0 | 0.0 | 424 ms | 0 |
| Mon 21 | 0 | 0.0 | 469 ms | 0 |
| Mon 23 | 0 | 0.0 | 476 ms | 0 |
| Tue 01 | 0 | 0.0 | 479 ms | 0 |
| Tue 03 | 0 | 0.0 | 465 ms | 0 |
| Tue 06 | 0 | 0.0 | 456 ms | 0 |
| Tue 08 | 0 | 0.0 | 450 ms | 0 |
| Tue 10 | 0 | 0.0 | 456 ms | 0 |
| Tue 12 | 0 | 0.0 | 550 ms | 0 |
| Tue 14 | 0 | 0.0 | 472 ms | 0 |
| Tue 16 | 0 | 0.0 | 502 ms | 0 |
| Tue 19 | 0 | 0.0 | 437 ms | 0 |
| Tue 21 | 0 | 0.0 | 423 ms | 0 |
| Tue 23 | 0 | 0.0 | 446 ms | 0 |
| Wed 01 | 0 | 0.0 | 486 ms | 0 |
| Wed 04 | 0 | 0.0 | 503 ms | 0 |
| Wed 06 | 0 | 0.0 | 552 ms | 0 |
| Wed 08 | 0 | 0.0 | 368 ms | 0 |
| Wed 10 | 0 | 0.0 | 415 ms | 0 |
| Wed 13 | 0 | 0.0 | 490 ms | 0 |
| Wed 15 | 0 | 0.0 | 512 ms | 0 |
| Wed 17 | 0 | 0.0 | 547 ms | 0 |
| Wed 19 | 0 | 0.0 | 631 ms | 0 |
| Wed 21 | 0 | 0.0 | 476 ms | 0 |
| Wed 23 | 0 | 0.0 | 399 ms | 0 |
| Thu 02 | 0 | 0.0 | 471 ms | 0 |
| Thu 04 | 0 | 0.0 | 570 ms | 0 |
| Thu 06 | 0 | 0.0 | 452 ms | 0 |
| Thu 08 | 0 | 0.0 | 581 ms | 0 |
| Thu 10 | 0 | 0.0 | 497 ms | 0 |
| Thu 12 | 0 | 0.0 | 393 ms | 0 |
| Thu 14 | 0 | 0.0 | 410 ms | 0 |
| Thu 16 | 0 | 0.0 | 479 ms | 0 |
| Thu 18 | 0 | 0.0 | 574 ms | 0 |
| Thu 20 | 0 | 0.0 | 512 ms | 0 |
| Thu 22 | 0 | 0.0 | 438 ms | 0 |
| Fri 00 | 0 | 0.0 | 508 ms | 0 |
| Fri 02 | 0 | 0.0 | 474 ms | 0 |
| Fri 04 | 0 | 0.0 | 450 ms | 0 |
| Fri 06 | 0 | 0.0 | 501 ms | 0 |
| Fri 09 | 0 | 0.0 | 449 ms | 0 |
| Fri 11 | 0 | 0.0 | 450 ms | 0 |
| Fri 13 | 0 | 0.0 | 591 ms | 0 |
| Fri 15 | 0 | 0.0 | 460 ms | 0 |
| Fri 17 | 0 | 0.0 | 473 ms | 0 |
| Fri 19 | 0 | 0.0 | 486 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live put.io badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for put.io yet. Outages of 10 minutes or more get their own page here.
Having trouble with put.io?
One report per service every 10 minutes from this network. No account.
Follow put.io
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.
About put.io
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: 483 ms average, 438–591 ms range across 16 successful checks.
Questions
Is put.io down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was put.io last down?
We have not recorded a public put.io incident since monitoring began 8 days ago.
What is put.io's uptime?
From our own checks: 100% over 8 days of checks.
How fast does put.io respond?
483 ms on average over the last 24 hours (438–591 ms).
Does put.io have an official status page?
Yes, at https://status.put.io.
put.io not working for me but the status is fine. What now?
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.