Vendor Status Watch

← all vendors

Pusher status history

Current state: operational — “All Systems Operational” per https://status.pusher.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
2incidents, last 90 days
19incidents on record
Incidents per week, last 12 weeks:

How long do Pusher incidents last?

2.1 hmedian incident duration19 measured
13.8 h90th percentile1 in 10 ran longer
2.6 hmedian, major/critical only3 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-23 01:27 UTCElevated Errors on us2resolvednone3 h 44 min
2026-08-22 03:17 UTCElevated errors on us2 clusterresolvednone1 h 30 min
2026-04-06 01:52 UTCIntermittent API errors in US2 clusterresolvedminor1 h 03 min
2026-03-31 12:33 UTCCluster SA1: Delayed Channels webhook delivery on SA1 clusterresolvedminor11 min
2026-02-15 20:33 UTCIncreased error rate on the US2 clusterresolvednone1 h 40 min
2026-01-29 10:38 UTCErrors increase for API in cluster us3resolvednone20 min
2026-01-26 22:29 UTCIncreased error rate on the US2 cluster impacting presence eventsresolvednone14 min
2026-01-22 16:38 UTCIncorrect subscription changes affecting some accountsresolvednone19 h 20 min
2026-01-16 08:48 UTCIntermittent errors with message delivery on cluster us2resolvedminor3 h 52 min
2026-01-16 01:07 UTCIntermittent errors with message deliveryresolvedminor30 min
2025-10-27 11:50 UTCAP1 cluster - Socket connection failuresresolvedminor1 h 44 min
2025-10-21 15:06 UTCElevated API Errors in AP4 Clusterpostmortemmajor2 h 36 min
2025-10-20 18:36 UTCUS3 cluster - major outagepostmortemmajor2 h 05 min
2025-10-20 17:26 UTCMT1 cluster - increased latencyresolvedmajor13 h 48 min
2025-10-20 17:21 UTCPusher Beams degradationresolvedminor13 h 51 min
2025-10-20 08:19 UTCBeams - webhook delivery issuesresolvednone1 h 58 min
2025-10-20 08:10 UTCMT1 cluster - increased latency and webhook delivery failuresresolvedminor4 h 46 min
2025-10-19 00:44 UTCIncreased latency - US2 clusterpostmortemminor7 h 32 min
2025-09-19 21:15 UTCHigher latency on our AP1 cluster for some customersresolvedminor34 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
}