Expo Outage History

Expo is up right now

Expo had 69 outages in the last 2 years totaling 145h 13m of downtime — averaging 2.8 incidents per month.

There were 69 Expo outages since October 16, 2025 totaling 145h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.expo.io

Major April 9, 2026

Some push notifications are not being delivered

Detected by Pingoru
Apr 09, 2026, 10:25 PM UTC
Resolved
Apr 09, 2026, 11:29 PM UTC
Duration
1h 4m
Affected: Push Notifications Broker
Timeline · 3 updates
  1. investigating Apr 09, 2026, 10:43 PM UTC

    We are investigating a partial outage of the push notification service.

  2. resolved Apr 09, 2026, 11:36 PM UTC

    The root cause has been fixed and our charts confirm availability is back to normal. We apologize for the outage.

  3. postmortem Apr 09, 2026, 11:36 PM UTC

    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.

Read the full incident report →

Minor April 9, 2026

Intermittent Android build failures due to errors when downloading dependencies

Detected by Pingoru
Apr 09, 2026, 11:23 AM UTC
Resolved
Apr 09, 2026, 12:30 PM UTC
Duration
1h 7m
Affected: EAS Build
Timeline · 3 updates
  1. investigating Apr 09, 2026, 11:23 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 09, 2026, 11:59 AM UTC

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

  3. resolved Apr 09, 2026, 01:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 7, 2026

Some workflow runs are not progressing

Detected by Pingoru
Apr 07, 2026, 12:48 PM UTC
Resolved
Apr 08, 2026, 02:20 PM UTC
Duration
1d 1h
Affected: EAS Workflows
Timeline · 3 updates
  1. investigating Apr 07, 2026, 12:48 PM UTC

    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.

  2. identified Apr 07, 2026, 02:15 PM UTC

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

  3. resolved Apr 08, 2026, 07:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 1, 2026

Elevated rate of EAS Build iOS builds failing to start

Detected by Pingoru
Apr 01, 2026, 10:48 AM UTC
Resolved
Apr 01, 2026, 10:39 PM UTC
Duration
11h 50m
Affected: EAS Build
Timeline · 4 updates
  1. investigating Apr 01, 2026, 10:48 AM UTC

    We are currently investigating this issue.

  2. monitoring Apr 01, 2026, 06:38 PM UTC

    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.

  3. monitoring Apr 01, 2026, 10:37 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Apr 01, 2026, 10:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 31, 2026

Some EAS Workflows stuck in pending state

Detected by Pingoru
Mar 31, 2026, 01:40 PM UTC
Resolved
Mar 31, 2026, 02:30 PM UTC
Duration
49m
Affected: EAS Workflows
Timeline · 2 updates
  1. investigating Mar 31, 2026, 01:40 PM UTC

    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.

  2. resolved Mar 31, 2026, 03:52 PM UTC

    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.

Read the full incident report →

Minor March 26, 2026

Log in to EAS may be broken for some users

Detected by Pingoru
Mar 26, 2026, 05:56 PM UTC
Resolved
Mar 26, 2026, 11:48 PM UTC
Duration
5h 51m
Affected: Website
Timeline · 3 updates
  1. investigating Mar 26, 2026, 05:56 PM UTC

    We are currently investigating. Clearing cookies for `expo.dev` may resolve the issue for some users.

  2. monitoring Mar 26, 2026, 11:46 PM UTC

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

  3. resolved Mar 26, 2026, 11:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 25, 2026

Fingerprint jobs failing to parse params

Detected by Pingoru
Mar 25, 2026, 12:19 PM UTC
Resolved
Mar 25, 2026, 12:38 PM UTC
Duration
19m
Affected: EAS Workflows
Timeline · 2 updates
  1. identified Mar 25, 2026, 12:19 PM UTC

    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.

  2. resolved Mar 25, 2026, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2026

Some EAS Build failures

Detected by Pingoru
Mar 24, 2026, 10:10 PM UTC
Resolved
Mar 24, 2026, 07:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 24, 2026, 10:10 PM UTC

    Some EAS Builds are failing with errors reading from the Expo config

