Changes / Expo / Major outage of EAS backend
Expo: Critical incident: Major outage of EAS backend
Summary
Expo reported a critical EAS backend outage affecting EAS Build, EAS Hosting, EAS Insights, EAS Submit, EAS Update, EAS Workflows and the Website from 2026-07-08 20:39 UTC to 2026-07-08 21:29 UTC (50 min). Expo implemented a fix at 21:01 UTC and confirmed all services were operational at resolution; no cause was stated.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Major outage of EAS backend
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-08 20:39 UTC
Before: not present
After: 2026-07-08 21:29 UTC
Before: not present
After: EAS Build, EAS Hosting, EAS Insights, EAS Submit, EAS Update, EAS Workflows, Expo Application Services - EAS Build, Expo Application Services - EAS Hosting, Expo Application Services - EAS Insights, Expo Application Services - EAS Submit, Expo Application Services - EAS Update, Expo Application Services - EAS Workflows, Website
Before: not present
After: We have detected a major outage of EAS services. We are actively working on resolving the issue.
Before: not present
After: We implemented a fix. Systems are recovering. We will continue to monitor the situation until fully resolved.
Before: not present
After: We are continuing to monitor for any further issues.
Before: not present
After: We are continuing to monitor for any further issues.
Before: not present
After: All services are back to operational.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Major outage of EAS backend (this change) Expo reported a critical EAS backend outage affecting EAS Build, EAS Hosting, EAS Insights, EAS Submit, EAS Update, EAS Workflows and the Website from 2026-07-08 20:39 UTC to 2026-07-08 21:29 UTC (50 min). Expo implemented a fix at 21:01 UTC and confirmed all services were operational at resolution; no cause was stated. | Major incident |