Minor incident

PubNub: Errors with history readers in FRA

Affected: Storage and History Service, European Points of Presence

Current status of PubNub: Operational — live PubNub status

Timeline

1. Oct 26, 2026, 21:14 UTC
   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]
2. Oct 26, 2026, 21:17 UTC
   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].
3. Oct 26, 2026, 21:46 UTC
   resolved
   This incident has been resolved. If you feel you were impacted, please contact [email protected].
4. Oct 30, 2026, 17:23 UTC
   postmortem
   ### 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.

Updates as published by PubNub (original).