CDN Global Performance Impact
CDN Global Performance Impact
19 August 2026, 17:02 UTC
19 August 2026, 17:02 UTC
We are investigating increased latency for purging at our Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) Points of Presence (POPs).
All other products and services are unaffected by this incident.
19 August 2026, 22:09 UTC
19 August 2026, 22:09 UTC
Our engineers believe they have identified contributing factor causing the issue impacting the Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) status page components.
We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.
All other products and services are unaffected by this incident.
19 August 2026, 23:04 UTC
19 August 2026, 23:04 UTC
Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to the Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) status page components.
All other locations and services are unaffected.
19 August 2026, 23:27 UTC
19 August 2026, 23:27 UTC
Engineering has confirmed the impact to the Purging, Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) status page components has been mitigated.
19 August 2026, 23:30 UTC
19 August 2026, 23:30 UTC
Engineering has confirmed that our Minneapolis (STP), Ranchi (IXR), Mumbai (QAI), Surat (STV), Ambala (QAV), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL), LA - Santa Clara (RHV), LA - West Florida (VNC), LA - Salt Lake City (BTF), LA - Denver (APA), LA - Pompano (PPM), LA - Richmond (RIC), LA - Nashville (BNA), LA - Memphis (MEM), LA - Pittsburgh (PIT), LA - Roseville (STP) POPs and Purging service has been fully restored.
Customers may have experienced delayed cache purge propagation, with some purge requests lost from 17:02 to 23:24 UTC.
Customers who purged content during this window should expect that some previously purged content may have been served as stale until the fix was applied.
This incident is resolved.
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.