Minor impactResolvedCommunication

Pusher incident: Higher latency on our AP1 cluster for some customers

Pusher reported this minor-impact incident on its official status page on Sep 19, 2025, 21:15 UTC. It was resolved after 1d 10h.

Right now Pusher is operational. Live Pusher status →

🔔 Get alerted when Pusher has issuesFree · email alerts · no credit card
Sep 19, 2025, 21:15 UTC
started
Sep 21, 2025, 07:54 UTC
resolved
1d 10h
duration
Minor
impact

Affected components

  • Channels WebSocket client API
  • Channels Webhooks
  • Channels presence channels

Timeline

updates from Pusher's status page ↗
  1. resolvedSep 21, 2025, 07:54 UTC

    This incident has been resolved.

  2. monitoringSep 20, 2025, 09:57 UTC

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

  3. identifiedSep 19, 2025, 21:15 UTC

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

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: Pusher Channel Historical Usage reports are not working since 27 July 4 PM UTC+1 (Jul 28, 2025)Next: Increased latency - US2 cluster (Oct 19, 2025) →
Pusher incident on Sep 19, 2025: Higher latency on our AP1 cluster for some customers · APIStatus.watch