Pusher Outage History

26 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Pusher status100.00% uptime history

Every Recorded Pusher Incident

Pusher incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 23, 2026Elevated Errors on us2This incident has been resolved.3h 44mResolved
Aug 22, 2026Elevated errors on us2 clusterThis incident has been resolved.1h 30mResolved
Apr 6, 2026Intermittent API errors in US2 clusterThis incident has been resolved.1h 3mResolved
Mar 31, 2026Cluster SA1: Delayed Channels webhook delivery on SA1 clusterThis incident has been resolved.11 minResolved
Mar 15, 2026Maintenance on cluster US3The scheduled maintenance has been completed.30 minScheduled
Feb 15, 2026Increased error rate on the US2 clusterThis incident has been resolved.1h 40mResolved
Feb 6, 2026Maintenance on the Channels US3 clusterThe scheduled maintenance has been completed.4h 0mScheduled
Feb 5, 2026Maintenance on the Channels US3 clusterThe scheduled maintenance has been completed.5h 0mScheduled
Jan 29, 2026Errors increase for API in cluster us3This incident has been resolved.20 minResolved
Jan 26, 2026Increased error rate on the US2 cluster impacting presence eventsThis incident has been resolved.14 minResolved
Jan 22, 2026Incorrect subscription changes affecting some accountsAll affected accounts have been restored to their correct subscription levels. We sent an email yesterday to all impacted customers. If you notice any issues with your subscription, please contact us.19h 20mResolved
Jan 16, 2026Intermittent errors with message delivery on cluster us2This incident has been resolved.3h 52mResolved
Jan 16, 2026Intermittent errors with message deliveryThis incident has been resolved.30 minResolved
Jan 14, 2026Maintenance on Pusher Channels Stats IntegrationThe scheduled maintenance has been completed.4h 0mScheduled
Jan 8, 2026Maintenance on Pusher Channels Stats IntegrationThe scheduled maintenance has been completed.3h 0mScheduled
Dec 16, 2025Maintenance on Pusher Channels Stats IntegrationThe scheduled maintenance has been completed.5h 0mScheduled
Dec 15, 2025Maintenance on Pusher Channels Stats IntegrationThe scheduled maintenance has been completed.17h 0mScheduled
Oct 27, 2025AP1 cluster - Socket connection failuresThis incident has been resolved.1h 44mResolved
Oct 21, 2025Elevated API Errors in AP4 Cluster## **Root Cause Analysis: Elevated API Errors and Outage in AP4 Cluster** **Incident Date:** October 20, 2025 **Status:** Resolved ### **Summary** Between **October 20 and October 21, 2025**, customers using the…2h 36mResolved
Oct 20, 2025US3 cluster - major outage## Root Cause Analysis: Redis Cluster Startup Failures – US3 Cluster **Incident Date:** October 20, 2025 **Duration:** 18:36 UTC – 20:41 UTC **Status:** Resolved ## **Summary** On October 20, 2025, customers…2h 5mResolved
Oct 20, 2025MT1 cluster - increased latencyThis incident has been resolved.13h 48mResolved
Oct 20, 2025Pusher Beams degradationThis incident has been resolved.13h 51mResolved
Oct 20, 2025Beams - webhook delivery issuesOur cloud provider is reporting recovery across most affected services. On our side, we haven’t noticed any issues in the past hour, and all services are operating normally. We continue to monitor the situation closely…1h 58mResolved
Oct 20, 2025MT1 cluster - increased latency and webhook delivery failuresThis incident has been resolved.4h 46mResolved
Oct 19, 2025Increased latency - US2 cluster## **Root Cause Analysis: Increased Latency and Message Delivery Failures – US2 Cluster** **Incident Date:** October 19, 2025 **Duration:** 00:44 UTC – 08:17 UTC **Status:** Resolved ### **Summary** On October 19…7h 32mResolved
Sep 19, 2025Higher latency on our AP1 cluster for some customersThis incident has been resolved.34h 39mResolved

How to Read This Pusher Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Pusher acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Pusher outage in this window ran 1d 10h, against a mean recovery of 5h 55m. If you depend on Pusher in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.