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 2 hr ago. Last stored result reached it in 499 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 681 ms | 0 |
| Tue 00 | 0 | 0.0 | 439 ms | 0 |
| Tue 02 | 0 | 0.0 | 382 ms | 0 |
| Tue 04 | 0 | 0.0 | 738 ms | 0 |
| Tue 06 | 0 | 0.0 | 474 ms | 0 |
| Tue 08 | 0 | 0.0 | 541 ms | 0 |
| Tue 10 | 0 | 0.0 | 333 ms | 0 |
| Tue 12 | 0 | 0.0 | 453 ms | 0 |
| Tue 14 | 0 | 0.0 | 688 ms | 0 |
| Tue 17 | 0 | 0.0 | 614 ms | 0 |
| Tue 19 | 0 | 0.0 | 657 ms | 0 |
| Tue 21 | 0 | 0.0 | 76 ms | 0 |
| Tue 23 | 0 | 0.0 | 502 ms | 0 |
| Wed 02 | 0 | 0.0 | 1023 ms | 0 |
| Wed 04 | 0 | 0.0 | 333 ms | 0 |
| Wed 06 | 0 | 0.0 | 518 ms | 0 |
| Wed 08 | 0 | 0.0 | 426 ms | 0 |
| Wed 11 | 0 | 0.0 | 352 ms | 0 |
| Wed 13 | 0 | 0.0 | 627 ms | 0 |
| Wed 15 | 0 | 0.0 | 381 ms | 0 |
| Wed 17 | 0 | 0.0 | 387 ms | 0 |
| Wed 19 | 0 | 0.0 | 407 ms | 0 |
| Wed 21 | 0 | 0.0 | 116 ms | 0 |
| Wed 23 | 0 | 0.0 | 740 ms | 0 |
| Thu 02 | 0 | 0.0 | 490 ms | 0 |
| Thu 04 | 0 | 0.0 | 289 ms | 0 |
| Thu 06 | 0 | 0.0 | 477 ms | 0 |
| Thu 08 | 0 | 0.0 | 423 ms | 0 |
| Thu 10 | 0 | 0.0 | 549 ms | 0 |
| Thu 12 | 0 | 0.0 | 716 ms | 0 |
| Thu 14 | 0 | 0.0 | 664 ms | 0 |
| Thu 16 | 0 | 0.0 | 712 ms | 0 |
| Thu 18 | 0 | 0.0 | 406 ms | 0 |
| Thu 20 | 0 | 0.0 | 119 ms | 0 |
| Thu 22 | 0 | 0.0 | 831 ms | 0 |
| Fri 00 | 0 | 0.0 | 95 ms | 0 |
| Fri 02 | 0 | 0.0 | 410 ms | 0 |
| Fri 04 | 0 | 0.0 | 450 ms | 0 |
| Fri 06 | 0 | 0.0 | 626 ms | 0 |
| Fri 07 | 0 | 0.0 | 911 ms | 0 |
| Fri 09 | 0 | 0.0 | 529 ms | 0 |
| Fri 11 | 0 | 0.0 | 346 ms | 0 |
| Fri 13 | 0 | 0.0 | 61 ms | 0 |
| Fri 15 | 0 | 0.0 | 626 ms | 0 |
| Fri 17 | 0 | 0.0 | 147 ms | 0 |
| Fri 19 | 0 | 0.0 | 509 ms | 0 |
| Fri 21 | 0 | 0.0 | 622 ms | 0 |
| Fri 22 | 0 | 0.0 | 499 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 Antioch 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 Antioch goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Antioch alerts to Slack, Discord or a webhook — free.
We track Antioch (antioch.com) as part of the AI group. High-fidelity simulation for Physical AI, at cloud scale. Join teams using Antioch to ship autonomous systems with confidence, entirely in simulation.
Antioch publishes an official status page at status.antioch.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 437 ms average, 61–923 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Antioch incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
437 ms on average over the last 24 hours (61–923 ms).
Yes, at https://status.antioch.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 Antioch here at once, the problem is on Antioch'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 Antioch. 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.