CheckUpstream has measured PubNub at 100.000% uptime over the last 90 days and 100.000% over the last 12 months. 2 incidents were recorded in the past 12 months; the most recent resolved 46 days ago after 38 minutes. Status signals are polled from PubNub's official Atlassian Statuspage status page, alongside independent probes and community reports.
90 days uptime
100.000%
90 of 90 days clean · 0m total downtime
Live status pill for PubNub. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=pubnub"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/pubnub" style="border:0;width:260px;height:44px" loading="lazy" title="PubNub status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/pubnub)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/pubnub/badge.svgPubNub is currently Operational. CheckUpstream tracks PubNub in real-time across the official status page, RSS / Atom feeds, and community telemetry — refresh this page for the latest reading.
PubNub's last resolved incident started 46 days ago and lasted 37 minutes (degraded performance).
Looking for the live "is PubNub down" view? See the PubNub Status page.
PubNub's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
Sign up to CheckUpstream and add PubNub 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).
We poll PubNub'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.