User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 4 min ago. Last stored result reached it in 197 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 146 ms | 0 |
| Tue 00 | 0 | 0.0 | 197 ms | 0 |
| Tue 02 | 0 | 0.0 | 207 ms | 0 |
| Tue 04 | 0 | 0.0 | 182 ms | 0 |
| Tue 06 | 0 | 0.0 | 253 ms | 0 |
| Tue 08 | 0 | 0.0 | 212 ms | 0 |
| Tue 11 | 0 | 0.0 | 184 ms | 0 |
| Tue 13 | 0 | 0.0 | 103 ms | 0 |
| Tue 15 | 0 | 0.0 | 364 ms | 0 |
| Tue 17 | 0 | 0.0 | 175 ms | 0 |
| Tue 20 | 0 | 0.0 | 76 ms | 0 |
| Tue 22 | 0 | 0.0 | 118 ms | 0 |
| Wed 00 | 0 | 0.0 | 296 ms | 0 |
| Wed 02 | 0 | 0.0 | 231 ms | 0 |
| Wed 05 | 0 | 0.0 | 196 ms | 0 |
| Wed 07 | 0 | 0.0 | 151 ms | 0 |
| Wed 09 | 0 | 0.0 | 262 ms | 0 |
| Wed 11 | 0 | 0.0 | 284 ms | 0 |
| Wed 13 | 0 | 0.0 | 119 ms | 0 |
| Wed 15 | 0 | 0.0 | 77 ms | 0 |
| Wed 18 | 0 | 0.0 | 229 ms | 0 |
| Wed 20 | 0 | 0.0 | 133 ms | 0 |
| Wed 22 | 0 | 0.0 | 126 ms | 0 |
| Thu 00 | 0 | 0.0 | 147 ms | 0 |
| Thu 02 | 0 | 0.0 | 199 ms | 0 |
| Thu 05 | 0 | 0.0 | 226 ms | 0 |
| Thu 07 | 0 | 0.0 | 118 ms | 0 |
| Thu 09 | 0 | 0.0 | 106 ms | 0 |
| Thu 11 | 0 | 0.0 | 223 ms | 0 |
| Thu 13 | 0 | 0.0 | 57 ms | 0 |
| Thu 15 | 0 | 0.0 | 272 ms | 0 |
| Thu 17 | 0 | 0.0 | 189 ms | 0 |
| Thu 19 | 0 | 0.0 | 237 ms | 0 |
| Thu 21 | 0 | 0.0 | 242 ms | 0 |
| Thu 23 | 0 | 0.0 | 78 ms | 0 |
| Fri 01 | 0 | 0.0 | 241 ms | 0 |
| Fri 03 | 0 | 0.0 | 213 ms | 0 |
| Fri 05 | 0 | 0.0 | 220 ms | 0 |
| Fri 06 | 0 | 0.0 | 177 ms | 0 |
| Fri 08 | 0 | 0.0 | 103 ms | 0 |
| Fri 10 | 0 | 0.0 | 274 ms | 0 |
| Fri 11 | 0 | 0.0 | 163 ms | 0 |
| Fri 13 | 0 | 0.0 | 262 ms | 0 |
| Fri 15 | 0 | 0.0 | 235 ms | 0 |
| Fri 17 | 0 | 0.0 | 185 ms | 0 |
| Fri 18 | 0 | 0.0 | 246 ms | 0 |
| Fri 20 | 0 | 0.0 | 180 ms | 0 |
| Fri 21 | 0 | 0.0 | 197 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Zoo 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 Zoo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Zoo alerts to Slack, Discord or a webhook — free.
Zoo is listed in our Productivity category and checked at zoo.dev. Zoo creates infrastructure for hardware design. We're laying the foundation for a modern hardware design toolkit, so that you can create new design tools never before possible.
Zoo publishes an official status page at status.zoo.dev; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 198 ms average, 78–274 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Zoo incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
198 ms on average over the last 24 hours (78–274 ms).
Yes, at https://status.zoo.dev.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Zoo here at once, the problem is on Zoo'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 Zoo. 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.