Read the full incident report →

Major March 20, 2026

Some EAS Builds fail to start

Detected by Pingoru
Mar 20, 2026, 02:12 PM UTC
Resolved
Mar 20, 2026, 03:15 PM UTC
Duration
1h 2m
Affected: EAS Build
Timeline · 2 updates
  1. identified Mar 20, 2026, 02:12 PM UTC

    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.

  2. resolved Mar 20, 2026, 03:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 19, 2026

EAS Build dashboard fails to load

Detected by Pingoru
Mar 19, 2026, 05:36 PM UTC
Resolved
Mar 19, 2026, 06:22 PM UTC
Duration
46m
Affected: EAS Build
Timeline · 2 updates
  1. investigating Mar 19, 2026, 05:36 PM UTC

    We are currently investigating an issue where users may fail to view their build page

  2. resolved Mar 19, 2026, 06:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 18, 2026

Increased queue times for EAS Workflows jobs

Detected by Pingoru
Mar 18, 2026, 05:59 PM UTC
Resolved
Mar 18, 2026, 07:37 PM UTC
Duration
1h 38m
Affected: EAS Workflows
Timeline · 2 updates
  1. identified Mar 18, 2026, 05:59 PM UTC

    Customers may experience longer wait times for Workflow jobs as we reach worker capacity

  2. resolved Mar 18, 2026, 07:37 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 12, 2026

Frozen workflow runs

Detected by Pingoru
Mar 12, 2026, 01:23 PM UTC
Resolved
Mar 12, 2026, 12:25 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 12, 2026, 01:23 PM UTC

    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.

Read the full incident report →

Minor March 4, 2026

Elevated Workflows and Submit times for free tier users

Detected by Pingoru
Mar 04, 2026, 09:36 PM UTC
Resolved
Mar 04, 2026, 11:24 PM UTC
Duration
1h 47m
Affected: EAS SubmitEAS Workflows
Timeline · 2 updates
  1. monitoring Mar 04, 2026, 09:36 PM UTC

    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.

  2. resolved Mar 04, 2026, 11:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 4, 2026

Android Emulators failing to start

Detected by Pingoru
Mar 04, 2026, 10:12 AM UTC
Resolved
Mar 04, 2026, 10:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 04, 2026, 10:12 AM UTC

    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.

Read the full incident report →

Major February 25, 2026

Degraded performance with EAS Update

Detected by Pingoru
Feb 25, 2026, 09:54 PM UTC
Resolved
Feb 23, 2026, 11:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 25, 2026, 09:54 PM UTC

    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.

Read the full incident report →

Notice February 25, 2026

Custom Node.js version not installing

Detected by Pingoru
Feb 25, 2026, 08:02 PM UTC
Resolved
Feb 24, 2026, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 25, 2026, 08:02 PM UTC

    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.

Read the full incident report →

Minor February 25, 2026

New login sessions don't work with Launch

Detected by Pingoru
Feb 25, 2026, 07:22 PM UTC
Resolved
Feb 25, 2026, 10:46 PM UTC
Duration
3h 23m
Timeline · 2 updates
  1. identified Feb 25, 2026, 10:37 PM UTC

    If you try to log in to use Launch (launch.dev) it does not work. This affects login sessions created after 11:22 AM PT. We are working on a fix.

  2. resolved Feb 25, 2026, 10:52 PM UTC

    This issue has been resolved. All login sessions work with Launch again.

Read the full incident report →

Minor February 24, 2026

Increased rate of workflow runs failing to start

Detected by Pingoru
Feb 24, 2026, 04:20 PM UTC
Resolved
Feb 24, 2026, 11:20 PM UTC
Duration
6h 59m
Affected: EAS Workflows
Timeline · 2 updates
  1. identified Feb 24, 2026, 04:20 PM UTC

    We're seeing workflow runs failing to start with error Invalid workflow definition. [jobs]: Invalid input: expected record, received undefined. We're working on a fix. As a temporary fix we recommend changing the YAML file slightly (e.g. add a YAML comment) to trigger a re-fetch from GitHub / reinstantiate workflow config.

  2. resolved Feb 24, 2026, 11:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 24, 2026

