Expo

Affected: EAS Submit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-17 00:51 UTC

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

2. resolved 2026-10-17 01:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit, Apple Developer APIs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-16 14:07 UTC

   We're seeing an increased rate of error response statuses coming from App Store Connect API ("500 Internal Server Error").

2. resolved 2026-10-16 16:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-14 14:56 UTC

   Around 6:30 AM California Time, our API server began experiencing elevated error rates for EAS submissions and build processing. We've identified the issue and are implementing a fix.

2. monitoring 2026-10-14 15:20 UTC

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

3. resolved 2026-10-14 16:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Website, Dev Tools API, Push Notifications Broker

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-05 21:08 UTC

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. monitoring 2026-10-05 21:15 UTC

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

3. resolved 2026-10-05 23:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-05 20:11 UTC

   Due to high database load, the Expo website and several services including submitting CI/CD jobs, build jobs, and store submissions were partially unavailable. The issue has subsided as of 1:30PM PT and we are continuing to diagnose the root cause and monitor the health of the...

2. postmortem 2026-10-05 20:40 UTC

   The primary database was under high CPU load from 1:11PM-1:29PM PT. The impact of this is that our website and API were partially unavailable \(more precisely, at 80-90% availability\) during that time. ### Scope What was affected: This affected most services including the...

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Update

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 23:37 UTC

   We are currently investigating this issue.

2. identified 2026-09-24 00:13 UTC

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

3. monitoring 2026-09-24 00:55 UTC

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

4. resolved 2026-09-24 03:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit, Apple Developer APIs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-21 21:18 UTC

   We're again seeing an elevated rate of iOS submissions failing. Our logs still point to a failing App Store Connect API (502 bad gateway response status code).

2. monitoring 2026-09-21 21:32 UTC

   The errors from the 3rd party API have stopped. Submissions look healthy!

3. resolved 2026-09-22 06:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit, Apple Developer APIs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-21 20:26 UTC

   We're seeing an elevated rate of iOS submissions failing. Our logs point to a failing App Store Connect API (502 bad gateway response status code).

2. monitoring 2026-09-21 20:31 UTC

   It looks like the 3rd party API is healthy again. We're going to keep monitoring.

3. resolved 2026-09-21 20:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit, EAS Workflows

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-18 12:43 UTC

   We are currently investigating this issue.

2. identified 2026-09-18 12:53 UTC

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

3. monitoring 2026-09-18 13:01 UTC

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

4. resolved 2026-09-18 15:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Push Notifications Broker

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-08 14:42 UTC

   We are investigating a backlog in the iOS queue for Expo Notifications, resulting in delayed sending of notifications and generation of push receipts.

2. resolved 2026-09-08 19:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Push Notifications Broker

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-05 15:38 UTC

   We are currently investigating this issue

2. resolved 2026-09-05 16:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 21:23 UTC

   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

2. monitoring 2026-09-05 00:30 UTC

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

3. resolved 2026-09-05 01:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. identified 2026-09-04 16:05 UTC

   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.

2. identified 2026-09-04 17:06 UTC

   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.

3. monitoring 2026-09-04 20:38 UTC

   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.

4. resolved 2026-09-05 07:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: npm Package installation

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 22:45 UTC

   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.

2. resolved 2026-09-04 16:45 UTC

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

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Workflows

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-02 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.

2. identified 2026-09-02 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...

3. resolved 2026-09-02 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...

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, Website, Google Cloud Platform - Google Compute Engine, EAS Submit, EAS Update, EAS Insights, EAS Workflows, EAS Hosting

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

Started during GitHub: Delays in commit processing.

1. investigating 2026-09-01 15:51 UTC

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

2. identified 2026-09-01 16:16 UTC

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

3. monitoring 2026-09-01 17:30 UTC

   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...

4. resolved 2026-09-01 19:13 UTC

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

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit, EAS Update, EAS Insights, EAS Workflows, EAS Hosting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-01 11:45 UTC

   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.

2. monitoring 2026-09-01 12:04 UTC

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

3. monitoring 2026-09-01 12:10 UTC

   Systems have mostly recovered.

4. resolved 2026-09-01 12:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-08-26 15:51 UTC

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

2. resolved 2026-08-26 19:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-18 16:25 UTC

   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

2. resolved 2026-08-19 00:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-08-17 21:12 UTC

   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

2. resolved 2026-08-17 23:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Workflows

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-14 17:04 UTC

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

2. identified 2026-08-14 17:15 UTC

   `eas-cli@21.8.0` package set to `latest` in the meantime. working on fix and will publish a new version.

