- Level
- confirmed
- Worst impact
- Operational
- Components
- Channels REST API, Channels WebSocket client API, Channels presence channels
What to do
Check whether you use Pusher Channels REST API, Channels WebSocket client API, Channels presence channels. 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 1h 31m it lasted.
Anything that failed between 2026-08-22 03:17 UTC and 2026-08-22 04:47 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 3
- investigating
We are investigating an increased error rate affecting the us2 cluster. All services remain operational, but a subset of customers may experience intermittent issues.
provider
- monitoring
A fix has been implemented, and we are monitoring the results. All publish requests are now succeeding.
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-737601e4a6
Is Pusher still down?
No, this incident was resolved 2026-08-22 04:47 UTC. For Pusher's live state, see https://down.guide/providers/pusher.
How long did it last?
1h 31m, from 2026-08-22 03:17 UTC to 2026-08-22 04:47 UTC, by the times Pusher posted.
What was affected?
Pusher named Channels REST API, Channels WebSocket client API, Channels presence channels.
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.