Builds and jobs' statuses not updating

Detected by Pingoru
Feb 24, 2026, 09:25 AM UTC
Resolved
Feb 24, 2026, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 24, 2026, 09:25 AM UTC

    Between 6 AM and 8 AM UTC some builds and workflow jobs were not getting their status updated despite VM completing the work. As of 9 AM UTC all the status have been successfully updated.

Read the full incident report →

Minor February 24, 2026

Degraded Android and iOS push notification delivery

Detected by Pingoru
Feb 24, 2026, 04:34 AM UTC
Resolved
Feb 24, 2026, 04:41 AM UTC
Duration
7m
Affected: Push Notifications Broker
Timeline · 2 updates
  1. investigating Feb 24, 2026, 04:34 AM UTC

    We are currently investigating delays in Android and iOS push notification delivery.

  2. resolved Feb 24, 2026, 04:41 AM UTC

    The issue with Android and iOS push notification delivery has been resolved. All queued notifications have been delivered.

Read the full incident report →

Minor February 23, 2026

SSO EAS CLI login failing

Detected by Pingoru
Feb 23, 2026, 08:23 PM UTC
Resolved
Feb 23, 2026, 08:52 PM UTC
Duration
28m
Timeline · 2 updates
  1. identified Feb 23, 2026, 08:23 PM UTC

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

  2. resolved Feb 23, 2026, 08:52 PM UTC

    Updating EAS CLI to >= 18.0.4 should resolve the login issue while we investigate further.

Read the full incident report →

Major February 18, 2026

EAS unavailable during database maintenance

Detected by Pingoru
Feb 18, 2026, 10:15 PM UTC
Resolved
Feb 18, 2026, 10:20 PM UTC
Duration
5m
Affected: EAS BuildWebsiteEAS SubmitDev Tools APIEAS UpdateClassic Update Service (Application Serving API)EAS InsightsPush Notifications BrokerEAS WorkflowsEAS Hosting
Timeline · 2 updates
  1. monitoring Feb 18, 2026, 10:15 PM UTC

    Our cloud provider is doing automatic database maintenance. We will update this status when the maintenance is done and availability is back.

  2. resolved Feb 18, 2026, 10:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026

iOS Builds experiencing dependency installation delays

Detected by Pingoru
Feb 17, 2026, 11:49 PM UTC
Resolved
Feb 18, 2026, 02:25 AM UTC
Duration
2h 36m
Affected: EAS BuildEAS Submit
Timeline · 3 updates
  1. investigating Feb 17, 2026, 11:49 PM UTC

    iOS Builds and Submissions may experience intermittent failures as we investigate certain packages timing out on install

  2. monitoring Feb 18, 2026, 01:33 AM UTC

    We are actively monitoring as iOS builds should no longer experience connection issues

  3. resolved Feb 18, 2026, 02:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 17, 2026

Push notification insights are missing

Detected by Pingoru
Feb 17, 2026, 06:03 PM UTC
Resolved
Feb 21, 2026, 01:24 AM UTC
Duration
3d 7h
Affected: Push Notifications Broker
Timeline · 2 updates
  1. identified Feb 20, 2026, 11:17 PM UTC

    Notifications are being delivered but the insights charts are not being populated. We are working on restoring this functionality.

  2. resolved Feb 21, 2026, 01:24 AM UTC

    Insights charts are receiving data once more as of February 20, 5:10pm PT.

Read the full incident report →

Major February 16, 2026

Workflow jobs failing to start

Detected by Pingoru
Feb 16, 2026, 10:00 AM UTC
Resolved
Feb 16, 2026, 10:21 AM UTC
Duration
21m
Affected: EAS Workflows
Timeline · 3 updates
  1. investigating Feb 16, 2026, 10:00 AM UTC

    Some workflow jobs are failing to get scheduled with "Failed to start the job. Try again."

  2. identified Feb 16, 2026, 10:09 AM UTC

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

  3. resolved Feb 16, 2026, 10:21 AM UTC

    This incident has been resolved.

Read the full incident report →