https://approjects-vendor-status-watch.static.hf.space/v/pusher.htmlIncidents from Pusher's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/zwqg1pjx8hfypusher:2026-08-23T01:27:50.123ZSun, 23 Aug 2026 01:27:50 +0000This incident has been resolved.https://stspg.io/7bnbcgkbhdklpusher:2026-08-22T03:17:10.408ZSat, 22 Aug 2026 03:17:10 +0000This incident has been resolved.https://stspg.io/80bmtqwc23fbpusher:2026-04-06T01:52:05.304ZMon, 06 Apr 2026 01:52:05 +0000This incident has been resolved.https://stspg.io/mh5dx011mv9xpusher:2026-03-31T12:33:28.286ZTue, 31 Mar 2026 12:33:28 +0000This incident has been resolved.https://stspg.io/0rv44htxtw4npusher:2026-02-15T20:33:40.188ZSun, 15 Feb 2026 20:33:40 +0000This incident has been resolved.https://stspg.io/89k2khjnhry9pusher:2026-01-29T10:38:02.971ZThu, 29 Jan 2026 10:38:02 +0000This incident has been resolved.https://stspg.io/b3420jvz2lk3pusher:2026-01-26T22:29:04.676ZMon, 26 Jan 2026 22:29:04 +0000This incident has been resolved.https://stspg.io/12sq01t39cdcpusher:2026-01-22T16:38:00.329ZThu, 22 Jan 2026 16:38:00 +0000All 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.https://stspg.io/9cw9jg93w3wtpusher:2026-01-16T08:48:53.259ZFri, 16 Jan 2026 08:48:53 +0000This incident has been resolved.https://stspg.io/hvmt3rcbnyfbpusher:2026-01-16T01:07:12.399ZFri, 16 Jan 2026 01:07:12 +0000This incident has been resolved.https://stspg.io/kcbvc21rrbh3pusher:2025-10-27T11:50:02.599ZMon, 27 Oct 2025 11:50:02 +0000This incident has been resolved.https://stspg.io/zcbl5knddsk2pusher:2025-10-21T15:06:39.819ZTue, 21 Oct 2025 15:06:39 +0000## **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 **AP4 cluster** experienced elevated API errors, latency, and message publishing failures. The issue primarily affected the **Channels API**, preventing customers from publishing new messages and leading to degraded real-time functionality for end-users. During system recovery and while implementing mitigations from a previous incident on Oct 18th, a **misconfigured Redis container** in the AP4 cluster failed to start correctly, preventing caching operations needed for API requests. This misconfiguration went undetected by proactive monitoring, delaying full recovery until Octhttps://stspg.io/dcfktz1mqkpspusher:2025-10-20T18:36:06.632ZMon, 20 Oct 2025 18:36:06 +0000## 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 experienced a significant outage affecting the US3 cluster. The disruption began with increased latency and 503 errors before escalating into full service downtime as Redis clusters in the US3 region failed to start successfully during an infrastructure update. Service was fully restored at 20:41 UTC after engineers identified and resolved the underlying startup issue, confirming stability across all Redis clusters. ## **Impact** Between **18:36 UTC and 20:41 UTC**, customers experienced: * Major outage in the **US3** cluster, impacting message delivery and connection rhttps://stspg.io/vth06sd5l50vpusher:2025-10-20T17:26:18.885ZMon, 20 Oct 2025 17:26:18 +0000This incident has been resolved.https://stspg.io/732gkz4w3x45pusher:2025-10-20T17:21:26.390ZMon, 20 Oct 2025 17:21:26 +0000This incident has been resolved.https://stspg.io/nt3cyt19x0cypusher:2025-10-20T08:19:49.127ZMon, 20 Oct 2025 08:19:49 +0000Our 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 and will provide updates if anything changes.https://stspg.io/8ww72kngbflvpusher:2025-10-20T08:10:37.068ZMon, 20 Oct 2025 08:10:37 +0000This incident has been resolved.https://stspg.io/cqw0hdd2dqmypusher:2025-10-19T00:44:46.098ZSun, 19 Oct 2025 00:44:46 +0000## **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, 2025, customers using Pusher experienced increased latency and message delivery failures. These issues primarily affected the US2 cluster, with intermittent impact also observed in the MT1 and US3 clusters.  The incident resulted in delayed or undelivered messages for many applications. Latency stabilized at 08:17 UTC after mitigation actions were completed. ### **Impact** Between 00:44 UTC and 08:17 UTC, multiple customers experienced: * **Delayed or failed message delivery** across affected clusters * **Degraded performance** in connection establishment and publishing https://stspg.io/7p71ldc2pzznpusher:2025-09-19T21:15:37.686ZFri, 19 Sep 2025 21:15:37 +0000This incident has been resolved.