We started checking PubNub on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what PubNub's own status page declared. Below it, any public chatter we saw about PubNub 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 PubNub'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 PubNub in the last 24 hours, which is not evidence that nothing is wrong.
PubNub's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
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 PubNub's own declaration, shown as they made it.
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.
PubNub's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Errors with history readers in FRAMinor incident
Oct 26, 2026, 9:14 PM UTC to Oct 26, 2026, 9:46 PM UTC (32 min)postmortem published
their latest update (Oct 30, 2026, 5:23 PM UTC): ### Problem Description, Impact, and Resolution
On October 26, 2026, from approximately 20:56 to 21:12 UTC, users accessing History APIs in Frankfurt may have experienced elevated error rates and latency. A sudden surge in history read requests exceeded the available capacity o…
Errors and Latency for PresenceMinor incident
Oct 26, 2026, 9:07 PM UTC to Oct 26, 2026, 9:55 PM UTC (48 min)postmortem published
their latest update (Oct 29, 2026, 9:39 PM UTC): ### Problem Description, Impact, and Resolution
At approximately 20:40 UTC on October 26, 2026, we observed elevated error rates and latency with the Presence API across multiple regions globally. A software update to the Presence service triggered resource issues that reduced …
Errors and Latency for Presence in FRA and BOMMinor incident
Oct 22, 2026, 4:02 PM UTC to Oct 22, 2026, 4:35 PM UTC (34 min)postmortem published
their latest update (Oct 26, 2026, 9:36 PM UTC): ### **Problem Description, Impact, and Resolution**
On October 22, from approximately 14:45 to 16:13 UTC, users of our Frankfurt \(FRA\) and Mumbai \(BOM\) points of presence may have seen elevated error rates and latency on Presence API calls. Other PubNub services were not aff…
Certificate Issue Causing Potential Connection IssuesPartial outage
Oct 22, 2026, 1:11 AM UTC to Oct 22, 2026, 2:47 AM UTC (1h 36m)postmortem published
their latest update (Oct 26, 2026, 9:30 PM UTC): ### **Problem Description, Impact, and Resolution**
From 19:26 UTC on October 21 until approximately 02:04 UTC on October 22, some PubNub endpoints served TLS certificates that our certificate authority had revoked. Clients that check certificate revocation could have failed to …
Increased Subscribe error rate and latency observed globallyAll systems operational
Oct 9, 2026, 5:30 PM UTC to Oct 9, 2026, 5:30 PM UTC (0 min)postmortem published
their latest update (Oct 14, 2026, 5:19 PM UTC): ### **Problem Description, Impact, and Resolution**
On October 9, 2026, between 17:30 and 18:20 UTC, we observed elevated HTTP 5xx errors affecting the Subscribe endpoint for a subset of customers. Some subscribe requests may have failed, and a subset of messages may have been …
Potential for some missed messages for subscribers in US East PoPMinor incident
Aug 25, 2026, 1:22 PM UTC to Aug 25, 2026, 2:51 PM UTC (1h 29m)postmortem published
their latest update (Aug 28, 2026, 5:46 PM UTC): ### **Problem Description, Impact, and Resolution**
On Tuesday, August 25th, 2026, at 12:10 UTC, our internal monitoring alerted us to an issue where a very small subset of messages within one availability zone of one region \(our US East point of presence\) may not have been i…
Global Errors and Failures with Publish and Functions, Delays with Events & ActionsAll systems operational
Aug 14, 2026, 2:29 PM UTC to Aug 14, 2026, 2:29 PM UTC (0 min)postmortem published
their latest update (Aug 20, 2026, 4:57 PM UTC): ### **Problem Description, Impact, and Resolution**
At approximately **13:55 UTC on Aug 14, 2026**, we observed elevated publish errors and message replication failures in our publish/subscribe service, which also caused latency in other PubNub services globally. Customers may …
Replication failuresAll systems operational
Jun 10, 2026, 8:14 PM UTC to Jun 10, 2026, 8:45 PM UTC (31 min)postmortem published
their latest update (Jun 15, 2026, 11:58 PM UTC): ## Problem Description, Impact, and Resolution
At 19:50 UTC on June 10, 2026, we observed a small fraction of publishes originating from US-EAST-1 failing to replicate to subscribers globally. We removed the degraded publisher pod from service and the issue was resolved at 21:2…
Global Errors and Failures with Publish and Functions, Delays with Events & ActionsAll systems operational
Jun 9, 2026, 2:00 PM UTC to Jun 9, 2026, 2:00 PM UTC (0 min)postmortem published
their latest update (Jun 12, 2026, 6:31 PM UTC): ### **Problem Description, Impact, and Resolution**
At approximately **13:20 UTC on June 9, 2026**, we observed elevated publish errors and message replication failures in our publish/subscribe service, which also caused latency in other PubNub services globally. Customers may …
Connectivity Issues Affecting a Subset of SubscriptionsAll systems operational
Mar 24, 2026, 8:21 PM UTC to Mar 24, 2026, 9:12 PM UTC (52 min)postmortem published
their latest update (Mar 25, 2026, 10:35 PM UTC): ### **Problem Description, Impact, and Resolution**
On March 24, 2026, at 19:27 UTC, one network shard experienced intermittent connectivity affecting a subset of customers. The affected users may have experienced elevated latency and temporary error responses related to their …
Showing the 10 most recent of 50 incidents PubNub has declared in the history we hold.
These entries are PubNub'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.
PubNub'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.