PubNub Status

Resolved: This incident has been resolved. If you feel you were impacted, please contact [email protected].

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 [email protected].

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 [email protected]

Postmortem: ### 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.

Resolved: This incident has been resolved, and we will follow up with a postmortem. If you have questions or concerns, please reach out to [email protected].

Monitoring: We are continuing to monitor for any further issues.

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 [email protected].

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 [email protected]

Postmortem: ### 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.

Resolved: This incident has been resolved, and we will follow up with a postmortem. If you have questions or concerns, please reach out to [email protected].

Monitoring: We are continuing to monitor for any further issues.

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 [email protected].

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 [email protected]

Resolved: This incident has been resolved. If you feel you were impacted, please contact [email protected].

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 [email protected].

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 [email protected]

Postmortem: ### 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.

Resolved: This incident has been resolved, and we will follow up with a postmortem. If you have questions or concerns, please reach out to [email protected].

Monitoring: We are continuing to monitor for any further issues.

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 [email protected].

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 [email protected]

Postmortem: ### 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.

Resolved: This incident has been resolved, and we will follow up with a postmortem. If you have questions or concerns, please reach out to [email protected].

Monitoring: We are continuing to monitor for any further issues.

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 [email protected].

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 [email protected]

Postmortem: ### 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.

Resolved: This incident has been resolved, and we will follow up with a postmortem. If you have questions or concerns, please reach out to [email protected].

Monitoring: We are continuing to monitor for any further issues.

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 [email protected].

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 [email protected]