Where does this status come from?

From Expo's own status page API at https://status.expo.dev. 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 Expo's words.

How can my agent or app check Expo status?

Fetch https://upbutler.com/status/expo/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":"expo"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Expo's?

Add "expo" to the dependencies of your UpButler workspace. When one of your monitors fails while Expo 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.

Is Expo down?

Right now

No. Expo is operational.

No incidents reported.

Read from status.expo.dev 42 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/expo/status.agent.json

MCP: upstream_status {"service":"expo"}

EAS Build, Submit and Update for React Native apps.

What Expo reports

Operational

Taken as is from Expo's own status page API. Incident titles and component names below are theirs.

Open status.expo.dev

UpButler's independent probe

There is no keyless endpoint of Expo that says anything useful, so UpButler does not probe it. To check your own Expo account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Expo components

35 operational

Third-Party Services

GitHubOperational
Google Cloud Platform - Google Compute EngineOperational
Google Cloud Platform - Google Container EngineOperational
AWS S3 -- us-west-1Operational
AWS S3 -- us-west-2Operational
Google Cloud Platform Google Cloud Pub/SubOperational
Google Cloud Platform Google Cloud SQLOperational
Google Cloud Platform Cloud Key Management ServiceOperational
Apple Developer APIsOperational
Cloudflare CDN/CacheOperational
Cloudflare DNS Root ServersOperational
GitHub API RequestsOperational
GitHub WebhooksOperational
SendGrid APIOperational
SendGrid API v3Operational
Cloudflare LogsOperational
Cloudflare DNS UpdatesOperational
Cloudflare FirewallOperational
Stripe APIOperational
Google Cloud Platform Google Cloud StorageOperational
Google Cloud Platform Google BigQueryOperational
Google Cloud Platform Google Kubernetes EngineOperational
npm Package installationOperational

Expo Application Services

EAS BuildOperational
EAS SubmitOperational
EAS UpdateOperational
EAS InsightsOperational
EAS WorkflowsOperational
EAS HostingOperational
EAS SimulatorOperational

WebsiteOperational
Dev Tools APIOperational
Classic Update Service (Application Serving API)Operational
Push Notifications BrokerOperational
NoneOperational

Expo incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Expo.

Started (UTC)	Incident	Impact	Lasted
2026-10-05 21:08	Website and services partially unavailable due to high database load	minor	2 h 13 min
2026-10-05 20:38	Website and services partially unavailable due to high database load	major	under a minute

Tell your outage from Expo's

Declare that your project depends on Expo. When one of your monitors fails while Expo 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.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - expo

Ask before you retry

curl -s https://upbutler.com/status/expo/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "expo",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Expo down right now?: No. As of 2026-10-10 05:13 UTC, Expo is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Expo's own status page API at https://status.expo.dev. 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 Expo's words.
How can my agent or app check Expo status?: Fetch https://upbutler.com/status/expo/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":"expo"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Expo's?: Add "expo" to the dependencies of your UpButler workspace. When one of your monitors fails while Expo 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 hosting and compute

UpButler is not affiliated with Expo. Status and incident text belong to Expo and are read from their public status source; the probe result is UpButler's own measurement.