Pusher Outage History

Pusher is up right now

Pusher had 29 outages in the last 2 years totaling 165h 28m of downtime — averaging 1.2 incidents per month.

There were 29 Pusher outages since June 5, 2024 totaling 165h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pusher.com

Minor April 6, 2026

Intermittent API errors in US2 cluster

Detected by Pingoru
Apr 06, 2026, 01:52 AM UTC
Resolved
Apr 06, 2026, 02:55 AM UTC
Duration
1h 3m
Affected: Channels WebSocket client API
Timeline · 4 updates
  1. investigating Apr 06, 2026, 01:52 AM UTC

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

  2. identified Apr 06, 2026, 02:01 AM UTC

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

  3. monitoring Apr 06, 2026, 02:32 AM UTC

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

  4. resolved Apr 06, 2026, 02:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2026

Cluster SA1: Delayed Channels webhook delivery on SA1 cluster

Detected by Pingoru
Mar 31, 2026, 12:33 PM UTC
Resolved
Mar 31, 2026, 12:44 PM UTC
Duration
11m
Affected: Channels Webhooks
Timeline · 3 updates
  1. identified Mar 31, 2026, 12:33 PM UTC

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

  2. monitoring Mar 31, 2026, 12:42 PM UTC

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

  3. resolved Mar 31, 2026, 12:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 15, 2026

Increased error rate on the US2 cluster

Detected by Pingoru
Feb 15, 2026, 08:33 PM UTC
Resolved
Feb 15, 2026, 10:14 PM UTC
Duration
1h 40m
Timeline · 3 updates
  1. investigating Feb 15, 2026, 08:33 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 15, 2026, 09:38 PM 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 Feb 15, 2026, 10:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 29, 2026

Errors increase for API in cluster us3

Detected by Pingoru
Jan 29, 2026, 10:38 AM UTC
Resolved
Jan 29, 2026, 10:58 AM UTC
Duration
20m
Affected: Channels REST API
Timeline · 3 updates
  1. investigating Jan 29, 2026, 10:38 AM UTC

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

  2. monitoring Jan 29, 2026, 10:55 AM UTC

    A fix has been implemented and we are monitoring the situation

  3. resolved Jan 29, 2026, 10:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 22, 2026

Incorrect subscription changes affecting some accounts

Detected by Pingoru
Jan 22, 2026, 04:38 PM UTC
Resolved
Jan 23, 2026, 11:58 AM UTC
Duration
19h 20m
Affected: Channels REST APIChannels Webhooks
Timeline · 2 updates
  1. identified Jan 22, 2026, 04:38 PM 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 subscription levels.

  2. resolved Jan 23, 2026, 11:58 AM 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.

Read the full incident report →

Minor January 16, 2026

Intermittent errors with message delivery on cluster us2

Detected by Pingoru
Jan 16, 2026, 08:48 AM UTC
Resolved
Jan 16, 2026, 12:41 PM UTC
Duration
3h 52m
Affected: Channels presence channels
Timeline · 4 updates
  1. investigating Jan 16, 2026, 08:48 AM UTC

    We are currently investigating this issue.

  2. identified Jan 16, 2026, 10:56 AM UTC

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

  3. monitoring Jan 16, 2026, 11:10 AM UTC

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

  4. resolved Jan 16, 2026, 12:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 16, 2026

Intermittent errors with message delivery

Detected by Pingoru
Jan 16, 2026, 01:07 AM UTC
Resolved
Jan 16, 2026, 01:37 AM UTC
Duration
30m
Affected: Channels WebSocket client APIChannels presence channels
Timeline · 3 updates
  1. investigating Jan 16, 2026, 01:07 AM UTC

    We are currently investigating this issue.

  2. monitoring Jan 16, 2026, 01:16 AM UTC

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

  3. resolved Jan 16, 2026, 01:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 27, 2025

AP1 cluster - Socket connection failures

Detected by Pingoru
Oct 27, 2025, 11:50 AM UTC
Resolved
Oct 27, 2025, 01:34 PM UTC
Duration
1h 44m
Affected: Channels WebSocket client APIChannels presence channels
Timeline · 5 updates
  1. investigating Oct 27, 2025, 11:50 AM 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 Oct 27, 2025, 12:22 PM 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 Oct 27, 2025, 12:41 PM 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. monitoring Oct 27, 2025, 12:53 PM UTC

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

  5. resolved Oct 27, 2025, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

MT1 cluster - increased latency

Detected by Pingoru
Oct 20, 2025, 05:26 PM UTC
Resolved
Oct 21, 2025, 07:14 AM UTC
Duration
13h 48m
Affected: Channels REST APIChannels WebSocket client APIChannels DashboardChannels presence channels
Timeline · 2 updates
  1. investigating Oct 20, 2025, 05:26 PM 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 additional impacts and working to minimize downstream effects while our provider implements a fix.

  2. resolved Oct 21, 2025, 07:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Pusher Beams degradation

Detected by Pingoru
Oct 20, 2025, 05:21 PM UTC
Resolved
Oct 21, 2025, 07:13 AM UTC
Duration
13h 51m
Affected: Beams
Timeline · 2 updates
  1. investigating Oct 20, 2025, 05:21 PM 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 minimize downstream effects while our provider implements a fix.

  2. resolved Oct 21, 2025, 07:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Beams - webhook delivery issues

