- Level
- confirmed
- Worst impact
- Degraded
- Components
- Channels Webhooks
- Regions
- us
What to do
Check whether you use Pusher Channels Webhooks in us. 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 11h 6m it lasted.
Anything that failed between 2024-02-24 02:29 UTC and 2024-02-24 13:35 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
- identified
The issue has been identified and a fix is being implemented.
provider
- identified
We have deployed a fix for this issue. The delivery of the delayed webhooks continues.
provider
- resolved
All delayed US webhooks completed processing at approximately 730 UTC. This incident is 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-6f041f2702
Is Pusher still down?
No, this incident was resolved 2024-02-24 13:35 UTC. For Pusher's live state, see https://down.guide/providers/pusher.
How long did it last?
11h 6m, from 2024-02-24 02:29 UTC to 2024-02-24 13:35 UTC, by the times Pusher posted.
What was affected?
Pusher named Channels Webhooks in us.
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.