rewindex

CompaniesExpoIncidents

Expo: Classic updates not served from expo.io

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.expo.dev (opens in new tab)

Timeline of updates

  1. resolved

    From 5pm Pacific time 9/23 to 8:30 am the following day, request for classic updates manifests made to expo.io would not receive a response containing an update, but an erroneous 404, and therefore the app would not update. Requests to the modern updates service were not effected, nor were other classic updates manifest requests made to exp.host.

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

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

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

Cite this

Status incident (vendor impact label: none) posted by Expo, started 2022-09-24 00:00 UTC, resolved after 0 min, 1 update(s).

Title
Classic updates not served from expo.io
Vendor
Expo
Date
URL
https://rewindex.com/company/expo/incidents/fp9g91zfd1nb

Expo profileRecent Expo incidentsAll outages on September 24, 2022Expo in September 2022MarkdownJSON