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 52 min ago. Last stored result reached it in 72 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 334 ms | 0 |
| Mon 18 | 0 | 0.0 | 176 ms | 0 |
| Mon 20 | 0 | 0.0 | 149 ms | 0 |
| Mon 22 | 0 | 0.0 | 271 ms | 0 |
| Tue 00 | 0 | 0.0 | 341 ms | 0 |
| Tue 02 | 0 | 0.0 | 136 ms | 0 |
| Tue 05 | 0 | 0.0 | 242 ms | 0 |
| Tue 07 | 0 | 0.0 | 281 ms | 0 |
| Tue 09 | 0 | 0.0 | 137 ms | 0 |
| Tue 11 | 0 | 0.0 | 122 ms | 0 |
| Tue 13 | 0 | 0.0 | 324 ms | 0 |
| Tue 15 | 0 | 0.0 | 165 ms | 0 |
| Tue 18 | 0 | 0.0 | 578 ms | 0 |
| Tue 20 | 0 | 0.0 | 229 ms | 0 |
| Tue 22 | 0 | 0.0 | 215 ms | 0 |
| Wed 00 | 0 | 0.0 | 222 ms | 0 |
| Wed 03 | 0 | 0.0 | 168 ms | 0 |
| Wed 05 | 0 | 0.0 | 220 ms | 0 |
| Wed 07 | 0 | 0.0 | 156 ms | 0 |
| Wed 09 | 0 | 0.0 | 186 ms | 0 |
| Wed 12 | 0 | 0.0 | 119 ms | 0 |
| Wed 14 | 0 | 0.0 | 117 ms | 0 |
| Wed 16 | 0 | 0.0 | 244 ms | 0 |
| Wed 18 | 0 | 0.0 | 167 ms | 0 |
| Wed 20 | 0 | 0.0 | 402 ms | 0 |
| Wed 22 | 0 | 0.0 | 154 ms | 0 |
| Thu 01 | 0 | 0.0 | 200 ms | 0 |
| Thu 03 | 0 | 0.0 | 179 ms | 0 |
| Thu 05 | 0 | 0.0 | 206 ms | 0 |
| Thu 06 | 0 | 0.0 | 241 ms | 0 |
| Thu 08 | 0 | 0.0 | 288 ms | 0 |
| Thu 10 | 0 | 0.0 | 311 ms | 0 |
| Thu 12 | 0 | 0.0 | 161 ms | 0 |
| Thu 14 | 0 | 0.0 | 304 ms | 0 |
| Thu 16 | 0 | 0.0 | 183 ms | 0 |
| Thu 18 | 0 | 0.0 | 278 ms | 0 |
| Thu 20 | 0 | 0.0 | 277 ms | 0 |
| Thu 22 | 0 | 0.0 | 82 ms | 0 |
| Fri 00 | 0 | 0.0 | 156 ms | 0 |
| Fri 02 | 0 | 0.0 | 108 ms | 0 |
| Fri 04 | 0 | 0.0 | 103 ms | 0 |
| Fri 06 | 0 | 0.0 | 179 ms | 0 |
| Fri 08 | 0 | 0.0 | 84 ms | 0 |
| Fri 10 | 0 | 0.0 | 110 ms | 0 |
| Fri 11 | 0 | 0.0 | 48 ms | 0 |
| Fri 13 | 0 | 0.0 | 115 ms | 0 |
| Fri 15 | 0 | 0.0 | 127 ms | 0 |
| Fri 17 | 0 | 0.0 | 72 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 Exa 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 Exa goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Exa alerts to Slack, Discord or a webhook — free.
We track Exa (exa.ai) as part of the AI group. Search API for AI agents that need real-time web data, deep research, and structured content from one endpoint. Try our API for free.
Exa publishes an official status page at status.exa.ai; 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: 135 ms average, 48–278 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 Exa incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
135 ms on average over the last 24 hours (48–278 ms).
Yes, at https://status.exa.ai.
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 Exa here at once, the problem is on Exa'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 Exa. 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.