Skip to content
Expo · Developer toolsApr 30, 2026, 20:13 UTC

Users unable to authenticate with Expo Go (404)

MinorBugUpdated 19h ago
Apr 30, 20:13 UTCApr 30, 20:13 UTC
Duration
0m
Impact
Minor
Root cause
Bug
Expo, 90 days
32 incidents
Affected
Not listed by the vendor.
Status page

Final update

Users received a 404 error when attempting to authenticate with Expo Go due to a server-side bug that wrongly overwrote the HTTP status code on one of our GraphQL endpoints. This has been fixed.

Timeline

  1. Resolved · Apr 30, 20:13 UTC
    Users received a 404 error when attempting to authenticate with Expo Go due to a server-side bug that wrongly overwrote the HTTP status code on one of our GraphQL endpoints. This has been fixed.

More from Expo

Full history
StartedIncidentDuration
Sep 2323:37 UTCEAS Update cache issue for rollout updates3h 34m
Sep 2121:18 UTCElevated rate of failed iOS submissions9h 24m
Sep 2120:26 UTCElevated rate of failed iOS submissions14m
Sep 1812:43 UTCElevated queue times for Android Builds, Submissions, and Workflows2h 48m
Sep 814:42 UTCiOS push notification degraded performance4h 41m
Sep 515:38 UTCDelayed iOS push notification delivery1h 1m

Also caused by software bug

All
StartedIncidentDuration
Sep 1518:57 UTCClickPipes failing on Kinesis in AWS us-east-1ClickHouse29h 46m
Sep 318:20 UTCRetroactive Incident: Twilio Personalized Support Phone Line AffectedTwilio0m
Aug 819:48 UTCAlerting expressions pipeline failing when recovery settingsGrafana Labs0m
Aug 615:22 UTCIncident with ActionsGitHub10h 42m
Jul 2314:14 UTC[Medium] Issues with Box HubsBox16m
Jun 1719:00 UTCIncident With WebhooksGitHub0m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.