Changes / Pusher / MT1 cluster - increased latency
Pusher: Major incident: MT1 cluster - increased latency
Summary
Pusher reported major increased latency on Channels cluster `mt1`, affecting Channels Dashboard, Channels presence channels, Channels REST API and Channels WebSocket client API. It started at 2025-10-20 17:26 UTC and was resolved at 2025-10-21 07:14 UTC, lasting 13 h 48 min. Pusher attributed the latency to an external cloud-provider incident.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
What changed
Before: not present
After: MT1 cluster - increased latency
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2025-10-20 17:26 UTC
Before: not present
After: 2025-10-21 07:14 UTC
Before: not present
After: Channels Dashboard, Channels presence channels, Channels REST API, Channels WebSocket client API
Before: not present
After: 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.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: MT1 cluster - increased latency (this change) Pusher reported major increased latency on Channels cluster `mt1`, affecting Channels Dashboard, Channels presence channels, Channels REST API and Channels WebSocket client API. It started at 2025-10-20 17:26 UTC and was resolved at 2025-10-21 07:14 UTC, lasting 13 h 48 min. Pusher attributed the latency to an external cloud-provider incident. | Major incident |