High Latency in US2 on Channels WebSocket Client API

What to do

• Check whether you use Pusher Channels WebSocket client API. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 15h 9m it lasted.

  Anything that failed between 2024-04-04 19:13 UTC and 2024-04-05 10:22 UTC may need a replay.

• Subscribe to Pusher's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pusher works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pusher 6

1. investigatingApr 4, 2024, 7:13 PM UTC

   We are currently investigating an issue with high latency in US2 on the Channels WebSocket Client API

   provider

2. monitoringApr 4, 2024, 7:49 PM UTC

   A fix has been implemented and the latency issues have resolved in US2. We will monitor the systems to ensure the issue does not reoccur.

   provider

3. identifiedApr 4, 2024, 8:23 PM UTC

   Issues with US2 have returned. We are seeing issues maintaining connections.

   provider

4. identifiedApr 4, 2024, 8:52 PM UTC

   We are continuing to investigate issues with users unable to establish connections from the Websocket Client.

   provider

5. monitoringApr 5, 2024, 1:28 AM UTC

   A fix for this issue has been deployed and we are monitoring the system.

   provider

6. resolvedApr 5, 2024, 10:22 AM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.