Elevated submission error rates
Last updateresolvedOct 17 · 01:43 UTC
This incident has been resolved.
Reported by Expo on their status page.
checked Nov 1, 2026 9:27 AM UTC · Expo's official status page
Expo is up and running.
Expo is currently operational with all systems functioning normally.
All components operational
Be the first to know
Statusfield watches Expo alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
Expo incident history
5 reports published by Expo in the last 30 days
When Expo breaks, it is typically resolved in 2h 3m — median across 12 resolved incidents over 30 days.
October 17, 2026
October 16, 2026
Elevated iOS submission error rates
Last updateresolvedOct 16 · 16:44 UTC
This incident has been resolved.
Reported by Expo on their status page.
October 14, 2026
Elevated API server error rates affecting submissions and builds
Last updateresolvedOct 14 · 16:04 UTC
This incident has been resolved.
Reported by Expo on their status page.
October 5, 2026
Website and services partially unavailable due to high database load
Last updateresolvedOct 5 · 23:21 UTC
This incident has been resolved.
Reported by Expo on their status page.
Website and services partially unavailable due to high database load
Last updatepostmortemOct 5 · 20:40 UTC
The primary database was under high CPU load from 1:11PM-1:29PM PT. The impact of this is that our website and API were partially unavailable (more precisely, at 80-90% availability) during that time.
Scope
What was affected: This affected most services including the website, builds, submissions, CI/CD jobs, and publishing updates.
What wasn’t affected: Serving updates to end users maintained 100.000% availability. App performance measurements sent to Observe were also unaffected.
Root cause analysis
An internal orchestrator service used to update the state of CI/CD jobs, including build jobs and store submission jobs, was updated to retry upon application-level failures. We are investigating more thoroughly and currently believe this led to a cascade of retries that caused more failures once the database was under more load than it could handle.
Remediation
The commit that changed retry behavior was rolled back and we are clearing the queue of retries.
For a more robust solution, the internal orchestrator must gracefully handle backpressure from the application server and database, and to apply more backoff.
Reported by Expo on their status page.