Pusher incident: AP1 cluster - Socket connection failures

Affected components

• Channels WebSocket client API
• Channels presence channels

1. resolvedOct 27, 2025, 13:34 UTC

   This incident has been resolved.

2. monitoringOct 27, 2025, 12:53 UTC

   All services are now fully operational. We continue to monitor the cluster.

3. monitoringOct 27, 2025, 12:41 UTC

   We observed unusual activity on the cluster, likely caused by at least one customer experiencing a cyber attack. Our team is mitigating the issue while simultaneously increasing cluster resources to minimize impact on other customers. The cluster availability is returning to normal. We continue to monitor closely.

4. identifiedOct 27, 2025, 12:22 UTC

   A fix is implemented. We are seeing improvements and continue to actively monitor the situation to ensure full stability. During the incident, many clients successfully connected using fallback protocols.

5. investigatingOct 27, 2025, 11:50 UTC

   We are currently experiencing disruptions with socket connections in AP1 cluster, which began at 10:00 UTC. Clients may experience reconnections. Our team is actively investigating the issue and working to restore full connectivity as quickly as possible.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Pusher's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Smartsheet: Brandfolder: SendGrid notifications not processing "Your account was frozen due to unpaid invoices"Major · Oct 27, 2025, 12:51 UTC
• Mux: Investigating elevated playback errors on Chrome version 141.0.7390.123 and laterMinor · Oct 23, 2025, 14:16 UTC

How often does Pusher have incidents?

Pusher reported 0 incidents in the last 90 days. See Pusher's uptime and incident history