PubNub Outage History
14 incidents recorded over the last 365 days, 12 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded PubNub Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | Errors with history readers in FRA### 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… | 32 min | Resolved |
| Oct 26, 2026 | Errors and Latency for Presence### 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… | 48 min | Resolved |
| Oct 22, 2026 | Errors and Latency for Presence in FRA and BOM### **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… | 33 min | Resolved |
| Oct 22, 2026 | Certificate Issue Causing Potential Connection Issues### **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… | 1h 36m | Resolved |
| Oct 9, 2026 | Increased Subscribe error rate and latency observed globally### **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… | -75 min | Resolved |
| Aug 25, 2026 | Potential for some missed messages for subscribers in US East PoP### **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… | 1h 28m | Resolved |
| Aug 15, 2026 | Scheduled Maintenance: PubNub Admin PortalThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Aug 14, 2026 | Global Errors and Failures with Publish and Functions, Delays with Events & Actions### **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… | 0 min | Resolved |
| Jun 10, 2026 | Replication failures## 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… | 31 min | Resolved |
| Jun 9, 2026 | Global Errors and Failures with Publish and Functions, Delays with Events & Actions### **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… | 0 min | Resolved |
| Mar 24, 2026 | Connectivity Issues Affecting a Subset of Subscriptions### **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… | 51 min | Resolved |
| Mar 7, 2026 | Scheduled Maintenance: PubNub Admin PortalThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jan 1, 2026 | Delay in Publishing Messages to Storage Globally### **Problem Description, Impact, and Resolution** On January 1, 2026 at 00:00 UTC, we observed elevated latency in our History service across multiple regions. Customers may have experienced delays in message… | 34 min | Resolved |
| Nov 20, 2025 | Increased errors observed and resolved**Problem Description, Impact, and Resolution** Starting at 16:46 UTC on Nov. 20, 2025, we noticed a small number of errors with the publish API in the North American and Asia Pacific regions. The system automatically… | 0 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next PubNub incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This PubNub Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before PubNub acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single PubNub outage in this window ran 3h, against a mean recovery of 60 min. If you depend on PubNub in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.