User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
ada.support · AI
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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.
Not enough checks
Last check reached it in 190 ms · 7 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 286 ms | 0 |
| 03:15 | 0 | 0.0 | 322 ms | 0 |
| 03:30 | 0 | 0.0 | 634 ms | 0 |
| 03:45 | 0 | 0.0 | 316 ms | 0 |
| 04:00 | 0 | 0.0 | 600 ms | 0 |
| 04:15 | 0 | 0.0 | 135 ms | 0 |
| 04:30 | 0 | 0.0 | 502 ms | 0 |
| 04:45 | 0 | 0.0 | 605 ms | 0 |
| 05:00 | 0 | 0.0 | 105 ms | 0 |
| 05:15 | 0 | 0.0 | 270 ms | 0 |
| 05:30 | 0 | 0.0 | 610 ms | 0 |
| 05:45 | 0 | 0.0 | 655 ms | 0 |
| 06:00 | 0 | 0.0 | 368 ms | 0 |
| 06:15 | 0 | 0.0 | 83 ms | 0 |
| 06:30 | 0 | 0.0 | 242 ms | 0 |
| 06:45 | 0 | 0.0 | 418 ms | 0 |
| 07:00 | 0 | 0.0 | 532 ms | 0 |
| 07:15 | 0 | 0.0 | 354 ms | 0 |
| 07:30 | 0 | 0.0 | 559 ms | 0 |
| 07:45 | 0 | 0.0 | 787 ms | 0 |
| 08:00 | 0 | 0.0 | 102 ms | 0 |
| 08:15 | 0 | 0.0 | 874 ms | 0 |
| 08:30 | 0 | 0.0 | 339 ms | 0 |
| 08:45 | 0 | 0.0 | 646 ms | 0 |
| 09:00 | 0 | 0.0 | 651 ms | 0 |
| 09:15 | 0 | 0.0 | 118 ms | 0 |
| 09:30 | 0 | 0.0 | 411 ms | 0 |
| 09:45 | 0 | 0.0 | 297 ms | 0 |
| 10:00 | 0 | 0.0 | 970 ms | 0 |
| 10:15 | 0 | 0.0 | 582 ms | 0 |
| 10:30 | 0 | 0.0 | 349 ms | 0 |
| 10:45 | 0 | 0.0 | 430 ms | 0 |
| 11:00 | 0 | 0.0 | 282 ms | 0 |
| 11:15 | 0 | 0.0 | 647 ms | 0 |
| 11:30 | 0 | 0.0 | 373 ms | 0 |
| 11:45 | 0 | 0.0 | 1141 ms | 0 |
| 12:00 | 0 | 0.0 | 807 ms | 0 |
| 12:15 | 0 | 0.0 | 445 ms | 0 |
| 12:30 | 0 | 0.0 | 194 ms | 0 |
| 12:45 | 0 | 0.0 | 424 ms | 0 |
| 13:00 | 0 | 0.0 | 514 ms | 0 |
| 13:15 | 0 | 0.0 | 304 ms | 0 |
| 13:30 | 0 | 0.0 | 631 ms | 0 |
| 13:45 | 0 | 0.0 | 429 ms | 0 |
| 14:00 | 0 | 0.0 | 1146 ms | 0 |
| 14:15 | 0 | 0.0 | 278 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 Ada 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 Ada goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ada alerts to Slack, Discord or a webhook — free.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
If Ada 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 Ada'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.