Exa Outage History
7 incidents recorded over the last 365 days, 7 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Exa Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 21, 2026 | Elevated failures affecting Agent runs | 5h 0m | Resolved |
| Sep 21, 2026 | Search API is down | 3 min | Resolved |
| Sep 21, 2026 | Search API is down | 18 min | Resolved |
| Sep 21, 2026 | Elevated latencies across search endpoints causing some requests to fail | 4h 14m | Resolved |
| Sep 18, 2026 | We are investigating a latency degradation affecting Search endpoints | 2h 31m | Resolved |
| Sep 14, 2026 | Search API is down | 24 min | Resolved |
| Aug 25, 2026 | Elevated latency in the /search endpoint | 1h 10m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Exa incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Exa Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Exa acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Exa outage in this window ran 5h, against a mean recovery of 1h 57m. If you depend on Exa in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.