Is Exa down?
For agents
proceed
Proceed.
GET upbutler.com/status/exa/status.agent.json
MCP: upstream_status {"service":"exa"}
Neural web search API for agents.
What Exa reports
Operational
Taken as is from Exa's own status page API. Incident titles and component names below are theirs.
Open status.exa.aiUpButler's independent probe
There is no keyless endpoint of Exa that says anything useful, so UpButler does not probe it. To check your own Exa account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Exa components
6 operational
- Search APIOperational
- WebsetsOperational
- Exa MCPOperational
- Agents APIOperational
Search API
- DefaultOperational
- PeopleOperational
Exa incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Exa publishes for 90 days from the day it starts tracking a service.
Tell your outage from Exa's
Declare that your project depends on Exa. When one of your monitors fails while Exa has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- exacurl -s https://upbutler.com/status/exa/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "exa",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Exa down right now?
- No. As of 2026-10-10 05:11 UTC, Exa is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Exa's own status page API at https://status.exa.ai. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Exa's words.
- How can my agent or app check Exa status?
- Fetch https://upbutler.com/status/exa/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"exa"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Exa's?
- Add "exa" to the dependencies of your UpButler workspace. When one of your monitors fails while Exa has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in search and web data
UpButler is not affiliated with Exa. Status and incident text belong to Exa and are read from their public status source; the probe result is UpButler's own measurement.