Pusher: MT1 cluster - increased latency

What to do

Check whether you use Pusher Channels REST API, Channels WebSocket client API, Channels Dashboard, 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 13h 49m it lasted.
Anything that failed between 2025-10-20 17:26 UTC and 2025-10-21 07:14 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.

investigatingOct 20, 2025, 5:26 PM UTC
Our cloud provider is currently experiencing an incident that's causing increased latency on Pusher Channels main cluster `mt1` . This issue is external to our systems and is not related to our infrastructure. Our team is actively investigating to determine if there are any additional impacts and working to minimize downstream effects while our provider implements a fix.
provider
resolvedOct 21, 2025, 7:14 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 2025-10-21 07:14 UTC. For Pusher's live state, see https://down.guide/pusher.

How long did it last?

13h 49m, from 2025-10-20 17:26 UTC to 2025-10-21 07:14 UTC, by the times Pusher posted.

What was affected?

Pusher named Channels REST API, Channels WebSocket client API, Channels Dashboard, 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.