There were 38 Expo outages since February 8, 2026 totaling 66h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are investigating a partial outage of the push notification service.
The root cause has been fixed and our charts confirm availability is back to normal. We apologize for the outage.
The Expo push notification service suffered from partial unavailability due to an outage of one of our cache servers. Specifically, we deployed a change that optimized our cache entries to be more compact to improve the performance and efficiency of our caches. However, the cache could not handle the load from evicting the old entries. Clearing the cache solved the problem.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to an intermittent internal system problems some workflow runs fail to progress to their next stage. We're working on resolving the issue. Affected runs will get canceled. You are not going to be charged the duration that the workflow run appears running, but is not running any VM.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
We identified and restarted a number of build hosts that were not functioning correctly. iOS builds should now be starting as expected. We're monitoring to confirm the fix is holding.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're investigating an issue where some EAS Workflows are not progressing past the pending state. Affected workflows show no logs and remain queued. We'll provide updates as we learn more.
The issue has been resolved. A database table lock was preventing workflows from being picked up and progressing. The lock has been cleared and workflow processing has resumed. Affected workflows that were stuck during this period have been marked as errored with a message pointing to this status page. If your workflow was affected, please re-run it. We are continuing to investigate the root cause of the lock to prevent this from recurring.
We are currently investigating. Clearing cookies for `expo.dev` may resolve the issue for some users.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A backwards-incompatible change to `type: fingerprint` params has been accidentally deployed to production (requiring providing `params` on the job). A fix is being deployed.
This incident has been resolved.
Some EAS Builds are failing with errors reading from the Expo config
We have identified a problem causing some builds to fail to start. Builds are automatically waived so the incur no fees. Working on a fix.
This incident has been resolved.
We are currently investigating an issue where users may fail to view their build page
This incident has been resolved.
Customers may experience longer wait times for Workflow jobs as we reach worker capacity
This incident has been resolved.
Some workflow runs due to progress between 11:50 UTC and 12:25 UTC have failed to due to internal outage. Easiest mitigation is to cancel the frozen workflow and retry "from failed jobs". We are sorry for the disruption.
We're observing unusually high queue times for free tier users on Workflows and EAS Submit. We have taken steps to reduce the queue times. Jobs are being processed and max queue time is steadily decreasing.
This incident has been resolved.
For 15 minutes Android Emulators in Maestro tests were failing to start due to faulty network readiness detection logic. We're sorry for the disruption.
EAS Update is experiencing degraded performance, preventing end users from receiving new updates. We are seeing elevated rates of 5xx responses from u.expo.dev during this time.
On February 24th we observed elevated rate of errors when installing custom Node.js version. Later this day it was fixed and should no longer be observed by users.
Pingoru polls Expo's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required