Push notifications not sending (502 error)

Incident Report for Expo

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.

Posted Jan 16, 2018 - 18:55 PST

Identified

We've taken actions which have greatly reduced the rate of errors, and have also identified a likely underlying cause. We are deploying a fix for that cause now.

Posted Jan 16, 2018 - 18:19 PST

Investigating

Sending push notifications through the Expo push notification service currently results in HTTP 502 errors. The Expo team is looking into this issue.

Posted Jan 16, 2018 - 16:48 PST