- Level
- confirmed
- Worst impact
- Degraded
- Components
- Channels REST API, Channels WebSocket client API
- Down Index
- 18of 100
What to do
Check whether you use Pusher Channels REST API, 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 14m it lasted.
Anything that failed between 2024-09-16 14:23 UTC and 2024-09-16 14:37 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 2
- investigating
We are currently investigating this issue.
provider
- resolved
This incident has been resolved. The team saw similarities with a previous incident that affected the US2 cluster and acted swiftly to mitigate and prevent further impact. Overall the impact was very small: a few connections saw small delays receiving messages for a very short time.
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-c8e0f52e74
Is Pusher still down?
No, this incident was resolved 2024-09-16 14:37 UTC. For Pusher's live state, see https://down.guide/pusher.
How long did it last?
14m, from 2024-09-16 14:23 UTC to 2024-09-16 14:37 UTC, by the times Pusher posted.
What was affected?
Pusher named Channels REST API, 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.