Pusher

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-23 01:27 UTC

   We are seeing unusual traffic on the us2 cluster that is affecting a subset of traffic. The impact is limited to certain requests, while the majority of traffic continues to operate normally. We are actively investigating the cause and working to mitigate the impact.

2. investigating 2026-08-23 02:03 UTC

   We are seeing short but frequent spikes in errors affecting a small subset of traffic on the us2 cluster. The impact is intermittent and varies across customers, with the vast majority of customers experiencing no impact. Our systems have automatically scaled capacity in...

3. resolved 2026-08-23 05:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API, Channels presence channels

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-22 03:17 UTC

   We are investigating an increased error rate affecting the us2 cluster. All services remain operational, but a subset of customers may experience intermittent issues.

2. monitoring 2026-08-22 03:32 UTC

   A fix has been implemented, and we are monitoring the results. All publish requests are now succeeding.

3. resolved 2026-08-22 04:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-06 01:52 UTC

   We are currently investigating an issue with intermittent errors for the Channels API in US2 cluster.

2. identified 2026-04-06 02:01 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-06 02:32 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-06 02:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-03-31 12:33 UTC

   Customers on the SA1 cluster may have experienced delayed or missed webhook deliveries, including cache channel webhooks.

2. monitoring 2026-03-31 12:42 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-31 12:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-15 20:33 UTC

   We are currently investigating this issue.

2. monitoring 2026-02-15 21:38 UTC

   The fix has been implemented and we are monitoring the results. The issue affected only part of the cluster traffic. All services are currently operational

3. resolved 2026-02-15 22:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-29 10:38 UTC

   We are currently investigating the issue with increased error rate for the Channels API in cluster us3

2. monitoring 2026-01-29 10:55 UTC

   A fix has been implemented and we are monitoring the situation

3. resolved 2026-01-29 10:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels presence channels, Channels Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-26 22:29 UTC

   We are currently investigating this issue.

2. resolved 2026-01-26 22:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels Webhooks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-01-22 16:38 UTC

   We’ve been made aware of an issue caused by our billing provider, Maxio, where a limited number of our customer accounts were incorrectly downgraded due to an incident on their side. We are actively working with Maxio to restore all affected accounts to their correct...

2. resolved 2026-01-23 11:58 UTC

   All 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.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels presence channels

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-16 08:48 UTC

   We are currently investigating this issue.

2. identified 2026-01-16 10:56 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-01-16 11:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-01-16 12:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API, Channels presence channels

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-16 01:07 UTC

   We are currently investigating this issue.

2. monitoring 2026-01-16 01:16 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-01-16 01:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API, Channels presence channels

Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-27 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.

2. identified 2025-10-27 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.

3. monitoring 2025-10-27 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...

4. monitoring 2025-10-27 12:53 UTC

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

5. resolved 2025-10-27 13:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API, Channels Stats Integrations

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-21 15:06 UTC

   We're experiencing an elevated level of API errors and latency in AP4 and are currently looking into the issue.

2. identified 2025-10-21 15:09 UTC

   The team has identified the issue with one of our backend caching servers. The team is working to restore the connections to the server.

3. identified 2025-10-21 15:27 UTC

   The team continues to make progress restoring the cache services. We anticipate full resolution in the next 10-15 minutes.

4. monitoring 2025-10-21 15:29 UTC

   A fix has been implemented and we are monitoring. The cluster will take a few more minutes to fully stabilize across all nodes.

5. identified 2025-10-21 17:32 UTC

   We are currently investigating an issue affecting the Channels API. A large number of customers may be unable to publish new messages through the API in the AP4 cluster.

6. monitoring 2025-10-21 17:39 UTC

   A fix has been implemented and we are monitoring the results.

7. resolved 2025-10-21 17:43 UTC

   This incident has been resolved.

8. postmortem 2025-10-23 14:12 UTC

   ## **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...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API, Channels presence channels

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-20 18:36 UTC

   We're seeing an increased latency and a number of 503 errors on us3 cluster. The team is investigating.

2. investigating 2025-10-20 19:01 UTC

   We are continuing to investigate this issue.

3. identified 2025-10-20 19:01 UTC

   We are continuing to investigate this issue.

4. identified 2025-10-20 19:04 UTC

   We are currently experiencing a major outage in US3 cluster. Our engineering team is actively working to restore full functionality as quickly as possible. In the meantime, we recommend customers temporarily switch to an alternative cluster to minimize service disruption.

5. identified 2025-10-20 19:59 UTC

   Our team has identified the root cause of the issue and implemented a fix. The affected cluster is now in the process of recovering, and performance is gradually returning to normal. We will continue to closely monitor the situation until full recovery is confirmed.

