Website and services partially unavailable due to high database load

What to do

• Check whether your product depends on Expo. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-05 20:38 UTC and 2026-10-05 20:11 UTC may need a replay.

• Subscribe to Expo's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=expo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

Due to high database load, the Expo website and several services including submitting CI/CD jobs, build jobs, and store submissions were partially unavailable.

Updates from Expo 2

1. resolvedOct 5, 2026, 8:11 PM UTC

   Due to high database load, the Expo website and several services including submitting CI/CD jobs, build jobs, and store submissions were partially unavailable. The issue has subsided as of 1:30PM PT and we are continuing to diagnose the root cause and monitor the health of the services.

   provider

2. postmortemOct 5, 2026, 8:40 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.