Expo incident: Elevated Linux worker queue times

Affected components

• EAS Build
• EAS Workflows

1. resolvedSep 2, 2026, 22:05 UTC

   A fix was deployed at 2:50pm PT/5:50pm ET. The job queue has been running as expected. The root cause of this incident is that a new version of a cache needed more vCPUs than it was given, and we have increased the CPU count as the immediate fix along with additional monitoring for CPU usage on these cache instances.

2. identifiedSep 2, 2026, 21:52 UTC

   We have determined that some of our package caches are under high load, and this is causing elevated build times and in turn causing higher Linux worker queue times. We are currently working on a fix. In-progress builds are continuing to complete and enqueued builds are continuing to be processed.

3. investigatingSep 2, 2026, 21:44 UTC

   Queue times are elevated for Linux workers for EAS Build and Workflows. Android build jobs may be delayed. We are currently investigating the 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.

• Elasticsearch: Replication bug causing slow recoveriesMajor · Sep 1, 2026, 08:16 UTC
• OVHcloud: [EU-SOUTH-MIL][Containers & Orchestration] - Managed Private Registry incident notificationMinor · Aug 26, 2026, 15:00 UTC
• Snowflake: INC20000150Minor · Aug 28, 2026, 00:07 UTC
• Shippo: Elevated errors on FedEx rating and label purchaseMinor · Sep 2, 2026, 17:31 UTC
• LiveKit: Investigating reports of one-way audio issues in LiveKit Phone NumbersMinor · Sep 2, 2026, 21:25 UTC
• Telnyx: Intermittent delays for some outbound messagesMinor · Sep 2, 2026, 21:33 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