3. identified 2026-08-14 17:30 UTC

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

4. identified 2026-08-14 17:41 UTC

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

5. monitoring 2026-08-14 17:49 UTC

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

6. resolved 2026-08-14 19:35 UTC

   Fix deployed to server, `eas-cli@22.0.0` set back to `latest`.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Update

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-13 02:59 UTC

   We are currently investigating this issue.

2. monitoring 2026-08-13 03:01 UTC

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

3. resolved 2026-08-13 03:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-12 19:00 UTC

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

2. identified 2026-08-12 23:29 UTC

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

3. identified 2026-08-12 23:36 UTC

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

4. resolved 2026-08-13 00:00 UTC

   Fix is deployed.

Excerpts are shortened. Read the full incident on Expo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-08 23:00 UTC

   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.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 15:32 UTC

   We are currently investigating this issue.

2. monitoring 2026-08-07 15:50 UTC

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

3. resolved 2026-08-07 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-07 12:39 UTC

   We are currently investigating this issue.

2. investigating 2026-08-07 12:40 UTC

   We are continuing to investigate this issue.

3. investigating 2026-08-07 12:50 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-08-07 13:01 UTC

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

5. resolved 2026-08-07 13:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Push Notifications Broker

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-04 22:19 UTC

   We are currently investigating this issue.

2. resolved 2026-08-04 23:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Workflows

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-04 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.

2. resolved 2026-08-04 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...

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Update

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-30 06:19 UTC

   We are currently investigating this issue.

2. resolved 2026-07-30 06:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-26 23:22 UTC

   We're currently seeing elevated failures with EAS Submit for iOS. This appears to be related to potential issues with Apple APIs / App Store Connect services. Our team is actively monitoring submit success rates and external reports, and we’ll share updates as we learn more.

2. identified 2026-07-27 00:03 UTC

   Elevated submission failures for iOS are caused by an App Store Connect outage. We’re monitoring recovery — check Apple’s System Status for updates.

3. resolved 2026-07-27 00:55 UTC

   iOS submission success rates are back to normal as App Store Connect continues to recover. Submissions that failed during the outage won’t be retried automatically — please resubmit those builds.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-14 21:17 UTC

   We're seeing increased submission times when submitting iOS apps (both queue times and upload times).

2. identified 2026-07-14 22:07 UTC

   The issue has been identified and we are monitoring queue times.

3. monitoring 2026-07-15 00:12 UTC

   iOS submission queue times are recovering to normal rates — we'll keep monitoring until they're fully back to expected levels.

4. resolved 2026-07-15 01:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-10 13:18 UTC

   We're seeing increased submission times when submitting Android apps (both queue times and upload times).

2. monitoring 2026-07-10 13:28 UTC

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

3. resolved 2026-07-10 13:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, Website, EAS Submit, EAS Update, EAS Insights, EAS Workflows, EAS Hosting

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-08 20:39 UTC

   We have detected a major outage of EAS services. We are actively working on resolving the issue.

2. monitoring 2026-07-08 21:01 UTC

   We implemented a fix. Systems are recovering. We will continue to monitor the situation until fully resolved.

3. monitoring 2026-07-08 21:10 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-07-08 21:16 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-07-08 21:29 UTC

   All services are back to operational.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 13:39 UTC

   We are investigating reports that some free plan users are getting limited on builds before reaching their included allowance.

2. resolved 2026-07-01 14:35 UTC

   It looks like users are not actually getting limited, but are getting a 100% build used warning ahead of time when triggering a build from the eas cli. Use eas-cli@latest for correct messaging.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit, EAS Workflows

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-29 15:28 UTC

   We identified a bad deployment causing elevated error rates and latency for EAS Build, Workflows, and Submit. Our team is working on mitigating the issue.

2. resolved 2026-06-29 15:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit, EAS Workflows

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-29 15:14 UTC

   We identified a bad deployment causing elevated error rates and latency for EAS Build, Workflows, and Submit. Our team is working on mitigating the issue.

2. monitoring 2026-06-29 15:18 UTC

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

3. resolved 2026-06-29 15:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-06-26 16:00 UTC

   Between 9:04am PDT and 10:56am PDT, users experienced scrolling issues on the Build and Workflows pages of expo.dev. This was caused by a CSS issue introduced in a recent deployment. We rolled back the deployment and verified the issue is resolved. We apologize for the...

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-25 01:35 UTC

   We are currently investigating elevated EAS Build failures.

