Expo had 69 outages in the last 2 years totaling 51h 59m of downtime — averaging 2.8 incidents per month.
There were 69 Expo outages since October 16, 2025 totaling 51h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are investigating elevated queue times for high-priority iOS submissions on EAS Submit.
EAS iOS submission queue times are returning to normal. We are actively monitoring to confirm full recovery and will provide an update once resolved.
This incident has been resolved.
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.
This incident has been resolved.
We are experiencing higher than usual database load. We are investigating the cause, and you may experience build failures during this time.
The elevated database load has subsided and builds are processing normally. We'll continue to monitor closely.
This incident has been resolved.
We are currently investigating an issue affecting the progression of iOS jobs
Starting at 3AM PDT we observed limited availability of EAS Update manifest endpoint. Availability has now recovered. We are looking into underlying causes.
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.
We are currently investigating this issue.
This incident has been resolved.
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.
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.
Deployments via EAS Hosting are also affected by this issue.
Existing deployments are loading fine, deploying new versions is currently disrupted.
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
Users with Android Builds on priority queues may experience extended wait times as we hit capacity
Android priority queue times have returned to normal levels and backlogged jobs are progressing. We are continuing to monitor performance.
This incident has been resolved.
Limited availability for Linux workers resulting in higher than expected queue times and invalid concurrency limits
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating delays affecting Android push notification delivery. Our team is actively working to mitigate the issue and restore normal performance.
This Incident has been resolved and services are operating normally again.
We are currently investigating this issue.
A high percentage of Android builds failed to find workers due to us exceeding capacity. We have now provisioned additional resources to meet capacity.
We are currently investigating this issue.
This incident has been resolved.
We're seeing increased wait times for free tier users of EAS. A fix is deploying.
This incident has been resolved.
During a rollout of new, improved underlying Linux infrastructure for EAS we've noticed an increased rate of OOM errors. The change has been reverted.
We're investigating reports of EAS Update publishes failing with "not supported" error (e.g. "SDK 55.0.0 is not supported").
We've identified a recent change that introduced a regression. A fix is on the way.
A fix has been deployed. EAS Update publishing is fully operational.
Users received a 404 error when attempting to authenticate with Expo Go due to a server-side bug that wrongly overwrote the HTTP status code on one of our GraphQL endpoints. This has been fixed.
We're investigating reports of browser security warnings appearing on build download URLs for some browsers.
This incident has been resolved.
Between 3:44 PM and 4:08 PM PDT, existing sessions on expo.dev were treated as invalid, and users were unable to sign back in. During this window, login attempts from the website failed. The issue has been resolved and users can now sign in normally. We're investigating the root cause.
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.
Apple App Store Connect appears to have recovered, and EAS iOS submissions are returning to normal success rates. We are monitoring closely, and iOS submissions are being processed successfully.
This incident has been resolved.
We are experiencing an issue where Mac workers fail to start, resulting in impacted ios builds
This incident has been resolved.
Between 06:27 and 06:40 AM PST on April 27, EAS Build experienced failures due to a database issue. Builds started during this window may have failed to start or complete successfully. The issue has been resolved and EAS Build is operating normally. Affected builds can be re-triggered.
Starting workflow runs from GitHub events and moving workflow runs from one stage to another is currently slower than usual. We're investigating the issue.
This incident has been resolved.
Some push notifications are experiencing delayed delivery.
Push notification delivery has returned to normal.