Pusher: Intermittent API errors in US2 cluster

What to do

Check whether you use Pusher 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 1h 4m it lasted.
Anything that failed between 2026-04-06 01:52 UTC and 2026-04-06 02:55 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.

investigatingApr 6, 2026, 1:52 AM UTC
We are currently investigating an issue with intermittent errors for the Channels API in US2 cluster.
provider
identifiedApr 6, 2026, 2:01 AM UTC
The issue has been identified and a fix is being implemented.
provider
monitoringApr 6, 2026, 2:32 AM UTC
A fix has been implemented and we are monitoring the results.
provider
resolvedApr 6, 2026, 2:55 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Pusher still down?

No, this incident was resolved 2026-04-06 02:55 UTC. For Pusher's live state, see https://down.guide/pusher.

How long did it last?

1h 4m, from 2026-04-06 01:52 UTC to 2026-04-06 02:55 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.