Is Expo Down?

No — Expo is up

Reachable from all 8 checked regions

Average response time: 315ms

Last checked 19 minutes ago · checks run every 6 hours

Official status page: https://status.expo.dev

Expo uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

350ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

21-day clean streak

Sep 14 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

iad

250ms

DNS 49ms TCP 14ms TLS 27ms TTFB 208ms

jnb

589ms

DNS 205ms TCP 1ms TLS 7ms TTFB 510ms

lax

280ms

DNS 104ms TCP 1ms TLS 10ms TTFB 267ms

lhr

217ms

DNS 17ms TCP 2ms TLS 10ms TTFB 183ms

nrt

211ms

DNS 10ms TCP 1ms TLS 11ms TTFB 206ms

ord

288ms

DNS 109ms TCP 2ms TLS 10ms TTFB 280ms

sin

413ms

DNS 51ms TCP 1ms TLS 10ms TTFB 336ms

sjc

276ms

DNS 70ms TCP 13ms TLS 21ms TTFB 227ms

What Expo does

Expo is the framework and cloud service many teams use to ship React Native apps. Its Expo Application Services build iOS and Android binaries, submit them to the app stores and push over-the-air JavaScript updates to apps already installed, so it sits between a team's repository and every phone running their app.

What an outage looks like

EAS Build jobs sit queued or fail partway without a code change on your side. Submissions to the App Store or Google Play stall. Publishing an EAS Update errors out, or the update never reaches devices. Push notifications sent through Expo's broker are delayed. The expo.dev dashboard may load while builds behind it are stuck, because the website is reported separately.

What to do about it

Check status.expo.dev, which lists EAS Build, Submit, Update, Insights, Workflows and Hosting as separate rows, plus a Third-Party Services group covering GitHub, Google Cloud, AWS S3, Apple Developer APIs and Cloudflare. If only a third-party row is degraded, the cause sits upstream. Do not re-trigger a stuck build repeatedly; each retry joins the same queue.

Is it down for everyone, or just you?

If this page says Expo is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Expo outage FAQ

Do installed apps break if EAS Update is down?

No. Expo's own documentation says an app that cannot fetch an update runs the newest update it already downloaded, and falls back to the bundle embedded at build time if it has none. So users keep a working app. What stops is delivery of new fixes, which means an urgent patch published during the incident may not reach anyone until the service recovers.

Why is my EAS build failing when my code has not changed?

Builds depend on more than Expo. The status page tracks GitHub, Google Cloud, AWS S3, Apple Developer APIs and Cloudflare as Third-Party Services, and a problem in any of them can fail a build that worked yesterday. Check that group before debugging your own configuration, and compare against a colleague's build on a different project.

Is Expo down or is it the App Store?

Look at EAS Submit and the Apple Developer APIs row separately. EAS Submit is Expo's upload service; Apple's APIs are what it talks to. If Submit is healthy and the Apple row is degraded, the delay is on Apple's side and resubmitting from Expo will not help. Waiting for the upstream row to clear is usually faster.

Does an Expo outage affect push notifications?

It can. The Push Notifications Broker is its own component on the status page, and apps using Expo's push service send through it rather than directly to Apple and Google. Notifications may arrive late or not at all while it is degraded. Apps that call Apple and Google push services directly are not affected by that row.

Can I still build locally while EAS is down?

Usually, yes. Expo projects can be built on your own machine with the native toolchains, which does not depend on EAS Build's queue. That is slower to set up if you have never done it, so it is most useful when a release cannot wait. Over-the-air updates and store submission through EAS still need the service.

How we measure this

We request Expo's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Expo publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Expo goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required