Minor impactResolvedCommunication

Pusher incident: Intermittent API errors in US2 cluster

Pusher reported this minor-impact incident on its official status page on Apr 6, 2026, 01:52 UTC. It was resolved after 1h 4m.

Right now Pusher is operational. Live Pusher status →

🔔 Get alerted when Pusher has issuesFree · email alerts · no credit card
Apr 6, 2026, 01:52 UTC
started
Apr 6, 2026, 02:55 UTC
resolved
1h 4m
duration
Minor
impact

Affected components

  • Channels WebSocket client API

Timeline

updates from Pusher's status page ↗
  1. resolvedApr 6, 2026, 02:55 UTC

    This incident has been resolved.

  2. monitoringApr 6, 2026, 02:32 UTC

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

  3. identifiedApr 6, 2026, 02:01 UTC

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

  4. investigatingApr 6, 2026, 01:52 UTC

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

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Pusher's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Pusher have incidents?

Pusher reported 0 incidents in the last 90 days. See Pusher's uptime and incident history

← Previous: Cluster SA1: Delayed Channels webhook delivery on SA1 cluster (Mar 31, 2026)
Pusher incident on Apr 6, 2026: Intermittent API errors in US2 cluster · APIStatus.watch