Potential for some missed messages for subscribers in US East PoP
Affected: Publish/Subscribe ServiceNorth America Points of Presence
PubNub Outage History
PubNub is up right nowPubNub had 11 outages in the last 2 years totaling 17h 52m of downtime — averaging 0.5 incidents per month.
There were 11 PubNub outages since September 7, 2025 totaling 17h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
Global Errors and Failures with Publish and Functions, Delays with Events & Actions
Affected: Publish/Subscribe ServiceFunctions ServiceNorth America Points of PresenceEuropean Points of PresenceAsia Pacific Points of PresenceSouthern Asia Points of Presence
Timeline · 2 updates
Replication failures
Affected: Publish/Subscribe ServiceNorth America Points of Presence
Timeline · 4 updates
Connectivity Issues Affecting a Subset of Subscriptions
Affected: Publish/Subscribe Service
Timeline · 3 updates
Delay in Publishing Messages to Storage Globally
Affected: North America Points of PresenceStorage and Playback ServiceEuropean Points of PresenceAsia Pacific Points of PresenceSouthern Asia Points of Presence
Timeline · 4 updates
Increased errors observed and resolved
Timeline · 2 updates
- resolved Nov 20, 2025, 05:36 PM UTC
Increased errors (5XX) observed On Nov. 20, 2025 between 16:36 UTC and 16:48 UTC, publish and replication errors (5xx) were observed in North American and Asia Pacific regions, and immediately resolved. Please contact [email protected] if you believe you were impacted by the issue and would like to discuss it with our team.
- postmortem Nov 25, 2025, 01:05 AM UTC
**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 recovered with all functionality fully restored by 16:50 UTC on Nov. 20, 2025.
Increased latency and errors observed in US-West
Affected: Publish/Subscribe ServiceNorth America Points of PresencePresence ServiceAccess Manager Service
Timeline · 15 updates
Elevated latencies and errors for multiple services in US-west and US East
Affected: Publish/Subscribe ServiceNorth America Points of PresenceStorage and Playback ServiceStream Controller ServicePresence ServiceAccess Manager ServiceDNS ServiceMobile Push GatewayApp Context Service
Timeline · 5 updates
Potential for some missed messages for subscribers in IAD
Affected: Publish/Subscribe ServiceNorth America Points of Presence
Timeline · 5 updates
Elevated Event & Action Error In FRA Region
Affected: European Points of Presence
Timeline · 5 updates
Increased Error Rate and Latency for Presence
Affected: Presence Service
Timeline · 3 updates
- monitoring Sep 07, 2025, 06:45 PM UTC
We experienced increased latencies and error rates in our Tokyo, San Jose, and Virginia points-of-presence from 18:14 - 18:17 UTC. A fix was deployed and we are monitoring the situation.
- resolved Sep 07, 2025, 07:02 PM UTC
The issues affected the Presence service from 18:14 - 18:17 UTC. We will follow up with a post-mortem soon. We apologize for the impact this may have had on your service. Please reach out to us by contacting PubNub Support ([email protected]) if you wish to discuss the impact on your service.
- postmortem Sep 12, 2025, 11:19 PM UTC
### **Problem Description, Impact, and Resolution** At 18:14 UTC on September 7, 2025 we observed increased error rates and latency for our Presence service in our San Jose, Virginia, and Tokyo regions. We increased capacity in those regions and the issue was resolved at 18:17 UTC. This issue was a recurrence of the issue [experienced on September 2, 2025](https://status.pubnub.com/incidents/1n8xk6w5y9lk), where a bug in one of our APIs allowed a request to execute an operation that exceeded assumed limits in extreme cases, causing out-of-memory conditions for the Presence service. ### **Mitigation Steps and Recommended Future Preventative Measures** In the previous instance of this issue, we placed restrictions on the API in question; those changes were not restrictive enough, which allowed for this recurrence. We have corrected that oversight, as well as increased memory capacities in this area of our system as an additional safeguard.