Expo incident: High queue times and concurrency errors for Android builds

Affected components

• EAS Build
• EAS Workflows

1. resolvedMay 14, 2026, 21:09 UTC

   This incident has been resolved.

2. monitoringMay 14, 2026, 19:40 UTC

   A fix has been implemented and we are monitoring the results.

3. investigatingMay 14, 2026, 17:12 UTC

   Limited availability for Linux workers resulting in higher than expected queue times and invalid concurrency limits

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
• Upstash: Upstash Redis – intermittent connection issues in some regionsMajor · May 14, 2026, 15:47 UTC
• PlanetScale: There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information.Major · May 14, 2026, 20:30 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• DigitalOcean: DNS service, Certificates and Managed MongoDBMinor · May 14, 2026, 13:57 UTC
• CircleCI: Elevated 429 errors pulling from maven centralMinor · May 14, 2026, 16:49 UTC
• Akamai: Cloudlets Policy Updates IssuesMinor · May 14, 2026, 18:08 UTC
• Datadog: Delayed Metric LoadingMinor · May 14, 2026, 18:24 UTC
• Clerk: SCIM services are facing intermittent errorsMinor · May 14, 2026, 20:37 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