Skip to content

Outage tracker

Pusher: incident history

The last 24 hours in detail, Pusher's declared incident record, and our regional check results beside it.

← Back to Pusher's check readings

We started checking Pusher on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when Pusher reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Pusher's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Pusher's own status page declared. Below it, any public chatter we saw about Pusher and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Pusher's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Pusher in the last 24 hours, which is not evidence that nothing is wrong.
Pusher's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Pusher's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Pusher next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East100.00%730
US-West100.00%576
Europe100.00%527
Asia-Pacific100.00%319

Their declared record

Pusher's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Elevated Errors on us2All systems operational
Aug 23, 2026, 1:27 AM UTC to Aug 23, 2026, 5:12 AM UTC (3h 45m)resolved
their latest update (Aug 23, 2026, 5:12 AM UTC): This incident has been resolved.
Elevated errors on us2 clusterAll systems operational
Aug 22, 2026, 3:17 AM UTC to Aug 22, 2026, 4:47 AM UTC (1h 31m)resolved
their latest update (Aug 22, 2026, 4:47 AM UTC): This incident has been resolved.
Intermittent API errors in US2 clusterMinor incident
Apr 6, 2026, 1:52 AM UTC to Apr 6, 2026, 2:55 AM UTC (1h 4m)resolved
their latest update (Apr 6, 2026, 2:55 AM UTC): This incident has been resolved.
Cluster SA1: Delayed Channels webhook delivery on SA1 clusterMinor incident
Mar 31, 2026, 12:33 PM UTC to Mar 31, 2026, 12:44 PM UTC (11 min)resolved
their latest update (Mar 31, 2026, 12:44 PM UTC): This incident has been resolved.
Increased error rate on the US2 clusterAll systems operational
Feb 15, 2026, 8:33 PM UTC to Feb 15, 2026, 10:14 PM UTC (1h 41m)resolved
their latest update (Feb 15, 2026, 10:14 PM UTC): This incident has been resolved.
Errors increase for API in cluster us3All systems operational
Jan 29, 2026, 10:38 AM UTC to Jan 29, 2026, 10:58 AM UTC (21 min)resolved
their latest update (Jan 29, 2026, 10:58 AM UTC): This incident has been resolved.
Increased error rate on the US2 cluster impacting presence eventsAll systems operational
Jan 26, 2026, 10:29 PM UTC to Jan 26, 2026, 10:43 PM UTC (14 min)resolved
their latest update (Jan 26, 2026, 10:43 PM UTC): This incident has been resolved.
Incorrect subscription changes affecting some accountsAll systems operational
Jan 22, 2026, 4:38 PM UTC to Jan 23, 2026, 11:58 AM UTC (19h 20m)resolved
their latest update (Jan 23, 2026, 11:58 AM UTC): All affected accounts have been restored to their correct subscription levels. We sent an email yesterday to all impacted customers. If you notice any issues with your subscription, please contact us.
Intermittent errors with message delivery on cluster us2Minor incident
Jan 16, 2026, 8:48 AM UTC to Jan 16, 2026, 12:41 PM UTC (3h 52m)resolved
their latest update (Jan 16, 2026, 12:41 PM UTC): This incident has been resolved.
Intermittent errors with message deliveryMinor incident
Jan 16, 2026, 1:07 AM UTC to Jan 16, 2026, 1:37 AM UTC (31 min)resolved
their latest update (Jan 16, 2026, 1:37 AM UTC): This incident has been resolved.

Showing the 10 most recent of 50 incidents Pusher has declared in the history we hold.

These entries are Pusher's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Pusher's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.