User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 1 hr ago. Last stored result reached it in 151 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 03 | 0 | 0.0 | 427 ms | 0 |
| Mon 05 | 0 | 0.0 | 362 ms | 0 |
| Mon 07 | 0 | 0.0 | 191 ms | 0 |
| Mon 09 | 0 | 0.0 | 381 ms | 0 |
| Mon 11 | 0 | 0.0 | 266 ms | 0 |
| Mon 13 | 0 | 0.0 | 456 ms | 0 |
| Mon 15 | 0 | 0.0 | 422 ms | 0 |
| Mon 17 | 0 | 0.0 | 401 ms | 0 |
| Mon 19 | 0 | 0.0 | 376 ms | 0 |
| Mon 22 | 0 | 0.0 | 450 ms | 0 |
| Tue 00 | 0 | 0.0 | 269 ms | 0 |
| Tue 02 | 0 | 0.0 | 267 ms | 0 |
| Tue 04 | 0 | 0.0 | 358 ms | 0 |
| Tue 06 | 0 | 0.0 | 384 ms | 0 |
| Tue 08 | 0 | 0.0 | 174 ms | 0 |
| Tue 10 | 0 | 0.0 | 407 ms | 0 |
| Tue 12 | 0 | 0.0 | 404 ms | 0 |
| Tue 14 | 0 | 0.0 | 373 ms | 0 |
| Tue 17 | 0 | 0.0 | 228 ms | 0 |
| Tue 19 | 0 | 0.0 | 192 ms | 0 |
| Tue 21 | 0 | 0.0 | 287 ms | 0 |
| Wed 00 | 0 | 0.0 | 215 ms | 0 |
| Wed 02 | 0 | 0.0 | 501 ms | 0 |
| Wed 04 | 0 | 0.0 | 191 ms | 0 |
| Wed 06 | 0 | 0.0 | 192 ms | 0 |
| Wed 08 | 0 | 0.0 | 354 ms | 0 |
| Wed 11 | 0 | 0.0 | 209 ms | 0 |
| Wed 13 | 0 | 0.0 | 171 ms | 0 |
| Wed 15 | 0 | 0.0 | 375 ms | 0 |
| Wed 17 | 0 | 0.0 | 370 ms | 0 |
| Wed 19 | 0 | 0.0 | 133 ms | 0 |
| Wed 21 | 0 | 0.0 | 387 ms | 0 |
| Thu 00 | 0 | 0.0 | 384 ms | 0 |
| Thu 02 | 0 | 0.0 | 201 ms | 0 |
| Thu 04 | 0 | 0.0 | 308 ms | 0 |
| Thu 06 | 0 | 0.0 | 468 ms | 0 |
| Thu 08 | 0 | 0.0 | 122 ms | 0 |
| Thu 10 | 0 | 0.0 | 194 ms | 0 |
| Thu 12 | 0 | 0.0 | 369 ms | 0 |
| Thu 14 | 0 | 0.0 | 374 ms | 0 |
| Thu 16 | 0 | 0.0 | 386 ms | 0 |
| Thu 18 | 0 | 0.0 | 405 ms | 0 |
| Thu 20 | 0 | 0.0 | 372 ms | 0 |
| Thu 22 | 0 | 0.0 | 379 ms | 0 |
| Fri 00 | 0 | 0.0 | 202 ms | 0 |
| Fri 02 | 0 | 0.0 | 170 ms | 0 |
| Fri 04 | 0 | 0.0 | 371 ms | 0 |
| Fri 06 | 0 | 0.0 | 151 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 CloudZero 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 CloudZero goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send CloudZero alerts to Slack, Discord or a webhook — free.
We track CloudZero (cloudzero.com) as part of the AI group. CloudZero is the AI ROI Company. AI Signals & multi-dimensional allocation tie every AI dollar to the customer, product & outcome it drives.
CloudZero publishes an official status page at status.cloudzero.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 297 ms average, 122–453 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public CloudZero incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
297 ms on average over the last 24 hours (122–453 ms).
Yes, at https://status.cloudzero.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report CloudZero here at once, the problem is on CloudZero'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 CloudZero. 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.