Expo incident: Elevated Android build failures

Affected components

• EAS Build
• EAS Workflows

1. resolvedAug 4, 2026, 21:15 UTC

   This incident is resolved. Android builds are completing normally. Some Android builds and Linux workflow jobs failed early with the error "We've lost connection to the worker". Builds and jobs that failed with this error were automatically excluded from billing and can be retried.

2. investigatingAug 4, 2026, 17:54 UTC

   We are investigating an elevated rate of Android build failures on EAS. Affected builds stop early and report a lost connection to the build worker. iOS builds are not affected at the current time.

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.

• Discord: Messaging failuresCritical · Aug 4, 2026, 18:49 UTC
• Grafana Cloud: Some Grafana Instances UnavailableCritical · Aug 4, 2026, 19:11 UTC
• OneSignal: Apple push notifications failing in about 3% of casesMajor · Aug 4, 2026, 17:20 UTC
• Anthropic: Elevated errors across many modelsMajor · Aug 4, 2026, 20:48 UTC
• Supabase: Management API Performance DegradationMinor · Jul 31, 2026, 18:36 UTC
• Supabase: Project Upgrade DelaysMinor · Aug 3, 2026, 15:28 UTC
• OVHcloud: [EU-WEST-PAR][Storage] - Object storage incident notificationMinor · Aug 4, 2026, 14:08 UTC
• DigitalOcean: Spaces Cold Storage BillingMinor · Aug 4, 2026, 16:13 UTC
• CircleCI: Increased Job Queue Times: Windows, Android, and GPUMinor · Aug 4, 2026, 19:27 UTC
• LiveKit: Elevated timeouts on LiveKit Inference (google/gemma-4-31b-it)Minor · Aug 4, 2026, 20:45 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