Storage is experiencing elevated latencies in the Mumbai PoP
Incident Report for PubNub
Postmortem

Problem Description, Impact, and Resolution 

At 09:16 UTC on 2021-03-18, we observed an increase in latency and errors for the History service in the South Asia PoP. We determined that there was an issue with our storage services vendor and immediately opened a ticket with them, the vendor restarted the Storage processes, and error rates dropped significantly at 09:45 UTC, and the incident was fully resolved at 10:21 UTC.

Mitigation Steps and Recommended Future Preventative Measures 

To prevent a similar issue from occurring, we have made optimizations to the Message Actions service, and we are actively working with the vendor to align on their mitigation steps.

Posted Mar 22, 2021 - 22:47 UTC

Resolved
We're genuinely sorry for the disruption today. We'll be back with a Root Cause Analysis of this issue.
Posted Mar 18, 2021 - 11:14 UTC
Monitoring
A fix has been implemented and we are monitoring the results for the next 30 mins.
Posted Mar 18, 2021 - 10:44 UTC
Identified
The issue has been identified, and a fix is being implemented. Most of the latencies/errors have been recovered, and we're closely monitoring a small subset of API calls being latent or resulting in errors.
Posted Mar 18, 2021 - 09:59 UTC
Investigating
At about 09:17 UTC, the History began to experience elevated latencies in the Mumbai PoP. PubNub Technical Staff is investigating and more information will be posted as it becomes available.

If you are experiencing issues that you believe to be related to this incident, please report the details to PubNub Support (support@pubnub.com).
Posted Mar 18, 2021 - 09:34 UTC
This incident affected: Realtime Network (Storage and Playback Service) and Points of Presence (Southern Asia Points of Presence).