User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
maze.co · AI
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 449 ms · 4 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 622 ms | 0 |
| 08:15 | 0 | 0.0 | 352 ms | 0 |
| 08:30 | 0 | 0.0 | 277 ms | 0 |
| 08:45 | 0 | 0.0 | 307 ms | 0 |
| 09:00 | 0 | 0.0 | 397 ms | 0 |
| 09:15 | 0 | 0.0 | 309 ms | 0 |
| 09:30 | 0 | 0.0 | 747 ms | 0 |
| 09:45 | 0 | 0.0 | 1039 ms | 0 |
| 10:00 | 0 | 0.0 | 891 ms | 0 |
| 10:15 | 0 | 0.0 | 603 ms | 0 |
| 10:30 | 0 | 0.0 | 724 ms | 0 |
| 10:45 | 0 | 0.0 | 1016 ms | 0 |
| 11:00 | 0 | 0.0 | 216 ms | 0 |
| 11:15 | 0 | 0.0 | 278 ms | 0 |
| 11:30 | 0 | 0.0 | 274 ms | 0 |
| 11:45 | 0 | 0.0 | 639 ms | 0 |
| 12:00 | 0 | 0.0 | 410 ms | 0 |
| 12:15 | 0 | 0.0 | 597 ms | 0 |
| 12:30 | 0 | 0.0 | 953 ms | 0 |
| 12:45 | 0 | 0.0 | 234 ms | 0 |
| 13:00 | 0 | 0.0 | 339 ms | 0 |
| 13:15 | 0 | 0.0 | 621 ms | 0 |
| 13:30 | 0 | 0.0 | 448 ms | 0 |
| 13:45 | 0 | 0.0 | 919 ms | 0 |
| 14:00 | 0 | 0.0 | 445 ms | 0 |
| 14:15 | 0 | 0.0 | 1163 ms | 0 |
| 14:30 | 0 | 0.0 | 409 ms | 0 |
| 14:45 | 0 | 0.0 | 317 ms | 0 |
| 15:00 | 0 | 0.0 | 714 ms | 0 |
| 15:15 | 0 | 0.0 | 1135 ms | 0 |
| 15:30 | 0 | 0.0 | 434 ms | 0 |
| 15:45 | 0 | 0.0 | 568 ms | 0 |
| 16:00 | 0 | 0.0 | 910 ms | 0 |
| 16:15 | 0 | 0.0 | 626 ms | 0 |
| 16:30 | 0 | 0.0 | 446 ms | 0 |
| 16:45 | 0 | 0.0 | 572 ms | 0 |
| 17:00 | 0 | 0.0 | 798 ms | 0 |
| 17:15 | 0 | 0.0 | 725 ms | 0 |
| 17:30 | 0 | 0.0 | 406 ms | 0 |
| 17:45 | 0 | 0.0 | 414 ms | 0 |
| 18:00 | 0 | 0.0 | 753 ms | 0 |
| 18:15 | 0 | 0.0 | 391 ms | 0 |
| 18:30 | 0 | 0.0 | 323 ms | 0 |
| 18:45 | 0 | 0.0 | 579 ms | 0 |
| 19:00 | 0 | 0.0 | 471 ms | 0 |
| 19:15 | 0 | 0.0 | 1095 ms | 0 |
| 19:30 | 0 | 0.0 | 321 ms | 0 |
| 19:45 | 0 | 0.0 | 449 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 Maze 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 Maze goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Maze 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 Maze 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 Maze'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.