CheckUpstream measured Expo at 100.000% availability across 2029 independent checks (global · api). 48 incidents were recorded in the past 12 months; the most recent resolved 5 days ago after 4 hours. Status signals are polled from Expo's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2029 · p95 390ms (30d)
Share of our own checks against Expo endpoints that returned Expo's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 10 incidents · 27 of 30 days with none posted · 2h 6m of declared impact
Fewer incidents in the last 30 days than 9% of 232 tracked services.
Share of each window with no impact declared by Expo
7d
100.000%
30d
99.707%
90d
99.683%
180d
98.722%
1y
99.370%
Downtime like this can be refundable
If you're a paying Expo customer, outages in these windows may count against Expo's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Expo entitlement →Does Expo actually matter to you?
A Expo outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 10 incidents Expo published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Expo takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 26, 15:51 UTC · resolved in 3h 39m · Resolved
Aug 18, 16:25 UTC · resolved in 12h 5m · Resolved
Aug 17, 21:12 UTC · resolved in 1h 58m · Resolved
Live Expo status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/expo)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Expo is currently Operational. CheckUpstream tracks Expo in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Expo's last resolved incident started 5 days ago and lasted 3h 39m (degraded performance).
Looking for the live "is Expo down" view? See the Expo Live status page.
Aug 14, 17:04 UTC · resolved in 2h 35m · Resolved
Jul 30, 06:19 UTC · resolved in 26m · Resolved
Jul 26, 23:22 UTC · resolved in 1h 37m · Resolved
Jul 14, 21:17 UTC · resolved in 3h 52m · Resolved
Jul 10, 13:18 UTC · resolved in 21m · Resolved
Jul 8, 20:50 UTC · resolved in 40m · Resolved
Jun 29, 15:28 UTC · resolved in 15m · Resolved
Jun 29, 15:14 UTC · resolved in 16m · Resolved
Jun 25, 01:35 UTC · resolved in 2h 40m · Resolved
Jun 23, 17:28 UTC · resolved in 2h 22m · Resolved
Jun 19, 09:02 UTC · resolved in 17m · Resolved
Expo's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Expo endpoints. It is the share of checks that returned the expected response, not a figure taken from Expo's status page.
Sign up to CheckUpstream and add Expo to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Expo's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.