PubNub outage, 1 January 2026

Delay in Publishing Messages to Storage Globally

Started
Resolved
1 Jan 2026, 01:00 UTC (after 35 min)
Impact
Minor
Affected
North America Points of Presence, Storage and Playback Service, European Points of Presence, Asia Pacific Points of Presence, Southern Asia Points of Presence

Last update from PubNub

### **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 persistence and history availability during this period. The issue was caused by a mismatch in newly created persistence tables. Specifically, required columns for message metadata were missing from the new tables, resulting in failed write operations and backed-up queues. This created downstream pressure on our storage systems, leading to higher latency in history processing. We mitigated the issue by manually applying the correct updates across all affected persistence spaces. A...

5 Jan 2026, 17:01 UTC

Read the full incident on the official PubNub status page

Is PubNub down now?

This page is the record of one past incident. For the live status, see Is PubNub down right now? - it reads the official status page every 2 minutes.

Other PubNub incidents

  1. Increased Subscribe error rate and latency observed globally

  2. Potential for some missed messages for subscribers in US East PoP

  3. Global Errors and Failures with Publish and Functions, Delays with Events & Actions

  4. Replication failures

  5. Global Errors and Failures with Publish and Functions, Delays with Events & Actions

  6. Connectivity Issues Affecting a Subset of Subscriptions

  7. Increased errors observed and resolved

  8. Increased latency and errors observed in US-West

All recorded PubNub incidents