Traffic in Ambala (QAA) has been temporarily rerouted.

All other locations and services are unaffected.

Update: The responding escalation manager erroneously marked the incorrect status page component in their original post which caused the wrong title to appear within customer support chat and email threads. This was corrected to display the proper component (Ambala (QAA)). 

All other components, locations and services were unaffected by this event. 

As part of Fastly’s global network expansion, we will be adding a Riyadh (RUH) data center to Fastly's Saudi Arabia network. 

Traffic served by our Riyadh (RUH) data center will be aggregated into our Saudi Arabia region for billing and stats purposes.

We expect that some traffic currently served by our data centers in neighboring regions will shift to Riyadh (RUH) . 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.

Traffic in Dhanbad (QAM), Raipur (RPR) has been temporarily rerouted.

All other locations and services are unaffected.

Fastly Engineers detected a performance impacting event affecting the Tokyo (NRT) data center.

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

Fastly Engineers detected a performance impacting event affecting the Varanasi (VNS) data center.

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

We are investigating elevated errors to our Pune (PNQ), Varanasi (VNS), 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), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) 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 Pune (PNQ), Varanasi (VNS), 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), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) 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 Pune (PNQ), Varanasi (VNS), 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), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) Point of Presence (POP) has been mitigated.

We are continuing to monitor the situation closely.

Engineering has confirmed that impact for Pune (PNQ), Varanasi (VNS), 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), Chennai (QAP), Kolkata (QAR), Agra (QAS), Patna (QBE), Ahmedabad (QAU), Bhopal (QBL), Guwahati (QAX), Bhubaneshwar(QBM), Asansol (QAW), Bangalore (QBK), Noida (QBD), Lucknow (QAZ), Delhi-Vikaspuri (HDO), Ambala (QAV), Vijaywada (QBI), Warrangal (QBJ), Ludhiana (QBA), Shimla (QBF), Kochi (QBO), Port Blair (IXZ), Srinagar-Nahota (QBG), Hyderabad (QBN), Siliguri (IXB), Shillong (SHL) Point of Presence (POP) has been fully restored. Customers may have experienced elevated errors from 07:11 to 07:55 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 Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) 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 Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) 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 Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs has been mitigated.

Engineering has confirmed that our Hyderabad (HYD), Kolkata (CCU), Mumbai (BOM), New Delhi (DEL), Amsterdam (AMS), Brussels (BRU), Copenhagen (CPH), Dublin (DUB), Frankfurt (FRA), Helsinki (HEL), Lisbon (LIS), London (LCY), London (LON), Madrid (MAD), Manchester (MAN), Milan (LIN), Milan (MXP), Munich (MUC), Oslo (OSL), Rome (FCO), Sofia (SOF), Stockholm (BMA), Christchurch (CHC), Dubai (DXB), Fujairah (FJR), Melbourne (MEL), Seoul (ICN), Singapore (QPG), Sydney (SYD), Tokyo (NRT), Wellington (WLG), Bangkok (BKK), Bogota (BOG), Buenos Aires (EZE), Fortaleza (FOR), Lima (LIM), Rio de Janeiro (GIG), Santiago (SCL), Ghana (ACC), Ashburn (IAD), Atlanta (PDK), Boston (BOS), Calgary (YYC), Chicago (CHI), Dallas (DFW), Denver (DEN), Detroit (DTW), Gainesville (GNV), Honolulu (HNL), Houston (IAH), Kansas City (MCI), Los Angeles (BUR), Miami (MIA), Minneapolis (MSP), Montreal (YUL), New York (LGA), Phoenix (PHX), San Jose (SJC), Seattle (BFI), St. Louis (STL), Toronto (YYZ), Vancouver (YVR), Sao Paulo (GRU), Paris (PAR), Los Angeles (LAX), Sydney (WSI), Amsterdam (RTM), Jacksonville (JAX), Milan (BGY), Brasilia (BSB) POPs  have been fully restored.

Customers may have experienced elevated 5xx errors from 17:13  to 17: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.

Fastly Engineers detected a performance impacting event affecting the Hong Kong (HKG) data center.

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

Our engineers believe they have identified contributing factor causing the issue impacting Hong Kong (HKG) POP.

Our engineers are now developing a fix, and we will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services remain unaffected by this incident.

Engineering has confirmed that Hong Kong (HKG) POP has been fully restored. Customers may have experienced slow loading and elevated errors from 1:57am to 2:17am 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.

We are investigating elevated errors to our Port Blair (IXZ) 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  Port Blair (IXZ) 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.

This event has been resolved.