Expo outage history

We are currently investigating this issue

This incident has been resolved.

Users may experience extended queue times or failed submissions due to an issue with downloading build artifacts. This is related to a current outage with R2 storage https://www.cloudflarestatus.com/incidents/ftvf8c3m4mv5

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

This incident has been resolved.

Queue times for Android builds and other Linux workflows are currently elevated due to GCP regional capacity constraints. We are currently enabling capacity in additional regions. Jobs in queue are continuing to progress.

Queue times for Android builds and other Linux workflows are currently elevated due to upstream provider issues affecting the provisioning of VM's. GCP has confirmed the issue and is working on resolving.

The upstream issue with creating VM's has been resolved by GCP, Linux worker queues are draining, and queue times are returning to expected levels.

This incident has been resolved.

We are currently monitoring degraded performance on the NPM registry. The degradation may cause package installs to time out, and EAS Builds to fail when using NPM. We will provide updates from NPM when available.

This incident has been resolved. NPM has restored registry performance. Package installs and EAS Builds using NPM should now complete as expected.

Maintenance on the cache instance serving Maven artifacts to Android builds has rendered the cache unavailable. We're implementing fixes.

This incident has been resolved.

Queue times are elevated for Linux workers for EAS Build and Workflows. Android build jobs may be delayed. We are currently investigating the issue.

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.

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.

We are seeing problems in our cloud provider which cause API and website availability disruption on top of delays when processing GitHub events.

The issue has been identified and a fix is being implemented.

As of 10:06am PT we rescheduled our services to run outside of the affected availability zone that is still having some networking issues. In short, Expo's services are no longer affected but we are monitoring the cloud provider's own status updates until the incident is fully resolved and we can reschedule services across all availability zones again.

Our cloud provider's network is fully operational in all of the availability zones Expo uses.

We are experiencing availability problems with our background job processing. This affects broad set of operations across EAS. We are investigating the issue and will provide updates as soon as we have more information.

A fix has been implemented and we are monitoring the systems as they are recovering.

Systems have mostly recovered.

This incident has been resolved.

Users may experience errors from Apple upon uploading to App Store Connect, resulting in failed submissions. We are continuing to monitor.

This incident has been resolved.

User's may experience iOS submissions delayed with long build uploads to App Store Connect. Apple’s API is reporting prolonged pending or processing states, which will increase submission queue times

This incident has been resolved.

User's may experience iOS submissions delayed with long build uploads to App Store Connect. Apple’s API is reporting prolonged pending or processing states, which will increase submission queue times

This incident has been resolved.

The issue has been identified and a fix is being implemented.

`[email protected]` package set to `latest` in the meantime. working on fix and will publish a new version.

We are continuing to work on a fix for this issue.

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

Fix deployed to server, `[email protected]` set back to `latest`.

We are currently investigating this issue.

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

This incident has been resolved.

Users may see errors when logging into Expo Go or Dev Clients.

Fix is being deployed, should be available within the next ~1hr.

We are continuing to work on a fix for this issue.

Fix is deployed.

At around 4 PM PDT, we experienced a temporary spike in EAS Update manifest serving errors. Service reliability has returned to normal, and we are monitoring the situation.

We are currently investigating this issue.

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

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

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

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

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.

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.

We are currently investigating this issue.

This incident has been resolved.