E
Outage recap · Exa

Exa outage — September 21, 2026

On September 21, 2026, Exa had 6 reported incidents on Exa's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Elevated latencies across search endpoints causing some requests to fail

PARTIALOUTAGE
Started
Sep 21, 8:39 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Exa 24 times in the two hours after Exa's start time (it published no end time), once every five minutes. Every one of them reached Exa's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 93 ms, against 120 ms over the 24 hours before.

Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.

Search API is down

PARTIALOUTAGE
Started
Sep 21, 9:05 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Exa 24 times in the two hours after Exa's start time (it published no end time), once every five minutes. Every one of them reached Exa's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 107 ms, against 120 ms over the 24 hours before. Exa's feed showed the incident by Sep 21, 9:10 AM EDT (we read it every five minutes).

Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.

Search API is down

PARTIALOUTAGE
Started
Sep 21, 9:24 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Exa 24 times in the two hours after Exa's start time (it published no end time), once every five minutes. Every one of them reached Exa's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 104 ms, against 119 ms over the 24 hours before. Exa's feed showed the incident by Sep 21, 9:30 AM EDT (we read it every five minutes).

Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.

Search API is down

PARTIALOUTAGE
Started
Sep 21, 9:27 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Exa 24 times in the two hours after Exa's start time (it published no end time), once every five minutes. Every one of them reached Exa's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 102 ms, against 119 ms over the 24 hours before. Exa's feed showed the incident by Sep 21, 9:35 AM EDT (we read it every five minutes).

Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.

Search API is down

PARTIALOUTAGE
Started
Sep 21, 9:44 AM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Exa 24 times in the two hours after Exa's start time (it published no end time), once every five minutes. Every one of them reached Exa's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 97 ms, against 120 ms over the 24 hours before. Exa's feed showed the incident by Sep 21, 9:50 AM EDT (we read it every five minutes).

Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.

Elevated failures affecting Agent runs

DEGRADEDPERFORMANCE
Started
Sep 21, 6:17 PM EDT
Resolved
—
Duration
end time not published

What our checks recorded

We checked Exa 24 times in the two hours after Exa's start time (it published no end time), once every five minutes. Every one of them reached Exa's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 120 ms, against 114 ms over the 24 hours before.

Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.

AIDownCheck is not affiliated with Exa. This recap summarizes incidents published on Exa's official status page.