6. monitoring 2025-10-20 20:20 UTC

   All services are now fully operational. Our team continues to monitor the system closely to ensure ongoing stability and performance.

7. resolved 2025-10-20 20:41 UTC

   This incident has been resolved.

8. postmortem 2025-11-03 20:04 UTC

   ## 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...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API, Channels Dashboard, Channels presence channels

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 17:26 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...

2. resolved 2025-10-21 07:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Beams

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 17:21 UTC

   Our cloud provider is currently experiencing an incident that's affecting Pusher Beams operations. 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...

2. resolved 2025-10-21 07:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Beams

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 08:19 UTC

   Our cloud provider is currently experiencing an incident affecting webhook deliveries in Beams. This issue is external to our infrastructure and is limited to webhooks. Other Beams functionality remains operational. Our team is actively investigating to identify any additional...

2. monitoring 2025-10-20 09:34 UTC

   The impact on our services is decreasing and we have not observed any additional issues with other services. We continue to monitor the situation closely.

3. resolved 2025-10-20 10:18 UTC

   Our 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.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-20 08:10 UTC

   Our cloud provider is currently experiencing an incident that's causing increased latency and webhook delivery failures. 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...

2. monitoring 2025-10-20 09:33 UTC

   The impact on our services is decreasing and we have not observed any additional issues with other services. We continue to monitor the situation closely.

3. monitoring 2025-10-20 10:17 UTC

   Our 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.

4. resolved 2025-10-20 12:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API, Channels presence channels

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-19 00:44 UTC

   Increased latency and degraded performance on clusters main, us2 and us3.

2. identified 2025-10-19 03:11 UTC

   The issue has been identified and we are applying mitigations. We are seeing improved latency in main and us3 clusters. us2 still has elevated latency.

3. identified 2025-10-19 04:03 UTC

   We have scaled all three clusters out to handle the increased traffic. We anticipate the latency to slowly improve.

4. resolved 2025-10-19 08:17 UTC

   Latency has remained stable over the past three hours. Our investigation identified multiple contributing factors to the earlier latency increase, including network saturation and capacity limits at our cloud providers affecting the US2 cluster. The US3 cluster issue was...

5. postmortem 2025-10-23 14:16 UTC

   ## **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...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API, Channels presence channels, Channels Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-19 21:15 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2025-09-20 09:57 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-09-21 07:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-03 01:55 UTC

   We are currently investigating this issue.

2. resolved 2025-08-03 05:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-28 13:45 UTC

   We are currently investigating this issue.

2. investigating 2025-07-28 13:46 UTC

   This is only affecting historical usage reports. The real-time stats is functioning as expected.

3. identified 2025-07-28 15:09 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2025-07-29 08:25 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-07-29 13:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard, Channels Stats Integrations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-09 08:10 UTC

   We are currently experiencing an issue affecting our stats collection systems. As a result, Realtime Stats are currently unavailable. Additionally, our Datadog integration is experiencing degraded performance. Our engineering team is actively investigating the root cause and...

2. identified 2025-04-09 14:37 UTC

   The issue affecting Stats Collection and the Datadog integration has been identified and addressed. Systems are now catching up on the backlog, and Realtime Stats and Datadog integration should gradually return to normal. We are continuing to monitor the recovery closely and...

3. monitoring 2025-04-10 07:27 UTC

   Systems are now catching up on the backlog, and Realtime Stats and Datadog integration should gradually return to normal. We are continuing to monitor the recovery closely and will provide another update once the catch-up is fully complete.

4. resolved 2025-04-10 09:59 UTC

   The backlog has fully cleared and Stats Collection and Datadog integration are now operating normally. This incident is now resolved. We apologise for any inconvenience caused and appreciate your patience throughout.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard, Beams dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-13 20:27 UTC

   We are currently investigating an issue where the Pusher dashboard is inaccessible to users attempting to login with username/password. Users logging with SSO are unaffected. Pusher products remain functional without any issues.

2. resolved 2025-01-13 21:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-10 13:09 UTC

   Our engineering team is currently investigating an issue that is causing errors when users attempt to log in to the Pusher portal via Google. All other login methods are functioning as expected.

2. resolved 2024-12-10 14:10 UTC

   Our engineering team has resolved this incident. We apologise for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-01 15:32 UTC

   We are aware of an issue where customers can't downgrade their account plan. Everything else continues to function normally.

2. resolved 2024-11-01 15:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-09-25 05:00 UTC

   From 5:02UTC until 6:23UTC Beams suffered intermittent disruption loading accounts from the pusher dashboard. This was due to internal services not picking up a new ssl certificate that was automatically issued during this time.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-16 14:23 UTC

   We are currently investigating this issue.

