As part of Fastly’s global network expansion, we will be adding Chennai (QAP) data center to Fastly's Asia-Pacific (APAC) network. 

Traffic served by our  Chennai (QAP)  data center will be aggregated into our APAC region for billing and stats purposes.

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

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

As part of Fastly’s global network expansion, we will be adding Lucknow (QAZ) data center to Fastly's Asia-Pacific (APAC) network. 

Traffic served by our Lucknow (QAZ) data center will be aggregated into our APAC region for billing and stats purposes.

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

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

The scheduled maintenance has been completed.

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

We are investigating elevated errors to our Singapore (QPG) Point of Presence (POP).

Our engineers are continuing to investigate elevated errors to our Singapore (QPG) POP.

Our engineers believe they have identified contributing factor causing the issue impacting the Singapore (QPG) status page component.

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. 

Engineering has confirmed the impact to Singapore (QPG) POP has been mitigated.

Engineering has confirmed that Singapore (QPG) POP has been fully restored. Customers may have experienced elevated errors and latency from 14:38 to 17:50 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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.

We are investigating elevated errors to our Dubai (DXB) Point of Presence (POP).

All other products and services are unaffected by this incident.

Our engineers believe they have identified contributing factor causing the issue impacting the Dubai (DXB) status page component.

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.

Engineering has confirmed the impact to Dubai (DXB) POP has been mitigated.

Engineering has confirmed that Dubai (DXB) POP has been fully restored. Customers may have experienced elevated 5xx errors and increased latency from 07:30 to 10:40 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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.

Fastly Engineers detected a performance impacting event affecting the Singapore (QPG) data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

As part of Fastly’s global network expansion, we will be adding two new data centers, Asansol (QAW) and Noida (QBD) to Fastly's Asia network.

Traffic served by our Asansol (QAW) and  Noida (QBD) data centers 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  these new Points of Presence (POPs) . As such, some customers may see a change in their bills.

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

The scheduled maintenance has been completed.

As part of Fastly’s global network expansion, we will be adding Bangalore (QBK) data center to Fastly's Asia-Pacific (APAC) network. 

Traffic served by our Bangalore (QBK) data center will be aggregated into our APAC region for billing and stats purposes.

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

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

The scheduled maintenance has been completed.

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

As part of Fastly’s global network expansion, we will be adding Bhubaneshwar(QBM), Nagpur Mauda (QBB) data center to Fastly's Asia  network. 

Traffic served by our  Bhubaneshwar(QBM), Nagpur Mauda (QBB) 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  Bhubaneshwar(QBM), Nagpur Mauda (QBB). As such, some customers may see a change in their bills.

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

The scheduled maintenance has been completed.

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

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.

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.

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.

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.

As part of Fastly’s global network expansion, we will be adding Guwahati (QAX) data center to Fastly's Asia-Pacific (APAC) network. 

Traffic served by our Guwahati (QAX) data center will be aggregated into our APAC region for billing and stats purposes.

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

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

The scheduled maintenance has been completed.

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