Pusher status history
Current state: operational — “All Systems Operational” per https://status.pusher.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Pusher incidents last?
From 19 incidents with a vendor-posted start and resolve time. Longest on record: Higher latency on our AP1 cluster for some customers — 34.6 h (2025-09-19 21:15 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (19)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-23 01:27 UTC | Elevated Errors on us2 | resolved | none | 3 h 44 min |
| 2026-08-22 03:17 UTC | Elevated errors on us2 cluster | resolved | none | 1 h 30 min |
| 2026-04-06 01:52 UTC | Intermittent API errors in US2 cluster | resolved | minor | 1 h 03 min |
| 2026-03-31 12:33 UTC | Cluster SA1: Delayed Channels webhook delivery on SA1 cluster | resolved | minor | 11 min |
| 2026-02-15 20:33 UTC | Increased error rate on the US2 cluster | resolved | none | 1 h 40 min |
| 2026-01-29 10:38 UTC | Errors increase for API in cluster us3 | resolved | none | 20 min |
| 2026-01-26 22:29 UTC | Increased error rate on the US2 cluster impacting presence events | resolved | none | 14 min |
| 2026-01-22 16:38 UTC | Incorrect subscription changes affecting some accounts | resolved | none | 19 h 20 min |
| 2026-01-16 08:48 UTC | Intermittent errors with message delivery on cluster us2 | resolved | minor | 3 h 52 min |
| 2026-01-16 01:07 UTC | Intermittent errors with message delivery | resolved | minor | 30 min |
| 2025-10-27 11:50 UTC | AP1 cluster - Socket connection failures | resolved | minor | 1 h 44 min |
| 2025-10-21 15:06 UTC | Elevated API Errors in AP4 Cluster | postmortem | major | 2 h 36 min |
| 2025-10-20 18:36 UTC | US3 cluster - major outage | postmortem | major | 2 h 05 min |
| 2025-10-20 17:26 UTC | MT1 cluster - increased latency | resolved | major | 13 h 48 min |
| 2025-10-20 17:21 UTC | Pusher Beams degradation | resolved | minor | 13 h 51 min |
| 2025-10-20 08:19 UTC | Beams - webhook delivery issues | resolved | none | 1 h 58 min |
| 2025-10-20 08:10 UTC | MT1 cluster - increased latency and webhook delivery failures | resolved | minor | 4 h 46 min |
| 2025-10-19 00:44 UTC | Increased latency - US2 cluster | postmortem | minor | 7 h 32 min |
| 2025-09-19 21:15 UTC | Higher latency on our AP1 cluster for some customers | resolved | minor | 34 h 39 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Pusher with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"pusher"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}