- Level
- confirmed
- Worst impact
- Degraded
- Components
- Channels REST API
What to do
Check whether you use Pusher Channels REST 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 51m it lasted.
Anything that failed between 2023-11-29 15:17 UTC and 2023-11-29 16:09 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 currently investigating this issue.
provider
- identified
Our engineering team is working on rolling out an improvement to resolve the high latency on the US2 cluster.
provider
- resolved
Our engineering team has confirmed this issue has been mitigated. We apologise for any inconvenience this may have caused you.
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-be5bfe2db7
Is Pusher still down?
No, this incident was resolved 2023-11-29 16:09 UTC. For Pusher's live state, see https://down.guide/pusher.
How long did it last?
51m, from 2023-11-29 15:17 UTC to 2023-11-29 16:09 UTC, by the times Pusher posted.
What was affected?
Pusher named Channels REST 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.