- Level
- confirmed
- Worst impact
- Operational
- Components
- Channels WebSocket client API
What to do
Check whether you use Pusher Channels WebSocket client API. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 9h 40m it lasted.
Anything that failed between 2024-04-05 11:18 UTC and 2024-04-05 20:58 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
- investigating
Customers are seeing high latency on the US2 cluster (WebSockets). The team is working on it.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue. Impact is greatly reduced now. Customers are seeing lower latencies.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-51fbc217e2
Is Pusher still down?
No, this incident was resolved 2024-04-05 20:58 UTC. For Pusher's live state, see https://down.guide/providers/pusher.
How long did it last?
9h 40m, from 2024-04-05 11:18 UTC to 2024-04-05 20:58 UTC, by the times Pusher posted.
What was affected?
Pusher named Channels WebSocket client API.
What caused it?
Pusher hasn't published a root cause. If it does, it shows here.
Where does this come from?
Pusher's official status page, https://status.pusher.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.