User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
exact.com · AI
Something is off: the vendor reports a minor incident. Official status: Partially Degraded Service
Estimated fix: Not enough Exact history yet; similar AI outages lasted 18 min (median, typically 9 min–27 min; 10 outages).
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.
Reachable from all 4 regions we check from.
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 184 ms · 4 min ago.
Minor incident
Partially Degraded Service Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 07:00 | 0 | 0.0 | 598 ms | 0 |
| 07:15 | 0 | 0.0 | 421 ms | 0 |
| 07:30 | 0 | 0.0 | 357 ms | 0 |
| 07:45 | 0 | 0.0 | 193 ms | 0 |
| 08:00 | 0 | 0.0 | 1307 ms | 0 |
| 08:15 | 0 | 0.0 | 384 ms | 0 |
| 08:30 | 0 | 0.0 | 438 ms | 0 |
| 08:45 | 0 | 0.0 | 195 ms | 0 |
| 09:00 | 0 | 0.0 | 380 ms | 0 |
| 09:15 | 0 | 0.0 | 440 ms | 0 |
| 09:30 | 0 | 0.0 | 231 ms | 0 |
| 09:45 | 0 | 0.0 | 614 ms | 0 |
| 10:00 | 0 | 0.0 | 528 ms | 0 |
| 10:15 | 0 | 0.0 | 269 ms | 0 |
| 10:30 | 0 | 0.0 | 707 ms | 0 |
| 10:45 | 0 | 0.0 | 577 ms | 0 |
| 11:00 | 0 | 0.0 | 459 ms | 0 |
| 11:15 | 0 | 0.0 | 330 ms | 0 |
| 11:30 | 0 | 0.0 | 425 ms | 0 |
| 11:45 | 0 | 0.0 | — | 0 |
| 12:00 | 0 | 0.0 | 312 ms | 0 |
| 12:15 | 0 | 0.0 | 723 ms | 0 |
| 12:30 | 0 | 0.0 | 43 ms | 0 |
| 12:45 | 0 | 0.0 | 315 ms | 0 |
| 13:00 | 0 | 0.0 | 819 ms | 0 |
| 13:15 | 0 | 0.0 | 375 ms | 0 |
| 13:30 | 0 | 0.0 | 954 ms | 0 |
| 13:45 | 0 | 0.0 | 380 ms | 0 |
| 14:00 | 0 | 0.0 | 72 ms | 0 |
| 14:15 | 0 | 0.0 | 584 ms | 0 |
| 14:30 | 0 | 0.0 | 514 ms | 0 |
| 14:45 | 0 | 0.0 | 540 ms | 0 |
| 15:00 | 0 | 0.0 | 287 ms | 0 |
| 15:15 | 0 | 0.0 | 539 ms | 0 |
| 15:30 | 0 | 0.0 | 826 ms | 0 |
| 15:45 | 0 | 0.0 | 995 ms | 0 |
| 16:00 | 0 | 0.0 | 805 ms | 0 |
| 16:15 | 0 | 0.0 | 361 ms | 0 |
| 16:30 | 0 | 0.0 | 436 ms | 0 |
| 16:45 | 0 | 0.0 | 546 ms | 0 |
| 17:00 | 0 | 0.0 | 54 ms | 0 |
| 17:15 | 0 | 0.0 | 427 ms | 0 |
| 17:30 | 0 | 0.0 | 636 ms | 0 |
| 17:45 | 0 | 0.0 | 477 ms | 0 |
| 18:00 | 0 | 0.0 | 474 ms | 0 |
| 18:15 | 0 | 0.0 | 777 ms | 0 |
| 18:30 | 0 | 0.0 | 531 ms | 0 |
| 18:45 | 0 | 0.0 | 333 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 Exact 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 Exact goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Exact alerts to Slack, Discord or a webhook — free.
Something is off: the vendor reports a minor incident. Official status: Partially Degraded Service
If Exact 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 Exact'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.