CheckUpstream does not yet run an independent probe against Pusher, so no availability figure is published for it — only Pusher's own disclosure record below. 4 incidents were recorded in the past 12 months; the most recent resolved 148 days ago after 1 hour. Status signals are polled from Pusher's official Atlassian Statuspage status page, alongside independent probes and community reports.
We run no independent probe against Pusher yet, so we publish no availability figure for it. What follows is Pusher's own disclosure record, which is a different thing.
Vendor disclosed: 2 incidents · 364 of 365 days with none posted · 27m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Pusher
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.989%
1y
99.995%
Downtime like this can be refundable
If you're a paying Pusher customer, outages in these windows may count against Pusher's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A Pusher outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is Pusher currently down?
Pusher is currently Operational. CheckUpstream tracks Pusher in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Pusher's last resolved incident started 148 days ago and lasted 1h 13m (degraded performance).
›What's Pusher's 30-day uptime?
We don't publish one. CheckUpstream runs no independent probe against Pusher yet, and the only other figure available would be derived from Pusher's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
›How do I monitor Pusher in production?
Sign up to CheckUpstream and add Pusher to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track Pusher?
We poll Pusher's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.