Is PubNub Down?

### 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 of the infrastructure supporting these APIs, temporarily outpacing the autoscaling configuration for that service. Service returned to normal at approximately 21:12 UTC. Following continued monitoring, the incident was declared resolved at 21:46 UTC. ### Mitigation Steps and Recommended Future Preventative Measures  We increased capacity to address the immediate issue. To prevent a similar issue from occurring in the future, we are reviewing the autoscaling configuration of the service so it can better respond to similar traffic surges. --- [2026-10-26T21:46:22.881Z] (resolved) This incident has been resolved. If you feel you were impacted, please contact support@pubnub.com. --- [2026-10-26T21:17:52.280Z] (monitoring) A fix has been implemented and we are monitoring the results. If you feel you have been impacted by this, please reach out to support@pubnub.com. --- [2026-10-26T21:14:19.239Z] (investigating) Users may be experiencing elevated errors with History readers in the Frankfurt point-of-presence. We are working on remediation and will update this as we make progress. If you believe you are affected and would like to discuss, please reach out to support@pubnub.com

### 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 the number of servers available to handle requests. Our team identified the deployment as the source of the errors and initiated a rollback to the previous version.  Error rates returned to normal at approximately 21:07 UTC on October 26, 2026. We continued monitoring as latency improved, returning fully to normal at approximately 21:46 UTC. The incident was declared resolved at 21:55 UTC. ### Mitigation Steps and Recommended Future Preventative Measures  To prevent a similar issue from occurring in the future, we have temporarily paused Presence code deployments while we investigate the update’s resource usage. Before releasing the update again, we will address the identified issues and test resource consumption and service stability, with extra attention to the conditions that we experienced in this scenario. --- [2026-10-26T21:55:38.894Z] (resolved) This incident has been resolved, and we will follow up with a postmortem. If you have questions or concerns, please reach out to support@pubnub.com. --- [2026-10-26T21:17:11.103Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-10-26T21:12:05.001Z] (monitoring) A fix for this issue has been implemented and we are monitoring the results. If you feel you have been impacted by this, please reach out to support@pubnub.com. --- [2026-10-26T21:07:35.258Z] (investigating) Users may be experiencing elevated error and latency rates with the Presence API. We are working on remediation and will update this as we make progress. If you believe you are affected and would like to discuss, please reach out to support@pubnub.com

### **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 affected. The issue began during a software update to the Presence service in Frankfurt. The new version was not compatible with the previous version while both were running at the same time. That caused Presence servers in the region to restart repeatedly, and requests that could not reach a healthy server returned errors. Our team identified the update as the cause and rolled it back. Service returned to normal at approximately 16:13 UTC. ### **Mitigation Steps and Recommended Future Preventative Measures** We are fixing the incompatibility before this update is released again. We are also adding tests that run old and new versions side by side before every Presence release, rolling out updates one availability zone at a time, and improving our rollback procedure so it does not run incompatible versions together. --- [2026-10-22T16:35:59.083Z] (resolved) This incident has been resolved. If you feel you were impacted, please contact support@pubnub.com. --- [2026-10-22T16:19:28.409Z] (monitoring) A fix has been implemented and we are monitoring the results. If you were impacted by this issue, or feel you are still being impacted, please reach out to support@pubnub.com. --- [2026-10-22T16:12:51.106Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-22T16:02:03.516Z] (investigating) Users may be experiencing elevated error and latency rates from our Frankfurt and Bombay points-of-presence. We are working on remediation and will update this as we make progress. If you are affected, reach out to support@pubnub.com.