2. resolved 2024-09-16 14:37 UTC

   This incident has been resolved. The team saw similarities with a previous incident that affected the US2 cluster and acted swiftly to mitigate and prevent further impact. Overall the impact was very small: a few connections saw small delays receiving messages for a very short...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API, Channels presence channels, Channels Webhooks

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-08 18:00 UTC

   We are investigating what is causing the issue to our US cluster.

2. investigating 2024-09-08 19:31 UTC

   We are escalating the current issue from a partial outage to a major outage. The majority of traffic in the US2 cluster is currently affected. Our team is fully engaged and working to resolve the issue.

3. investigating 2024-09-08 21:19 UTC

   Our team is still investigating the issue within our infrastructure that is preventing us from adding WebSocket capacity to the US2 cluster. This issue is specifically impacting our WebSocket deployments. The majority of clients are currently unable to connect using WebSocket....

4. monitoring 2024-09-08 22:19 UTC

   The team has been able to identify the issue and push a fix. We are seeing a full recovery of the services. We will continue to monitor.

5. monitoring 2024-09-08 22:21 UTC

   A fix has been implemented, and we are monitoring the results. WebSocket connections should now be functional.

6. monitoring 2024-09-08 23:05 UTC

   We are continuing to monitor for any further issues.

7. resolved 2024-09-08 23:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard, Channels Stats Integrations

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-02 11:04 UTC

   Some customers have received incorrect warnings about account usage or observed usage statistics that appear to be incorrect. We are investigating.

2. resolved 2024-09-02 11:57 UTC

   We have resolved the statistics computation issue. Connection counts should be correct again and remain accurate going forward. Daily message volume counters will still show inflated usage until the end of the day; customers that are concerned about potential throttling due to...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-02 11:06 UTC

   We are currently investigating an issue with aggregated statistics being delayed on the Dashboard.

2. identified 2024-08-02 11:58 UTC

   The issue has been identified and mitigated. Missing aggregated statistics are being recovered. No data is missing.

3. monitoring 2024-08-02 12:46 UTC

   Aggregated statistics have been restored. We are monitoring the situation.

4. resolved 2024-08-02 13:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Stats Integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-05 21:01 UTC

   We are investigating why Stats collection has stopped.

2. monitoring 2024-06-05 22:23 UTC

   The problem has been identified and fixed. We are monitoring the results.

3. resolved 2024-06-05 22:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-22 08:16 UTC

   We are currently investigating this issue.

2. identified 2024-05-22 08:27 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-05-22 08:48 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-05-22 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Pusher.js CDN

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-20 08:42 UTC

   Impact: We are currently experiencing degraded performance on our EU clusters. As a result, some users are unable to send messages, and delays may be experienced. Affected Product: Pusher Channels Current Status: Our team is actively investigating the issue and working to...

2. identified 2024-05-20 09:01 UTC

   Issue identified and being fixed.

3. monitoring 2024-05-20 10:07 UTC

   Resolved. Monitoring the system.

4. resolved 2024-05-20 10:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Pusher.js CDN

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-05-18 10:06 UTC

   Impact: We are currently experiencing delays of up to 15 minutes in processing webhooks across our EU, MT1, and US2 clusters. However, we want to assure you that despite these delays, you can still utilize our system and successfully process messages. Affected Product: Pusher...

2. monitoring 2024-05-18 13:02 UTC

   Recovered. Actively monitoring the system.

3. resolved 2024-05-18 13:14 UTC

   The disturbance have been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-04-22 06:00 UTC

   The SSL certificate for our client stats endpoint expired at 00:00 UTC, but the issue was resolved at 8:49 AM UTC. During this period, clients who opted to send client stats using older versions of the JavaScript SDK for web (PusherJS) encountered some errors and were unable to...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-05 11:18 UTC

   Customers are seeing high latency on the US2 cluster (WebSockets). The team is working on it.

2. identified 2024-04-05 12:09 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2024-04-05 13:41 UTC

   We are continuing to work on a fix for this issue.

4. identified 2024-04-05 14:45 UTC

   We are continuing to work on a fix for this issue. Impact is greatly reduced now. Customers are seeing lower latencies.

5. monitoring 2024-04-05 16:59 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2024-04-05 20:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-04 19:13 UTC

   We are currently investigating an issue with high latency in US2 on the Channels WebSocket Client API

2. monitoring 2024-04-04 19:49 UTC

   A fix has been implemented and the latency issues have resolved in US2. We will monitor the systems to ensure the issue does not reoccur.

3. identified 2024-04-04 20:23 UTC

   Issues with US2 have returned. We are seeing issues maintaining connections.

