- 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 2h 11m it lasted.
Anything that failed between 2024-02-22 22:24 UTC and 2024-02-23 00:36 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 4
- investigating
Pusher US3 cluster is experiencing disruptions for client socket connections. Our team is looking into it.
provider
- identified
The team identified the problem. Most connections are stable now but some of them may get reconnected still. The team is working on a permenant solution.
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-a5e7945b7a
Is Pusher still down?
No, this incident was resolved 2024-02-23 00:36 UTC. For Pusher's live state, see https://down.guide/providers/pusher.
How long did it last?
2h 11m, from 2024-02-22 22:24 UTC to 2024-02-23 00:36 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.