Rewindex

CompaniesExpoIncidents

Expo: Disruption due to an upstream provider outage

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.expo.dev (opens in new tab)
Part of an outage event

Cloudflare outage, Dec 5, 2025 · 46 vendors, 46 incidents

Expo’s incident blames Cloudflare as the cause. (hop 1, posted +13 min vs the first vendor naming Cloudflare)

“…bout 10 minutes and manifested in expo.dev returning a 500 when accessed. This was due to Cloudflare Service Issues which have since been resolved. See https://www.cloudflarestatus.com/ for more detai…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamed CloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingExpo (this incident)posted +13 min
Cloudflareown incident not archivedWithin an hour18 vendors, 18 blamedCloudflareUnbounce, Expo, GitLab +151 to 4 hours later1 vendor, 1 blamed CloudflareKlaviyoLater2 vendors, 2 blamed CloudflareBitrise, Sigma ComputingExpo (this incident)posted +13 min
Expo is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>18 vendors, 18 blamed Cloudflare<br/>Unbounce, Expo, GitLab +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed Cloudflare<br/>Klaviyo"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed Cloudflare<br/>Bitrise, Sigma Computing"]:::blames
  root --> later
  me["Expo (this incident)<br/>posted +13 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    The outage lasted about 10 minutes and manifested in expo.dev returning a 500 when accessed. This was due to Cloudflare Service Issues which have since been resolved. See https://www.cloudflarestatus.com/ for more details.

From Expo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on status.expo.dev (opens in new tab).

Expo profileRecent Expo incidentsMarkdownJSON