Live / Expo / Incident
Expo: Website and services partially unavailable due to high database load
Expo · expo.devMinor incidentResolved2026-10-05 23:21 UTC
Public — what happened
Summary
Expo reported a minor incident on October 5, 2026, in which its website and services were partly unavailable, which the company attributed to heavy load on its database. Expo said it began seeing a higher rate of API errors at 21:08 UTC and started investigating. By 21:15 UTC the company said it had put a fix in place and was watching the results, and it marked the incident resolved at 23:21.
Affected
Website, Dev Tools API, Push Notifications Broker
Timeline
- Started — 2026-10-05 21:08 UTC
- Investigating — 2026-10-05 21:08 UTC
- Monitoring — 2026-10-05 21:15 UTC
- Resolved — 2026-10-05 23:21 UTC · 2h 13m 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 42, 2026, our weekly internet health report.