Pusher Outage History

Pusher is up right now

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

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

Source: https://status.pusher.com

Critical September 8, 2024

We are experiencing a major outage in our US2 cluster

Detected by Pingoru
Sep 08, 2024, 06:00 PM UTC
Resolved
Sep 08, 2024, 11:06 PM UTC
Duration
5h 5m
Affected: Channels REST APIChannels WebSocket client APIChannels presence channelsChannels Webhooks
Timeline · 7 updates
  1. investigating Sep 08, 2024, 06:00 PM UTC

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

  2. investigating Sep 08, 2024, 07:31 PM 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 Sep 08, 2024, 09:19 PM 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. However fallback mechanisms (SockJS, HTTP streaming, and HTTP polling) are available for connection if they are not disabled in your configuration.

  4. monitoring Sep 08, 2024, 10:19 PM 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 Sep 08, 2024, 10:21 PM UTC

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

  6. monitoring Sep 08, 2024, 11:05 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Sep 08, 2024, 11:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 2, 2024

Inaccurate Account Usage Warnings Reported

Detected by Pingoru
Sep 02, 2024, 11:04 AM UTC
Resolved
Sep 02, 2024, 11:57 AM UTC
Duration
53m
Affected: Channels DashboardChannels Stats Integrations
Timeline · 2 updates
  1. investigating Sep 02, 2024, 11:04 AM UTC

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

  2. resolved Sep 02, 2024, 11:57 AM 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 breaching daily limits can reach out to customer support to ensure access remains uninterrupted.

Read the full incident report →

Notice August 2, 2024

Statistics Aggregation delayed

Detected by Pingoru
Aug 02, 2024, 11:06 AM UTC
Resolved
Aug 02, 2024, 01:01 PM UTC
Duration
1h 55m
Affected: Channels Dashboard
Timeline · 4 updates
  1. investigating Aug 02, 2024, 11:06 AM UTC

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

  2. identified Aug 02, 2024, 11:58 AM UTC

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

  3. monitoring Aug 02, 2024, 12:46 PM UTC

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

  4. resolved Aug 02, 2024, 01:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 5, 2024

Stats collection experiencing an interruption

Detected by Pingoru
Jun 05, 2024, 09:01 PM UTC
Resolved
Jun 05, 2024, 10:39 PM UTC
Duration
1h 38m
Affected: Channels Stats Integrations
Timeline · 3 updates
  1. investigating Jun 05, 2024, 09:01 PM UTC

    We are investigating why Stats collection has stopped.

  2. monitoring Jun 05, 2024, 10:23 PM UTC

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

  3. resolved Jun 05, 2024, 10:39 PM UTC

    This incident has been resolved.

Read the full incident report →