Skip to main content
Pusher

We are experiencing a major outage in our US2 cluster

Major outage Lasted 5h 6m · started · Pusher's page

Level
confirmed
Worst impact
Major outage
Components
Channels REST API, Channels WebSocket client API, Channels presence channels, Channels Webhooks
Regions
us

What to do

  • Check whether you use Pusher Channels REST API, Channels WebSocket client API, Channels presence channels, Channels Webhooks in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 5h 6m it lasted.

    Anything that failed between 2024-09-08 18:00 UTC and 2024-09-08 23:06 UTC may need a replay.
  • Subscribe to Pusher's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=pusher works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Pusher 7

  1. investigating

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

    provider

  2. investigating

    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.

    provider

  3. investigating

    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.

    provider

  4. monitoring

    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.

    provider

  5. monitoring

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

    provider

  6. monitoring

    We are continuing to monitor for any further issues.

    provider

  7. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-ffcd7b96f6

Is Pusher still down?

No, this incident was resolved 2024-09-08 23:06 UTC. For Pusher's live state, see https://down.guide/pusher.

How long did it last?

5h 6m, from 2024-09-08 18:00 UTC to 2024-09-08 23:06 UTC, by the times Pusher posted.

What was affected?

Pusher named Channels REST API, Channels WebSocket client API, Channels presence channels, Channels Webhooks in us.

What caused it?

Pusher hasn't published a root cause. If it does, it shows here.

Where does this come from?

Pusher's official status page, https://status.pusher.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.