Berhampur (QAJ)

Compute Configuration and Update Latency in the Asia-Pacific (APAC) Region
27 January 2026, 14:50 UTC
Platform Asia Agra (QAS) Ahmedabad (QAU) Ambala (QAA) Anantapur (PUT) Asansol (QAW) Bangalore (QAH) Bangalore (QBK) Berhampur (QAJ) Bhopal (QAF) Bhopal (QBL) Bhubaneshwar (QAB) Bhubaneshwar(QBM) Chandigarh (QAL) Delhi (QAG) Dhanbad (QAM) Guwahati (QAX) Howrah (QAC) Hyderabad (QAE) Jaipur (QAY) Jamnagar (JGA) Kanpur (KNU) Kochi (QAN) Kolkata (QAR) Kota (KTU) Madurai (IXM) Meerut (QAD) Mumbai (NMI) Mumbai (QAI) Mumbai (QAO) Patna (QBE) Prayagraj (IXD) Pune (PNQ) Raipur (RPR) Ranchi (IXR) Sambalpur (QAK) Salem (SXV) Solapur (SSE) Surat (STV) Visakhapatnam (VTZ)
 
27 January 2026, 14:50 UTC

We are investigating elevated errors and configuration latency to our Pune (PNQ), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) Points of Presence (POPs). 

All other products and services are unaffected by this incident.

 
27 January 2026, 18:51 UTC

Our engineers believe they have identified contributing factor causing the issue impacting our  Pune (PNQ), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) POPs.

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.

 
27 January 2026, 19:00 UTC

Engineering has confirmed the impact to our Pune (PNQ), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) POPs has been mitigated.

 
27 January 2026, 19:16 UTC

Engineering has confirmed that our Pune (PNQ), Bhubaneshwar (QAB), Howrah (QAC), Meerut (QAD), Jamnagar (JGA), Hyderabad (QAE), Madurai (IXM), Delhi (QAG), Ambala (QAA), Bhopal (QAF), Kanpur (KNU), Ranchi (IXR), Bangalore (QAH), Mumbai (QAI), Surat (STV), Prayagraj (IXD), Berhampur (QAJ), Sambalpur (QAK), Solapur (SSE), Salem (SXV), Chandigarh (QAL), Kota (KTU), Dhanbad (QAM) , Raipur (RPR), Kochi (QAN), Anantapur (PUT), Mumbai (QAO), Visakhapatnam (VTZ), Mumbai (NMI), Kolkata (QAR), Jaipur (QAY), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Nagpur Mauda (QBB), Bangalore (QBK) POPs  have been fully restored.

Customers may have experienced delayed Compute configuration changes or elevated 5xx errors fetching newly deployed services from 14:50 to 18:45 UTC.

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.

Status Post, Created Date/Time:    2026-01-27 18:29:02 UTC    

Berhampur (QAJ) New Data Center
09 October 2025, 18:00 UTC
Platform Asia Berhampur (QAJ)
 
09 October 2025, 18:00 UTC

As part of Fastly’s global network expansion, we will be adding Berhampur (QAJ) data center to Fastly's network. 

Traffic served by our  Berhampur (QAJ)  data center will be aggregated into our Asia region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to  Berhampur (QAJ) . As such, some customers may see a change in their bills.

Fastly’s standard billing rates are located at https://www.fastly.com/pricing.

 
09 October 2025, 22:00 UTC

The scheduled maintenance has been completed.

To offer feedback on our status page, click "Give Feedback"