Expo incident: High percentage of Android build errors

Affected components

• EAS Build

1. resolvedMay 13, 2026, 19:28 UTC

   A high percentage of Android builds failed to find workers due to us exceeding capacity. We have now provisioned additional resources to meet capacity.

2. investigatingMay 13, 2026, 17:32 UTC

   We are currently investigating this issue.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Expo's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Short Codes to Google Voice United StatesMinor · May 4, 2026, 20:40 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
• Twilio: SMS Delivery Delays from Twilio to Multiple Networks in Multiple Countries in EuropeMinor · May 7, 2026, 08:07 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Twilio: Voice Call Audio Quality Degradation between a Subset of Twilio United States Phone Numbers and T-Mobile in United StatesMinor · May 11, 2026, 16:04 UTC
• Grafana Cloud: Intermittent Errors and High latency Writing to Cloud Metrics, Cloud Logs and Cloud TracesMinor · May 13, 2026, 08:50 UTC
• Snyk: Reporting PDF DegradedMinor · May 13, 2026, 14:49 UTC
• Supabase: Edge Traffic IssuesMinor · May 13, 2026, 16:15 UTC

How often does Expo have incidents?

Expo reported 27 incidents in the last 90 days, 7 of them major or critical. A typical incident lasted 2h 31m. See Expo's uptime and incident history