outages.live
Live

Expo

Expo is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

26

Days with an incident

23

Median duration

2 h 34 min

Longest incident

18 h

Components

35

Third-Party Services

GitHub Operational
90 days agoNo incidentsToday
Google Cloud Platform - Google Compute Engine Operational
90 days ago1 day with an incidentToday
Google Cloud Platform - Google Container Engine Operational
90 days agoNo incidentsToday
AWS S3 -- us-west-1 Operational
90 days agoNo incidentsToday
AWS S3 -- us-west-2 Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Cloud Pub/Sub Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Cloud SQL Operational
90 days agoNo incidentsToday
Google Cloud Platform Cloud Key Management Service Operational
90 days agoNo incidentsToday
Apple Developer APIs Operational
90 days ago3 days with an incidentToday
Cloudflare CDN/Cache Operational
90 days agoNo incidentsToday
Cloudflare DNS Root Servers Operational
90 days agoNo incidentsToday
GitHub API Requests Operational
90 days agoNo incidentsToday
GitHub Webhooks Operational
90 days agoNo incidentsToday
SendGrid API Operational
90 days agoNo incidentsToday
SendGrid API v3 Operational
90 days agoNo incidentsToday
Cloudflare Logs Operational
90 days agoNo incidentsToday
Cloudflare DNS Updates Operational
90 days agoNo incidentsToday
Cloudflare Firewall Operational
90 days agoNo incidentsToday
Stripe API Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Cloud Storage Operational
90 days agoNo incidentsToday
Google Cloud Platform Google BigQuery Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Kubernetes Engine Operational
90 days agoNo incidentsToday
npm Package installation Operational
90 days ago2 days with an incidentToday

Expo Application Services

EAS Build Operational
90 days ago5 days with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 17, 2026

Duration52 min00:51 to 01:43Elevated submission error ratesDegraded

This incident has been resolved.

Oct 16, 2026

Duration2 h 37 min14:07 to 16:44Elevated iOS submission error ratesPartial outage

This incident has been resolved.

Oct 14, 2026

Duration1 h 7 min14:56 to 16:04Elevated API server error rates affecting submissions and buildsDegraded

This incident has been resolved.

Oct 5, 2026

Duration2 h 13 min21:08 to 23:21Website and services partially unavailable due to high database loadDegraded

This incident has been resolved.

Sep 23, 2026

Duration3 h 34 min23:37 to 03:11EAS Update cache issue for rollout updatesDegraded

This incident has been resolved.

Sep 21, 2026

Duration9 h 24 min21:18 to 06:42Elevated rate of failed iOS submissionsPartial outage

This incident has been resolved.

Duration14 min20:26 to 20:41Elevated rate of failed iOS submissionsPartial outage

This incident has been resolved.

Sep 18, 2026

Duration2 h 48 min12:43 to 15:31Elevated queue times for Android Builds, Submissions, and WorkflowsDegraded

This incident has been resolved.

Sep 8, 2026

Duration4 h 41 min14:42 to 19:23iOS push notification degraded performanceDegraded

This incident has been resolved.

Sep 5, 2026

Duration1 h 1 min15:38 to 16:38Delayed iOS push notification deliveryDegraded

This incident has been resolved.

Sep 4, 2026

Duration4 h 37 min21:23 to 01:59Delayed and failed submissions due to issues with build artifactsDegraded

This incident has been resolved.

Duration15 h 4 min16:05 to 07:10Elevated Linux worker queue timesPartial outage

This incident has been resolved.

Sep 3, 2026

Duration18 h22:45 to 16:45Degraded performance on the NPM registryDegraded

This incident has been resolved. NPM has restored registry performance. Package installs and EAS Builds using NPM should now complete as expected.

Sep 2, 2026

Duration21 min21:44 to 22:05Elevated Linux worker queue timesDegraded

A fix was deployed at 2:50pm PT/5:50pm ET. The job queue has been running as expected. The root cause of this incident is that a new version of a cache needed more vCPUs than it was given, and we have increased the CPU count as the immediate fix along with additional monitoring for CPU usage on these cache instances.

Follow Expo

Your coding agent knows when Expo is down, and tells you when a failure is theirs, not yours. You can also get Expo incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "expo" and tell me if Expo has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=expo
Slack
/feed subscribe https://outages.live/feed.xml?providers=expo

Go from tracking outages to fixing production issues with Polylane.

Try Polylane