Is Expo down?

Last checked 3m ago
Current status
Expo is up

No incidents right now.

  • Official status page: status.expo.io
  • Checked every 5 minutes
  • 35 components tracked

Expo is operational right now. Last checked 3m ago; the most recent incident resolved 7d ago.

Real-time Expo status, recent outages, and incident history: pulled directly from Expo's official status page at status.expo.io every 5 minutes. Pingoru tracks 35 Expo services and has captured 31 incidents in the last 90 days (98.46% uptime). Get email, Slack, Discord, or webhook alerts the moment Expo reports a new incident, free for 3 monitors, no credit card.

Users who monitor Expo also follow these Web Hosting services: Gandi IONOS Germany Shippo FormAssembly Courier EasySpace Appwrite Endless Group Digital Pacific TPP Wholesale View all 8,000+ providers
Expo uptime 98.46% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 52m
    Started Oct 17, 2026, 12:51 AM UTC · Resolved Oct 17, 2026, 01:43 AM UTC
    EAS Submit
    Timeline · 2 updates
    • identified · Oct 17, 2026, 12:51 AM UTC

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

    • resolved · Oct 17, 2026, 01:43 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 2h 37m
    Started Oct 16, 2026, 02:07 PM UTC · Resolved Oct 16, 2026, 04:44 PM UTC
    EAS SubmitApple Developer APIs
    Timeline · 2 updates
    • identified · Oct 16, 2026, 02:07 PM UTC

      We're seeing an increased rate of error response statuses coming from App Store Connect API ("500 Internal Server Error").

    • resolved · Oct 16, 2026, 04:44 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1h 7m
    Started Oct 14, 2026, 02:56 PM UTC · Resolved Oct 14, 2026, 04:04 PM UTC
    EAS BuildEAS Submit
    Timeline · 3 updates
    • identified · Oct 14, 2026, 02:56 PM UTC

      Around 6:30 AM California Time, our API server began experiencing elevated error rates for EAS submissions and build processing. We've identified the issue and are implementing a fix.

    • monitoring · Oct 14, 2026, 03:20 PM UTC

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

    • resolved · Oct 14, 2026, 04:04 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 2h 13m
    Started Oct 05, 2026, 09:08 PM UTC · Resolved Oct 05, 2026, 11:21 PM UTC
    WebsiteDev Tools APIPush Notifications Broker
    Timeline · 3 updates
    • investigating · Oct 05, 2026, 09:08 PM UTC

      We're experiencing an elevated level of API errors and are currently looking into the issue.

    • monitoring · Oct 05, 2026, 09:15 PM UTC

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

    • resolved · Oct 05, 2026, 11:21 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved –
    Started Oct 05, 2026, 08:11 PM UTC · Resolved Oct 05, 2026, 08:11 PM UTC
    Timeline · 2 updates
    • resolved · Oct 05, 2026, 08:38 PM UTC

      Due to high database load, the Expo website and several services including submitting CI/CD jobs, build jobs, and store submissions were partially unavailable. The issue has subsided as of 1:30PM PT and we are continuing to diagnose the root cause and monitor the health of the services.

    • postmortem · Oct 05, 2026, 08:40 PM UTC

      The primary database was under high CPU load from 1:11PM-1:29PM PT. The impact of this is that our website and API were partially unavailable \(more precisely, at 80-90% availability\) during that time. ### Scope What was affected: This affected most services including the website, builds, submissions, CI/CD jobs, and publishing updates. What wasn’t affected: Serving updates to end users maintained 100.000% availability. App performance measurements sent to Observe were also unaffected. ### Root cause analysis An internal orchestrator service used to update the state of CI/CD jobs, including build jobs and store submission jobs, was updated to retry upon application-level failures. We are investigating more thoroughly and currently believe this led to a cascade of retries that caused more failures once the database was under more load than it could handle. ### Remediation The commit that changed retry behavior was rolled back and we are clearing the queue of retries. For a more robust solution, the internal orchestrator must gracefully handle backpressure from the application server and database, and to apply more backoff.

    Latest: The primary database was under high CPU load from 1:11PM-1:29PM PT. The impact of this is that our website and API were partially unavailable \(more precisely, at 80-90% availabili…

See the full Expo outage history

24 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Expo outage history →

Or sign up free to get alerts when Expo breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 35 components checked every 5 minutes
116incidents recorded
113last 12 months
29last 90 days
4 hourstypical duration, 12 months

The longest incident in the last year, Push notification insights are missing on February 17, 2026, ran for 3 days. 6 maintenance windows announced in the same period.

Most affected components, last 12 months

  • EAS Build38
  • EAS Submit37
  • EAS Workflows29
  • EAS Update12
  • Push Notifications Broker12

Latest incidents

Outage history

Past 90 days · 29 incidents View full outage history →