User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
zenduty.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 105 ms · 6 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 1186 ms | 0 |
| 03:15 | 0 | 0.0 | 342 ms | 0 |
| 03:30 | 0 | 0.0 | 490 ms | 0 |
| 03:45 | 0 | 0.0 | 107 ms | 0 |
| 04:00 | 0 | 0.0 | 1233 ms | 0 |
| 04:15 | 0 | 0.0 | 870 ms | 0 |
| 04:30 | 0 | 0.0 | 183 ms | 0 |
| 04:45 | 0 | 0.0 | 493 ms | 0 |
| 05:00 | 0 | 0.0 | 402 ms | 0 |
| 05:15 | 0 | 0.0 | 592 ms | 0 |
| 05:30 | 0 | 0.0 | 969 ms | 0 |
| 05:45 | 0 | 0.0 | 600 ms | 0 |
| 06:00 | 0 | 0.0 | 597 ms | 0 |
| 06:15 | 0 | 0.0 | 480 ms | 0 |
| 06:30 | 0 | 0.0 | 401 ms | 0 |
| 06:45 | 0 | 0.0 | 165 ms | 0 |
| 07:00 | 0 | 0.0 | 1279 ms | 0 |
| 07:15 | 0 | 0.0 | 484 ms | 0 |
| 07:30 | 0 | 0.0 | 1516 ms | 0 |
| 07:45 | 0 | 0.0 | 383 ms | 0 |
| 08:00 | 0 | 0.0 | 969 ms | 0 |
| 08:15 | 0 | 0.0 | 376 ms | 0 |
| 08:30 | 0 | 0.0 | 297 ms | 0 |
| 08:45 | 0 | 0.0 | 866 ms | 0 |
| 09:00 | 0 | 0.0 | 634 ms | 0 |
| 09:15 | 0 | 0.0 | 1546 ms | 0 |
| 09:30 | 0 | 0.0 | 701 ms | 0 |
| 09:45 | 0 | 0.0 | 1155 ms | 0 |
| 10:00 | 0 | 0.0 | 582 ms | 0 |
| 10:15 | 0 | 0.0 | 435 ms | 0 |
| 10:30 | 0 | 0.0 | 155 ms | 0 |
| 10:45 | 0 | 0.0 | 392 ms | 0 |
| 11:00 | 0 | 0.0 | 591 ms | 0 |
| 11:15 | 0 | 0.0 | 1434 ms | 0 |
| 11:30 | 0 | 0.0 | 818 ms | 0 |
| 11:45 | 0 | 0.0 | 1459 ms | 0 |
| 12:00 | 0 | 0.0 | 960 ms | 0 |
| 12:15 | 0 | 0.0 | 174 ms | 0 |
| 12:30 | 0 | 0.0 | 481 ms | 0 |
| 12:45 | 0 | 0.0 | 869 ms | 0 |
| 13:00 | 0 | 0.0 | 470 ms | 0 |
| 13:15 | 0 | 0.0 | 358 ms | 0 |
| 13:30 | 0 | 0.0 | 242 ms | 0 |
| 13:45 | 0 | 0.0 | 105 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Zenduty 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 Zenduty goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zenduty alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Zenduty is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Zenduty's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.