Live / Expo / Incident
Expo: Elevated API server error rates affecting submissions and builds
Expo · expo.devMinor incidentResolved2026-10-14 16:04 UTC
Public — what happened
Summary
Expo reported a rise in errors from its API server that disrupted EAS submissions and the processing of builds. The company said the trouble began at about 6:30 AM California time on October 14, 2026, and it posted the incident at 14:56 UTC, saying it had already pinpointed the problem and was working on a fix. Expo said a fix was in place by 15:20 UTC, and after a period of monitoring it marked the incident resolved at 16:04. The company did not publicly describe what caused the errors.
Affected
EAS Build, EAS Submit
Timeline
- Started — 2026-10-14 14:56 UTC
- Identified — 2026-10-14 14:56 UTC
- Monitoring — 2026-10-14 15:20 UTC
- Resolved — 2026-10-14 16:04 UTC · 1h 07m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Expo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Expo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Expo report →
More from Expo
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.