Skip to main content
Vendor reliability

Vendor record

Expo

Vendor reports Operational

Checked

Front door check counts and Expo’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Expo endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.expo.dev
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Expo product, region or your app worked.

How we count front door checks

Expo says

Incident posts from Expo’s status page, with its titles, impact levels and times. They say what Expo chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

7

incidents Expo posted, last 30 days

Median recorded duration: 2h 37m. From 7 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Elevated iOS submission error rates

    Major

    Started, per Expo

    Closed in our record(2h 37m)

    Expo’s post

  • Elevated API server error rates affecting submissions and builds

    Minor

    Started, per Expo

    Closed in our record(1h 13m)

    Expo’s post

  • Website and services partially unavailable due to high database load

    Minor

    Started, per Expo

    Closed in our record(2h 21m)

    Expo’s post

  • EAS Update cache issue for rollout updates

    Minor

    Started, per Expo

    Closed in our record(3h 42m)

    Expo’s post

  • Elevated rate of failed iOS submissions

    Major

    Started, per Expo

    Closed in our record(9h 31m)

    Expo’s post
15 older records

  • Elevated rate of failed iOS submissions

    Major

    Started, per Expo

    Closed in our record(23m)

    Expo’s post

  • Elevated queue times for Android Builds, Submissions, and Workflows

    Minor

    Started, per Expo

    Closed in our record(2h 56m)

    Expo’s post

  • iOS push notification degraded performance

    Minor

    Started, per Expo

    Closed in our record(1d)

    Expo’s post

  • Delayed iOS push notification delivery

    Minor

    Started, per Expo

    Closed in our record(1h 1m)

    Expo’s post

  • Delayed and failed submissions due to issues with build artifacts

    Minor

    Started, per Expo

    Closed in our record(4h 37m)

    Expo’s post

  • Elevated Linux worker queue times

    Major

    Started, per Expo

    Closed in our record(15h 9m)

    Expo’s post

  • Degraded performance on the NPM registry

    Minor

    Started, per Expo

    Closed in our record(14h 50m)

    Expo’s post

  • Elevated Android builds rate

    Major

    Started, per Expo

    Closed in our record(30m)

    Expo’s post

  • Elevated Linux worker queue times

    Minor

    Started, per Expo

    Closed in our record(1h 45m)

    Expo’s post

  • Problems with API and website availability

    Minor

    Started, per Expo

    Closed in our record(3h 28m)

    Expo’s post

  • EAS background operations availability issues

    Minor

    Started, per Expo

    Closed in our record(1h 4m)

    Expo’s post

  • iOS submissions failing on upload to App Store Connect

    Minor

    Started, per Expo

    Closed in our record(3h 39m)

    Expo’s post

  • iOS Submissions hanging on App Store Connect build uploads

    Minor

    Started, per Expo

    Closed in our record(12h 5m)

    Expo’s post

  • iOS Submissions hanging on App Store Connect build uploads

    Minor

    Started, per Expo

    Closed in our record(1h 58m)

    Expo’s post

  • EAS CLI broken in some workflows

    Minor

    Started, per Expo

    Closed in our record(2h 35m)

    Expo’s post

Your code, your dependencies

See which of your code paths call Expo

Connect GitHub or GitLab to find where your public or private repository uses Expo. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Expo status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · ExpoStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/expo?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Expo status badge"></iframe>

Frequently Asked Questions

Is Expo currently down?

Expo's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Expo last have an outage?

The most recent closed incident record began earlier today and spans 2h 37m. The vendor reported a partial outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Expo?

No. CheckUpstream checks Expo’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Expo in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Expo?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.

Related vendors