Pusher System Status

All Systems Operational

About This Site

Pusher monitors all of its critical services both internally and through 3rd party services. If there is a disruption in service, incident notes will be updated here.

Below, you’ll find the current status of the Pusher infrastructure, as well as any recent issues or incidents we may have had.

If you think that something is not working with the service, please get in touch with us by submitting a ticket through our support portal: https://support.pusher.com

Channels REST API ? Operational
Channels WebSocket client API ? Operational
Channels Dashboard ? Operational
Channels Stats Integrations ? Operational
Channels presence channels Operational
Channels Webhooks Operational
Channels Pusher.js CDN ? Operational
Beams Operational
Beams dashboard Operational
Marketing Website ? Operational
Payment API ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Nov 3, 2025

No incidents reported today.

Nov 2, 2025

No incidents reported.

Nov 1, 2025

No incidents reported.

Oct 31, 2025

No incidents reported.

Oct 30, 2025

No incidents reported.

Oct 29, 2025

No incidents reported.

Oct 28, 2025

No incidents reported.

Oct 27, 2025
Resolved - This incident has been resolved.
Oct 27, 13:34 UTC
Update - All services are now fully operational. We continue to monitor the cluster.
Oct 27, 12:53 UTC
Monitoring - 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.
Oct 27, 12:41 UTC
Identified - 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.
Oct 27, 12:22 UTC
Investigating - 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.
Oct 27, 11:50 UTC
Oct 26, 2025

No incidents reported.

Oct 25, 2025

No incidents reported.

Oct 24, 2025

No incidents reported.

Oct 23, 2025

No incidents reported.

Oct 22, 2025

No incidents reported.

Oct 21, 2025
Postmortem - Read details
Oct 23, 14:14 UTC
Resolved - This incident has been resolved.
Oct 21, 17:43 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 21, 17:39 UTC
Identified - 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.
Oct 21, 17:32 UTC
Monitoring - A fix has been implemented and we are monitoring. The cluster will take a few more minutes to fully stabilize across all nodes.
Oct 21, 15:29 UTC
Update - The team continues to make progress restoring the cache services. We anticipate full resolution in the next 10-15 minutes.
Oct 21, 15:27 UTC
Identified - The team has identified the issue with one of our backend caching servers. The team is working to restore the connections to the server.
Oct 21, 15:09 UTC
Investigating - We're experiencing an elevated level of API errors and latency in AP4 and are currently looking into the issue.
Oct 21, 15:06 UTC
Resolved - This incident has been resolved.
Oct 21, 07:14 UTC
Investigating - 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.
Oct 20, 17:26 UTC
Resolved - This incident has been resolved.
Oct 21, 07:13 UTC
Investigating - 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 minimize downstream effects while our provider implements a fix.
Oct 20, 17:21 UTC
Oct 20, 2025
Resolved - This incident has been resolved.
Oct 20, 20:41 UTC
Monitoring - All services are now fully operational. Our team continues to monitor the system closely to ensure ongoing stability and performance.
Oct 20, 20:20 UTC
Update - 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.
Oct 20, 19:59 UTC
Update - 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.
Oct 20, 19:04 UTC
Identified - We are continuing to investigate this issue.
Oct 20, 19:01 UTC
Update - We are continuing to investigate this issue.
Oct 20, 19:01 UTC
Investigating - We're seeing an increased latency and a number of 503 errors on us3 cluster. The team is investigating.
Oct 20, 18:36 UTC
Resolved - This incident has been resolved.
Oct 20, 12:57 UTC
Update - 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.
Oct 20, 10:17 UTC
Monitoring - 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.
Oct 20, 09:33 UTC
Investigating - 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 impacts and working to minimize downstream effects while our provider implements a fix.
Oct 20, 08:10 UTC
Resolved - 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.
Oct 20, 10:18 UTC
Monitoring - 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.
Oct 20, 09:34 UTC
Investigating - 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 impacts while monitoring the provider's resolution progress.
Oct 20, 08:19 UTC