Pusher: US2 Customers may be experiencing latency issues with or unable to utilize the Channels WebSocket and REST API

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 49m it lasted.
Anything that failed between 2023-12-01 20:31 UTC and 2023-12-01 21:20 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.

investigatingDec 1, 2023, 8:31 PM UTC
We are currently investigating an issue in US2 where some clients may be experiencing latency issues or unable to utilize the Channels WebSocket and REST API.
provider
identifiedDec 1, 2023, 8:46 PM UTC
The team has identified the cause of the latency and are actively working to resolve the high latency issues.
provider
monitoringDec 1, 2023, 8:53 PM UTC
The fix has been implemented and latency has improved.
provider
resolvedDec 1, 2023, 9:20 PM 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 2023-12-01 21:20 UTC. For Pusher's live state, see https://down.guide/pusher.

How long did it last?

49m, from 2023-12-01 20:31 UTC to 2023-12-01 21:20 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.