PubNub Outage History
PubNub is up right nowPingoru has recorded 55 incidents for PubNub: 10 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 2 | 1 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 2 | 2 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 3 | 3 of 587 (1%) |
Incidents, newest first
Minor May 16, 2025 Presence API errors & latency in US and AP North 24m North America Points of Presence, Asia Pacific Points of Presence, Presence Service
Started May 16, 2025, 09:59 AM UTC· resolved May 16, 2025, 10:23 AM UTC
- monitoring May 16, 2025, 09:59 AM UTC
At 09:05 UTC we detected increased errors and latency for the Presence service in US and AP-North regions. The service has stablized as of 9:30 UTC. Our engineers are monitoring the system.
- resolved May 16, 2025, 10:23 AM UTC
This incident has been resolved.
- postmortem Jun 05, 2025, 09:25 PM UTC
### **Problem Description, Impact, and Resolution** On May 16, 2025 at 09:05 AM UTC, some customers in US and APAC regions experienced elevated error rates and increased latency when using the Presence service. This disruption was caused by an interruption of underlying infrastructure supported by a third-party provider service. This failure also led to delays in resolving the issue, which prolonged the impact. We were able to adjust resource capacity to overcome this and bring the service back to normal. Services were fully restored on May 16, 2025 at 10:23 AM UTC. ### **Mitigation Steps and Recommended Future Preventative Measures** We increased memory on the Presence pods and are working with the third-party provider to address the issues encountered during the incident. To prevent such issues from recurring in the future, we will also work to improve the Presence service to be more resilient to fluctuations in traffic.
Minor May 13, 2025 Increase Latency and Errors in Presence in the US (East and West) and AP-North regions 43m Presence Service
Started May 13, 2025, 12:00 AM UTC· resolved May 13, 2025, 12:43 AM UTC
- investigating May 13, 2025, 12:00 AM UTC
Beginning at 23:22 UTC we detected increased errors and latency for the Presence service in US (East and West) and AP-North regions. Our engineers are investigating the issue and the service has stablized as of 23:52 UTC.
- monitoring May 13, 2025, 12:12 AM UTC
The issue has resolved and we are monitoring the system for stability.
- resolved May 13, 2025, 12:43 AM UTC
This incident has been resolved.
- postmortem May 16, 2025, 12:03 AM UTC
## **Problem Description, Impact, and Resolution** On May 12, 2025 at 23:22 UTC, we observed elevated errors and increased latency for customers using our Presence service in the Virginia \(US-East\), California \(US-West\), and Tokyo \(AP-North\) regions. After discovering the source of the errors and latency, a solution was set up and ready to be implemented, but the incident was resolved before it was implemented. This issue occurred because we could not be sure that the fix would not negatively impact some functionality of the presence system. ## **Mitigation Steps** To prevent a similar issue from occurring in the future, we are ensuring that all presence features work with channel sharding to safely enable the solution to any sudden usage changes.
Minor April 25, 2025 Server Errors and Elevated Latency 1h 41m Publish/Subscribe Service, North America Points of Presence, Asia Pacific Points of Presence, Presence Service and 2 more
Started Apr 25, 2025, 12:51 AM UTC· resolved Apr 25, 2025, 02:32 AM UTC
- investigating Apr 25, 2025, 12:51 AM UTC
At about 12:17 AM UTC, we started to experience elevated latencies and server errors in all PoPs. PubNub Technical Staff is currently investigating and more updates will follow once available. If you are experiencing issues and believe them to be related to this incident, please report them to PubNub Support at [email protected].
- investigating Apr 25, 2025, 01:22 AM UTC
The PubNub Technical Staff is investigating. More updates will follow once available.
- investigating Apr 25, 2025, 01:57 AM UTC
The PubNub Technical Staff continues to investigate. Errors and elevated latency are with some Presence customers. The real-time network services are operational.
- identified Apr 25, 2025, 02:05 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 25, 2025, 02:11 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 25, 2025, 02:32 AM UTC
With no further issues observed, the incident has been resolved. We will follow up soon with a root cause analysis. If you believe you experienced impact related to this incident, please report them to PubNub Support at [email protected].
- postmortem Apr 25, 2025, 07:36 PM UTC
### Problem Description, Impact, and Resolution At approximately 00:17 UTC on April 25, 2025, we observed elevated server errors and increased latency impacting multiple API endpoints, most notably the Presence service. Our engineering team immediately began investigating the issue. We identified that the root cause involved resource contention within a specific component of our backend infrastructure responsible for managing presence state. We implemented targeted configuration changes to better distribute this traffic and alleviate the resource contention. The issue was fully resolved by 02:32 UTC on April 25, 2025. ### Mitigation Steps and Recommended Future Preventative Measures To prevent a similar issue from occurring in the future, we have already implemented specific configuration changes to ensure the responsible backend component can more effectively handle the type of traffic pattern encountered. Furthermore, we are actively working to enhance our monitoring and alerting systems.
Minor March 10, 2025 Presence Server Errors and Elevated Latency 1h 12m North America Points of Presence, European Points of Presence, Asia Pacific Points of Presence, Presence Service and 1 more
Started Mar 10, 2025, 08:25 PM UTC· resolved Mar 10, 2025, 09:38 PM UTC
- investigating Mar 10, 2025, 08:25 PM UTC
At about 6:26 PM UTC, Presence service started to experience elevated latencies and server errors in all PoPs. PubNub Technical Staff is currently investigating and more updates will follow once available. If you are experiencing issues and believe them to be related to this incident, please report them to PubNub Support at [email protected].
- monitoring Mar 10, 2025, 08:38 PM UTC
We have identified the issue and have taken effective remediation actions, and our engineers are diligently monitoring the situation to guarantee that stability is fully restored.
- monitoring Mar 10, 2025, 09:08 PM UTC
We continue to monitor the situation to guarantee that stability is fully restored.
- resolved Mar 10, 2025, 09:38 PM UTC
With no further issues observed, the incident has been resolved. We will follow up soon with a root cause analysis. If you believe you experienced impact related to this incident, please report them to PubNub Support at [email protected].
- postmortem Mar 13, 2025, 03:47 PM UTC
### **Problem Description, Impact, and Resolution** On March 10, 2025, we observed elevated latency and errors in the Presence service across our global points of presence from 18:26 to 18:40 UTC and again from 20:05 to 20:27 UTC. After investigating, we found that a short spike in traffic with an unusual pattern caused a downstream service provider to respond with increased latency, which affected our own response times. While this incident resolved quickly, we are working with the third-party provider to better handle this scenario in the future.
Minor December 11, 2024 Errors and Latency Across All Services in our US-East and US-West Points of Presence 18m Publish/Subscribe Service, Website, Functions Service, North America Points of Presence and 13 more
Started Dec 11, 2024, 10:04 PM UTC· resolved Dec 11, 2024, 10:22 PM UTC
- investigating Dec 11, 2024, 10:04 PM UTC
We are currently investigating an issue that is causing requests in our US-East points-of-presence to fail or respond slowly.
- monitoring Dec 11, 2024, 10:10 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 11, 2024, 10:22 PM UTC
This incident has been resolved. We apologize for any impact this may have had on your service. Don't hesitate to contact us by reaching out to PubNub Support ([email protected]) if you wish to discuss the impact on your service. An RCA will be provided soon.
- postmortem Dec 16, 2024, 05:26 AM UTC
### **Problem Description, Impact, and Resolution** At 21:50 UTC on 2024-12-11 we observed increased latencies and error rates across all services in our US-East point-of-presence and, a few minutes later, in US-West as well. We observed that the PubNub Access Manager \(PAM\) was at the center of the degradation, and an investigation noted that nodes in that service were highly memory constrained. We increased capacity and the issue was mitigated in both points-of-presence at 22:10 UTC, and declared resolved at 22:22 UTC. This issue occurred because a previously unseen pattern of customer behavior overwhelmed a cache in the PAM system, causing memory to become constrained and performance to degrade. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we changed the cache capacity and updated our monitoring to alert on this and similar patterns of behavior.
Minor December 9, 2024 Elevated History Error/Latency in US West Region 1h 18m North America Points of Presence, Storage and Playback Service
Started Dec 09, 2024, 08:42 AM UTC· resolved Dec 09, 2024, 10:00 AM UTC
- investigating Dec 09, 2024, 08:42 AM UTC
Around 07:23 UTC we began to notice increasing errors and latency for History in SJC region(US West).
- identified Dec 09, 2024, 08:55 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Dec 09, 2024, 09:28 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 09, 2024, 10:00 AM UTC
This incident has been resolved with no errors observed for the last 30 minutes. We apologize for any impact this may have had on your service. Don't hesitate to contact us by reaching out to PubNub Support ([email protected]) if you wish to discuss the impact on your service. An RCA will be provided soon.
- postmortem Dec 16, 2024, 11:16 PM UTC
### **Problem Description, Impact, and Resolution** At 07:23 UTC on December 9th, we received alerts indicating high error levels related to storage writer operations in one of our data centers. Shortly after, one of our third-party service providers reported service disruption in their environment. The service provider began the process of replacing the affected nodes. Throughout the restoration process, we closely monitored our systems to assess how the issue impacted our environment. Once all nodes were successfully restored, error levels returned to normal, and all associated alerts were resolved. ### **Mitigation Steps and Recommended Future Preventative Measures** We have worked with our vendor to ensure that nodes of this type will be on redundant infrastructure going forward, so that there is less exposure to this kind of incident.