Expo outage, 5 October 2026

Website and services partially unavailable due to high database load

Started
Resolved
5 Oct 2026, 20:11 UTC - reported afterwards
Impact
Major

Last update from Expo

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 a...

5 Oct 2026, 20:40 UTC

Read the full incident on the official Expo status page

Is Expo down now?

This page is the record of one past incident. For the live status, see Is Expo down right now? - it reads the official status page every 2 minutes.

Other Expo incidents

  1. Elevated API server error rates affecting submissions and builds

  2. Website and services partially unavailable due to high database load

  3. EAS Update cache issue for rollout updates

  4. Elevated rate of failed iOS submissions

  5. Elevated rate of failed iOS submissions

  6. Elevated queue times for Android Builds, Submissions, and Workflows

  7. iOS push notification degraded performance

  8. Delayed iOS push notification delivery

All recorded Expo incidents