rewindex

CompaniesExpoIncidents

Expo: expo start 400 error

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

Timeline of updates

  1. resolved

    A bad validation scheme was deployed resulting in the 400 errors when running expo start.

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 2020-01-14 20:30 UTC, resolved after 0 min, 1 update(s).

Title
expo start 400 error
Vendor
Expo
Date
URL
https://rewindex.com/company/expo/incidents/827s5hv1st2z

Expo profileRecent Expo incidentsAll outages on January 14, 2020Expo in January 2020MarkdownJSON