Expo Outage History

EAS Update publishing was failing for 1.1 hours due to a regression that caused "not supported" errors for valid SDK versions like 55.0.0. The team identified the problematic recent change and deployed a fix to restore full operational status.

Expo experienced browser security warnings appearing on build download URLs that affected some browsers and the website component. The incident lasted 55 minutes before being resolved. Users encountered security warnings when attempting to download builds through their browsers.

EAS Submit for iOS experienced elevated failures for 2.1 hours due to issues with Apple's App Store Connect APIs. The incident affected iOS app submissions through the EAS Submit service and Apple Developer APIs. The issue was resolved when Apple's App Store Connect recovered and iOS submission success rates returned to normal.

Expo's EAS Build service experienced an issue where Mac workers failed to start, preventing iOS builds from running. The incident lasted 44 minutes and was classified as minor. The issue was resolved after investigation and the service was restored to normal operation.

Expo experienced slow workflow performance for 2.7 hours, with workflow runs taking longer than usual to start from GitHub events and progress between stages. The service team investigated and resolved the performance degradation affecting workflow execution speed.

Expo's push notification service experienced delayed delivery for 10.1 hours, affecting the Push Notifications Broker component. The issue was identified on April 13th at 9:30 AM PDT and resolved by 7:33 PM PDT the same day, with push notification delivery returning to normal operations.

Expo experienced a partial outage of their push notification service, preventing some push notifications from being delivered to users. The issue affected the Push Notifications Broker component for 54 minutes. The root cause was identified and fixed, with service availability returning to normal levels.

Expo's EAS Build service experienced intermittent Android build failures caused by errors when downloading dependencies, lasting 2.1 hours. The issue was investigated, a fix was implemented, and the incident was resolved after monitoring confirmed the solution was effective.

Expo experienced intermittent internal system problems that prevented some workflow runs from progressing to their next stage, lasting 31 hours. Affected workflow runs were canceled and users were not charged for the time when runs appeared to be running but no VMs were actually executing. The issue was identified and resolved with a fix implementation.

EAS Build experienced an elevated rate of iOS builds failing to start due to malfunctioning build hosts. The incident affected the EAS Build service for 11.9 hours until the team identified and restarted the problematic build hosts. iOS builds resumed normal operation and the issue was fully resolved after monitoring confirmed the fix was stable.