Expo had 69 outages in the last 2 years totaling 619h 47m of downtime — averaging 2.8 incidents per month.
There were 69 Expo outages since October 16, 2025 totaling 619h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're seeing elevated iOS submission numbers resulting in longer queue times.
This incident has been resolved.
For 20 minutes non-workflow builds were not starting correctly, resulting in immediate "Build failed" and "No logs" displayed. All builds that failed to start are automatically and do not count towards paid usage. We're sorry for the disruption.
We are currently investigating increased wait times for EAS Workflows jobs
We identified an issue leading to increased wait times for EAS Workflows jobs. Currently implementing a fix.
This incident has been resolved.
We are investigating an alert indicating a drop in availability for the Expo Push Notification service. Some requests may be delayed or temporarily unavailable.
The issue was identified and a fix was deployed, restoring normal service operation. All notification traffic is now fully operational, and we are continuing to monitor the system to ensure stability.
docs.expo.dev is inaccessible. We are investigating the issue.
We are experiencing above average usage for iOS jobs while our workers are at capacity. Users may experience longer wait times.
This incident has been resolved.
We are investigating network issues that results in few builds failing to upload artifacts
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Submissions are currently taking longer than usual and sometimes failing to download archive to submit.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating an issue related to elevated Android build failures.
We've identified the root cause and deployed a fix. We're now monitoring the system to confirm stability.
We've confirmed the system is back to normal and operating as expected. This incident is now resolved.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
EAS Update analytics are processing again. Updates published after January 6, 2026 at 6:32PM PST will have analytics missing until January 8 at 7:30PM PST. Analytics for updates published before that time are unaffected and, for clarity, all updates have complete analytics after January 8 at 7:30PM PST.
Currently investigating an issue in reduced availability of EAS services
Users may experience transient errors. We have identified the cause related to our internal network connection pool, and continue to implement a fix on raising the limit.
Connection limits now sustain expected usage. This incident has been resolved.
Increased error rate on iOS Submissions while Apple servers return 502 on App Store Connect API
Submissions should no longer observe App Store Connect errors or delayed queues
The outage lasted about 10 minutes and manifested in expo.dev returning a 500 when accessed. This was due to Cloudflare Service Issues which have since been resolved. See https://www.cloudflarestatus.com/ for more details.
We're seeing an increased error rate when installing JS dependencies caused by "500 Internal Server" being returned by NPM registry. See https://status.npmjs.org/incidents/bptmjs4rmx8q.
This incident has been resolved.
We're investigating an issue with Builds on EAS not getting marked as completed.
We've identified the bottleneck and implemented a fix. The number unsynchronized builds going down as pending builds are getting marked as completed. We're monitoring the fix.
All previously pending builds have completed, and the bottleneck has successfully been eliminated.
We are currently observing failures when installing CocoaPods. This appears to be caused by an ongoing issue with Cloudflare, which is impacting the availability of cdn.cocoapods.org. As a result, the CDN is intermittently unreachable, leading to pod installation errors for developers. We are monitoring the situation and will provide updates as Cloudflare resolves the underlying issue.
We are continuing to monitor for any further issues.
We’re seeing more and more iOS builds completing successfully, and cdn.cocoapods.org is reachable again. However, Cloudflare’s incident is still open, so we’ll continue to monitor the situation for a bit longer.
www.jitpack.io is also affected and currently unreachable. We’ve observed that some Android builds relying on this platform are impacted as well, resulting in Gradle installation failures. We’re continuing to monitor the situation.
According to Cloudflare, they have resolved the issue, and services should now be back to normal. We are still monitoring the situation.
This incident has been resolved.
Users running builds triggered by github events are seeing an elevated number of errors. A fix has been deployed and we are monitoring the results
The fix was successful and the incident is resolved.
An increased amount of notifications are failing due to an "apn write timeout".
We've taken action to improve server stability and are investigating the root cause of the "Session closed with error code 11" error to address the increased notification failure rate.
A fix has been deployed which has greatly reduced the number of failed APNs notifications. Work to improve reliability further is ongoing.
We have confirmed that a fix deployed 24 hours ago has returned APNs notifications availability to normal.
We are seeing longer than usual responses from the App Store submission API endpoints
This incident has been resolved.