Minor impactResolvedCommunication

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

Pusher reported this minor-impact incident on its official status page on Jul 28, 2025, 13:45 UTC. It was resolved after 23h 33m.

Right now Pusher is operational. Live Pusher status →

🔔 Get alerted when Pusher has issuesFree · email alerts · no credit card
Jul 28, 2025, 13:45 UTC
started
Jul 29, 2025, 13:18 UTC
resolved
23h 33m
duration
Minor
impact

Affected components

  • Channels Dashboard

Timeline

updates from Pusher's status page ↗
  1. resolvedJul 29, 2025, 13:18 UTC

    This incident has been resolved.

  2. monitoringJul 29, 2025, 08:25 UTC

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

  3. identifiedJul 28, 2025, 15:09 UTC

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

  4. investigatingJul 28, 2025, 13:46 UTC

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

  5. investigatingJul 28, 2025, 13:45 UTC

    We are currently investigating this issue.

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: Interruption in Stats Collection and Degraded Datadog Integration (Apr 9, 2025)Next: Higher latency on our AP1 cluster for some customers (Sep 19, 2025) →
Pusher incident on Jul 28, 2025: Pusher Channel Historical Usage reports are not working since 27 July 4 PM UTC+1 · APIStatus.watch