2. resolved 2026-06-25 04:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Apple Developer APIs

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-06-23 17:28 UTC

   App Store Connect is currently experiencing an outage, and you may not be able to interact with it through the API (such as to sign in and generate credentials). https://developer.apple.com/system-status/

2. resolved 2026-06-23 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Website

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-19 09:02 UTC

   The issue has been identified, a fix is deploying.

2. resolved 2026-06-19 09:13 UTC

   The fix is deployed. Environment variables pages should now work after refreshing. We apologize for the disruption.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Workflows

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-16 16:31 UTC

   We have observed a degradation in our NPM cache that has resulted in Workflows to timeout and fail on npm install. The cache is now disabled.

2. identified 2026-06-16 17:01 UTC

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

3. resolved 2026-06-16 18:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 22:51 UTC

   We are investigating elevated queue times for iOS submissions on EAS Submit.

2. monitoring 2026-06-11 01:02 UTC

   EAS iOS submission queue times are returning to normal. We are actively monitoring to confirm full recovery and will provide an update once resolved.

3. resolved 2026-06-11 01:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, Website, EAS Workflows, GitHub API Requests

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2026-06-10 16:05 UTC

   We're seeing certain actions like updating commit status of EAS jobs or fetching project source from GitHub are currently failing. We're following https://www.githubstatus.com/incidents/fcj3088jg1wx.

2. resolved 2026-06-10 17:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit, EAS Workflows

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-09 02:35 UTC

   We are experiencing higher than usual database load. We are investigating the cause, and you may experience build failures during this time.

2. monitoring 2026-06-09 02:52 UTC

   The elevated database load has subsided and builds are processing normally. We'll continue to monitor closely.

3. resolved 2026-06-09 03:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Build, EAS Submit, EAS Workflows

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-31 20:38 UTC

   There is a networking outage in our macOS data center. We are waiting for a fix on their end.

2. identified 2026-05-31 23:43 UTC

   There is a networking outage affecting our macOS data center provider. They are working in coordination with their upstream providers to resolve the issue. We will be ready to work immediately on restoring availability once the data center provider is back online.

3. identified 2026-06-01 01:02 UTC

   Our data center provider is still working on the issue. We noticed one of our racks became reachable again and started processing jobs successfully but that rack is now offline again. We are monitoring the servers’ network and status updates from the data center and are ready to...

4. monitoring 2026-06-01 01:37 UTC

   The data center’s network has partially recovered and the availability of the affected services (iOS build and submission jobs and macOS CI jobs) is back. We are monitoring service health. The backlog of affected jobs is being processed as fast as possible - specifically,...

5. monitoring 2026-06-01 03:46 UTC

   Our data center confirmed the network is fully operational and we are closing this incident after confirming EAS iOS build and submission jobs and macOS CI/CD workflow jobs are running as normal. All paid customer jobs have been processed and new paid, high-priority jobs will...

6. resolved 2026-06-01 03:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Update

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-29 12:54 UTC

   Starting at 3AM PDT we observed limited availability of EAS Update manifest endpoint. Availability has now recovered. We are looking into underlying causes.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Submit

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-28 15:20 UTC

   EAS Submit jobs of certain types have not been getting their status and logs updated in website, despite having been processed successfully. We have identified the issue, implemented a fix and have just finished updating all the old records to their right state.

Excerpts are shortened. Read the full incident on Expo's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-25 15:38 UTC

   We observed an increased rate of timeouts for updates manifest requests. This issue has been resolved and the service is stable.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: EAS Update

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-22 19:06 UTC

   We are currently investigating this issue.

2. resolved 2026-05-23 02:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Expo's status page.

Affected: Website, EAS Hosting

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-22 16:04 UTC

   We are investigating an issue where some project and hosting pages on expo.dev are stuck on the skeleton loading state or not rendering content.

2. identified 2026-05-22 16:05 UTC

   We have identified the cause of this issue as a problem with a third-party service. They are actively working on a fix and we will update this page once it is resolved.

3. identified 2026-05-22 16:17 UTC

   Deployments via EAS Hosting are also affected by this issue.

4. identified 2026-05-22 16:19 UTC

   Existing deployments are loading fine, deploying new versions is currently disrupted.

5. resolved 2026-05-22 16:42 UTC

   The project dashboard, hosting dashboard and "eas deploy" are operational again. For more information about the incident and timelines, see https://www.cloudflarestatus.com/incidents/znll7lfnd35h

Excerpts are shortened. Read the full incident on Expo's status page.