We are investigating a latency degradation affecting Search endpoints
DEGRADEDPERFORMANCE- Started
- Sep 18, 8:00 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 138 ms, against 119 ms over the 24 hours before.
Updates are Exa's own words from its status page (status: resolved); we never add an inferred cause.