Expo: Push notifications not sending (502 error)
Timeline of updates
- resolved
We've deployed a change to the Expo servers that fixes an issue with larger queues of push notifications that could cause them not to be processed and to time out. We believe this will fix a significant source of 502 errors on the push notification endpoint. As a proactive follow-up, we will also add further timeout detection and handling.
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 2018-01-17 00:48 UTC, resolved after 2.1 h, 1 update(s).
- Title
- Push notifications not sending (502 error)
- Vendor
- Expo
- Date
- URL
- https://rewindex.com/company/expo/incidents/l3629wy3lrls
Expo profileRecent Expo incidentsAll outages on January 17, 2018Expo in January 2018MarkdownJSON