Problems with API and website availability
Our cloud provider's network is fully operational in all of the availability zones Expo uses.
The latest update from Expo.
State
Resolved
Started
61 d ago
2026-09-01 15:51 UTC
Lasted
3 h 22 min
until 2026-09-01 19:13 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
25 min 12%
Identified
1 h 14 min 37%
Monitoring
1 h 43 min 51%
Updates
Times in UTCAs posted by Expo
Our cloud provider's network is fully operational in all of the availability zones Expo uses.
As of 10:06am PT we rescheduled our services to run outside of the affected availability zone that is still having some networking issues. In short, Expo's services are no longer affected but we are monitoring the cloud provider's own status updates until the incident is fully resolved and we can reschedule services across all availability zones again.
The issue has been identified and a fix is being implemented.
We are seeing problems in our cloud provider which cause API and website availability disruption on top of delays when processing GitHub events.
Affected components
15Expo in the last 90 days
Full historyIncidents in 90 days
26
Days with an incident
24
Median duration
2 h 34 min
This incident
1.3× the median
Other Expo incidents
All incidentsExpo·Elevated submission error rates
This incident has been resolved.
Expo·Elevated iOS submission error rates
This incident has been resolved.
Expo·Elevated API server error rates affecting submissions and builds
This incident has been resolved.
Expo·Website and services partially unavailable due to high database load
This incident has been resolved.
Expo·EAS Update cache issue for rollout updates
This incident has been resolved.
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.
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.cc/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.
https://outages.cc/feed.xml?providers=expo/feed subscribe https://outages.cc/feed.xml?providers=expoFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane