# Expo: Push notifications not sending (502 error)

> Expo status incident “Push notifications not sending (502 error)” on 2018-01-17: impact none (vendor’s label), 2.1 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/expo/incidents/l3629wy3lrls
Last updated: 2018-01-17T02:55:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2018-01-17 00:48 UTC · Resolved: 2018-01-17 02:55 UTC · Duration: 2.1 h
- Updates: 1
- [Vendor status page: https://status.expo.dev/incidents/l3629wy3lrls](https://status.expo.dev/incidents/l3629wy3lrls)
- [Company: Expo](https://rewindex.com/company/expo.md)

## Timeline of updates

- **resolved** 2018-01-17 02:55 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/expo/incidents/l3629wy3lrls
- Citation: Expo, “Push notifications not sending (502 error)” (2018-01-17 00:48 UTC). Archived by Rewindex: https://rewindex.com/company/expo/incidents/l3629wy3lrls (CC BY 4.0).
- Markdown link: `[Expo: Push notifications not sending (502 error) (2018-01-17)](https://rewindex.com/company/expo/incidents/l3629wy3lrls)`


---
Canonical: https://rewindex.com/company/expo/incidents/l3629wy3lrls · Markdown: https://rewindex.com/company/expo/incidents/l3629wy3lrls.md · JSON: https://rewindex.com/api/v1/companies/expo/incidents/l3629wy3lrls · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:40:02.346Z