Detected by Pingoru
Oct 20, 2025, 08:19 AM UTC
Resolved
Oct 20, 2025, 10:18 AM UTC
Duration
1h 58m
Affected: Beams
Timeline · 3 updates
  1. investigating Oct 20, 2025, 08:19 AM 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 impacts while monitoring the provider's resolution progress.

  2. monitoring Oct 20, 2025, 09:34 AM 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 Oct 20, 2025, 10:18 AM 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.

Read the full incident report →

Minor October 20, 2025

MT1 cluster - increased latency and webhook delivery failures

Detected by Pingoru
Oct 20, 2025, 08:10 AM UTC
Resolved
Oct 20, 2025, 12:57 PM UTC
Duration
4h 46m
Affected: Channels Webhooks
Timeline · 4 updates
  1. investigating Oct 20, 2025, 08:10 AM 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 impacts and working to minimize downstream effects while our provider implements a fix.

  2. monitoring Oct 20, 2025, 09:33 AM 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 Oct 20, 2025, 10:17 AM 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 Oct 20, 2025, 12:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 19, 2025

Higher latency on our AP1 cluster for some customers

Detected by Pingoru
Sep 19, 2025, 09:15 PM UTC
Resolved
Sep 21, 2025, 07:54 AM UTC
Duration
1d 10h
Affected: Channels WebSocket client APIChannels presence channelsChannels Webhooks
Timeline · 3 updates
  1. identified Sep 19, 2025, 09:15 PM UTC

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

  2. monitoring Sep 20, 2025, 09:57 AM UTC

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

  3. resolved Sep 21, 2025, 07:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 28, 2025

Pusher Channel Historical Usage reports are not working since 27 July 4 PM UTC+1

Detected by Pingoru
Jul 28, 2025, 01:45 PM UTC
Resolved
Jul 29, 2025, 01:18 PM UTC
Duration
23h 33m
Affected: Channels Dashboard
Timeline · 5 updates
  1. investigating Jul 28, 2025, 01:45 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 28, 2025, 01:46 PM UTC

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

  3. identified Jul 28, 2025, 03:09 PM UTC

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

  4. monitoring Jul 29, 2025, 08:25 AM UTC

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

  5. resolved Jul 29, 2025, 01:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 9, 2025

Interruption in Stats Collection and Degraded Datadog Integration

Detected by Pingoru
Apr 09, 2025, 08:10 AM UTC
Resolved
Apr 10, 2025, 09:59 AM UTC
Duration
1d 1h
Affected: Channels DashboardChannels Stats Integrations
Timeline · 4 updates
  1. investigating Apr 09, 2025, 08:10 AM 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 working to restore normal service as quickly as possible. We will provide updates as we learn more. Thank you for your patience and understanding.

  2. identified Apr 09, 2025, 02:37 PM 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 will provide another update once the catch-up is fully complete. Thank you for your continued patience.

  3. monitoring Apr 10, 2025, 07:27 AM 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 Apr 10, 2025, 09:59 AM 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.

Read the full incident report →

Minor January 13, 2025

Pusher dashboard inaccessible for logins with username/password

Detected by Pingoru
Jan 13, 2025, 08:27 PM UTC
Resolved
Jan 13, 2025, 09:16 PM UTC
Duration
49m
Affected: Channels DashboardBeams dashboard
Timeline · 2 updates
  1. investigating Jan 13, 2025, 08:27 PM 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 Jan 13, 2025, 09:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2024

Users unable to Log In using Google Login

Detected by Pingoru
Dec 10, 2024, 01:09 PM UTC
Resolved
Dec 10, 2024, 02:10 PM UTC
Duration
1h 1m
Affected: Channels Dashboard
Timeline · 2 updates
  1. investigating Dec 10, 2024, 01:09 PM 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 Dec 10, 2024, 02:10 PM UTC

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

Read the full incident report →

Minor November 1, 2024

Some customers are unable to downgrade their account

Detected by Pingoru
Nov 01, 2024, 03:32 PM UTC
Resolved
Nov 01, 2024, 03:58 PM UTC
Duration
25m
Affected: Channels Dashboard
Timeline · 2 updates
  1. investigating Nov 01, 2024, 03:32 PM UTC

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

  2. resolved Nov 01, 2024, 03:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 26, 2024

Beams: intermittent disruption loading accounts from the pusher dashboard

Detected by Pingoru
Sep 26, 2024, 12:18 PM UTC
Resolved
Sep 25, 2024, 05:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 26, 2024, 12:18 PM 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.

Read the full incident report →

Minor September 16, 2024

Increased latency on MT1

Detected by Pingoru
Sep 16, 2024, 02:23 PM UTC
Resolved
Sep 16, 2024, 02:37 PM UTC
Duration
13m
Affected: Channels REST APIChannels WebSocket client API
Timeline · 2 updates
  1. investigating Sep 16, 2024, 02:23 PM UTC

    We are currently investigating this issue.

  2. resolved Sep 16, 2024, 02:37 PM 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 time.

Read the full incident report →