4. identified 2024-04-04 20:52 UTC

   We are continuing to investigate issues with users unable to establish connections from the Websocket Client.

5. monitoring 2024-04-05 01:28 UTC

   A fix for this issue has been deployed and we are monitoring the system.

6. resolved 2024-04-05 10:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-04 09:28 UTC

   We are currently investigating the issue where on the Dashboard when navigating to the Functions feature an error is shown.

2. resolved 2024-04-04 11:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Marketing Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-02 06:12 UTC

   We are currently investigating this issue.

2. resolved 2024-04-02 07:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-03-30 04:15 UTC

   On Saturday March 30th from 04:15 UTC until 11:30 UTC Pusher channels experienced a partial outage and higher than usual latencies on our US2 cluster. The incident was triggered by a single, high volume customer sending requests that was causing an authentication error. These...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-25 01:02 UTC

   We are investigating a delay in Webhooks.

2. resolved 2024-02-25 04:11 UTC

   We have identified the issue and resolved it. Webhooks are behaving as expected again.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-02-24 02:29 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2024-02-24 05:16 UTC

   We have deployed a fix for this issue. The delivery of the delayed webhooks continues.

3. resolved 2024-02-24 13:35 UTC

   All delayed US webhooks completed processing at approximately 730 UTC. This incident is resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-02-23 23:53 UTC

   We are currently investigating this issue.

2. identified 2024-02-24 00:25 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-02-24 00:29 UTC

   A fix has been implemented and we are monitoring the results as the backload is processed off.

4. identified 2024-02-24 01:51 UTC

   We are continuing to see delays in webhooks. We are working on implementing an additional fix.

5. identified 2024-02-24 05:16 UTC

   We have deployed a fix for this issue. The delivery of the delayed webhooks continues.

6. resolved 2024-02-24 13:36 UTC

   All delayed EU webhooks completed processing at approximately 1030 UTC. This incident is resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels WebSocket client API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-22 22:24 UTC

   Pusher US3 cluster is experiencing disruptions for client socket connections. Our team is looking into it.

2. identified 2024-02-22 23:11 UTC

   The team identified the problem. Most connections are stable now but some of them may get reconnected still. The team is working on a permenant solution.

3. monitoring 2024-02-23 00:34 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-02-23 00:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-01-26 15:37 UTC

   Between 15:37 - 16:01 UTC we encountered an issue with our stats pipeline that resulted in missing metrics. Customers may notice data missing for this period in the Pusher Dashboard metrics along with any configured integration dashboards(DataDog and Librato). The issue has been...

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API, Channels Stats Integrations, Channels presence channels, Channels Webhooks

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-12-05 17:34 UTC

   The public EU cluster is currently experiencing an outage which affects customers in this region. For customers in other regions, there is no impact. We are actively working on restoring the public EU cluster.

2. identified 2023-12-05 17:36 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2023-12-05 17:47 UTC

   The public EU cluster has been restored and all services are now back online. We will continue to monitor the cluster health.

4. resolved 2023-12-05 18:11 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API, Channels WebSocket client API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-12-01 20:31 UTC

   We are currently investigating an issue in US2 where some clients may be experiencing latency issues or unable to utilize the Channels WebSocket and REST API.

2. identified 2023-12-01 20:46 UTC

   The team has identified the cause of the latency and are actively working to resolve the high latency issues.

3. monitoring 2023-12-01 20:53 UTC

   The fix has been implemented and latency has improved.

4. resolved 2023-12-01 21:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Dashboard, Channels Pusher.js CDN

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-11-30 10:30 UTC

   Our engineering team has detected an issue that is preventing all data to be published to DataDog. We are currently investigating the root cause

2. resolved 2023-11-30 11:17 UTC

   This incident is being resolved

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels REST API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-29 15:17 UTC

   We are currently investigating this issue.

2. identified 2023-11-29 15:48 UTC

   Our engineering team is working on rolling out an improvement to resolve the high latency on the US2 cluster.

3. resolved 2023-11-29 16:09 UTC

   Our engineering team has confirmed this issue has been mitigated. We apologise for any inconvenience this may have caused you.

Excerpts are shortened. Read the full incident on Pusher's status page.

Affected: Channels Webhooks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2023-11-22 13:08 UTC

   Our engineering team is actively investigating an issue that is impacting the delivery of a specific set of webhooks. This is only affecting our EU cluster

2. resolved 2023-11-22 14:27 UTC

   Our engineering team has rolled out a fix and has confirmed webhooks delivery is fully operational on the affected EU cluster.

Excerpts are shortened. Read the full incident on Pusher's status page.