Minneapolis (STP)

CDN Regional Performance Impact

29 June 2023, 18:46 UTC
Platform North America Europe Amsterdam (AMS) Brussels (BRU) Ashburn (IAD) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Frankfurt (HHN) Atlanta (PDK) Helsinki (HEL) Boston (BOS) London (LCY) Calgary (YYC) London (LON) Chicago (CHI) London (LHR) Lisbon (LIS) Madrid (MAD) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Dallas (DFW) Denver (DEN) Paris (PAR) Rome (FCO) Detroit (DTW) Sofia (SOF) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
29 June 2023, 18:46 UTC

We're currently investigating performance impacts in Europe, North America.

All other locations and services are unaffected.

 
29 June 2023, 19:56 UTC

This issue has been identified and a fix is being implemented. 

 
29 June 2023, 21:54 UTC

A fix has been implemented and we are monitoring the results.

 
29 June 2023, 23:54 UTC

This incident has been resolved.

CDN Global Performance Impact

19 January 2023, 23:05 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Rome (FCO) Detroit (DTW) Sofia (SOF) Tokyo (TYO) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
19 January 2023, 23:05 UTC

We're currently investigating potential impact to performance with our CDN services.

 
19 January 2023, 23:06 UTC

A fix has been implemented and we are monitoring the results.

 
19 January 2023, 23:48 UTC
On the 19th of January at 23:00 UTC a configuration change was deployed which impacted performance to global CDN delivery. Fastly Engineering reverted the change resulting in immediate recovery at 23:06 UTC. Fastly's Customer Incident Response team is currently preparing a Fastly Service Advisory of today's incident, and will be made available to Fastly Customers.

OpenSSL - Pending Vulnerability Announcement

28 October 2022, 19:48 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Rome (FCO) Detroit (DTW) Sofia (SOF) Tokyo (TYO) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
28 October 2022, 19:48 UTC

Fastly is aware of an expected critical vulnerability the OpenSSL project is expected to disclose in the near future. We are studying the currently available information surrounding this vulnerability and do not currently believe that Fastly is vulnerable. We will continue to monitor as additional information is released and will provide our customers with more information as available.

 
01 November 2022, 17:09 UTC

Fastly has reviewed the initial notification from OpenSSL regarding CVE-2022-3786 and CVE-2022-3602. We have analyzed the versions of OpenSSL in use at Fastly, and verified that we do not use OpenSSL 3.x. Fastly and customer usage of Fastly services are not vulnerable to CVE-2022-3786 or CVE-2022-3602.

CDN Performance Impact

15 September 2022, 20:10 UTC
Platform North America Europe Asia South America Oceania Africa Amsterdam (AMS) Adelaide (ADL) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Brussels (BRU) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dublin (DUB) Christchurch (CHC) Dubai (DXB) Fortaleza (FOR) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Hyderabad (HYD) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Santiago (SCL) Boston (BOS) Kolkata (CCU) London (LCY) Wellington (WLG) Sāo Paulo (CGH) Calgary (YYC) London (LON) Kuala Lumpur (KUL) Chicago (CHI) Sao Paulo (GRU) London (LHR) Manila (MNL) Mumbai (BOM) Lisbon (LIS) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Seoul (ICN) Milan (LIN) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Palermo (PMO) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Rome (FCO) Detroit (DTW) Sofia (SOF) Tokyo (TYO) Gainesville (GNV) Stockholm (BMA) Honolulu (HNL) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
15 September 2022, 20:10 UTC

We're currently investigating potential impact to performance with our CDN services.

 
15 September 2022, 20:26 UTC

The issue has been identified and a fix is being implemented.

 
15 September 2022, 20:33 UTC

A fix has been implemented and we are monitoring the results.

 
15 September 2022, 20:47 UTC

This incident has been resolved.

CDN Performance Impact

22 August 2021, 08:28 UTC
Amsterdam (AMS) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Buenos Aires (EZE) Ghana (ACC) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dublin (DUB) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Santiago (SCL) Boston (BOS) London (LCY) Wellington (WLG) Sāo Paulo (CGH) London (LON) Kuala Lumpur (KUL) Chicago (CHI) London (LHR) Manila (MNL) Mumbai (BOM) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Tokyo (TYO) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
22 August 2021, 08:28 UTC
We're currently investigating potential impact to performance with our CDN services.

Global CDN Disruption

08 June 2021, 09:58 UTC
Amsterdam (AMS) Bogota (BOG) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Buenos Aires (EZE) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Curitiba (CWB) Johannesburg (JNB) Dublin (DUB) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Lima (LIM) Frankfurt (HHN) Perth (PER) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Santiago (SCL) Boston (BOS) London (LCY) Wellington (WLG) Sāo Paulo (CGH) London (LON) Chicago (CHI) London (LHR) Mumbai (BOM) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Singapore (QPG) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Munich (MUC) Tokyo (HND) Dallas (DFW) Tokyo (NRT) Denver (DEN) Tokyo (TYO) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
08 June 2021, 09:58 UTC
We're currently investigating potential impact to performance with our CDN services.
 
08 June 2021, 10:07 UTC
We are continuing to investigate this issue.
 
08 June 2021, 10:11 UTC
We are continuing to investigate this issue.
 
08 June 2021, 10:21 UTC
We are continuing to investigate this issue.
 
08 June 2021, 10:23 UTC
We are continuing to investigate this issue.
 
08 June 2021, 10:26 UTC
We are continuing to investigate this issue.
 
08 June 2021, 10:44 UTC
The issue has been identified and a fix is being implemented.
 
08 June 2021, 10:57 UTC
The issue has been identified and a fix has been applied. Customers may experience increased origin load as global services return.
 
08 June 2021, 11:57 UTC
A fix was applied at 10:36 UTC. Customers may continue to experience decreased cache hit ratio and increased origin load as global services return.
 
08 June 2021, 12:41 UTC
Fastly has observed recovery of all services and has resolved this incident. Customers could continue to experience a period of increased origin load and lower Cache Hit Ratio (CHR).

Elevated Errors in Ashburn (BWI)

28 April 2021, 15:34 UTC
Platform North America Ashburn (IAD) Atlanta (PDK) Boston (BOS) Calgary (YYC) Chicago (CHI) Columbus (CMH) Columbus (LCK) Dallas (DFW) Denver (DEN) Detroit (DTW) Gainesville (GNV) Honolulu (HNL) Houston (IAH) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) New York (NYC) Palo Alto (PAO) Phoenix (PHX) Portland (PDX) San Jose (SJC) Seattle (BFI) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
28 April 2021, 15:34 UTC
We are aware of a possible issue and are working to determine the scope and impact.
 
28 April 2021, 15:41 UTC
We're investigating elevated errors in Ashburn (BWI). All other locations and services are unaffected
 
28 April 2021, 15:58 UTC
The issue has been identified and a fix is being implemented.
 
28 April 2021, 16:00 UTC
A fix has been implemented and we are monitoring the results.
 
28 April 2021, 16:35 UTC
This incident has been resolved.

Incident - Global CDN Performance Impact

12 January 2021, 15:25 UTC
Amsterdam (AMS) Cape Town (CPT) Chennai (MAA) Auckland (AKL) Ashburn (IAD) Copenhagen (CPH) Brisbane (BNE) Johannesburg (JNB) Dublin (DUB) Frankfurt (FRA) Fujairah (FJR) Melbourne (MEL) Frankfurt (HHN) Perth (PER) Atlanta (PDK) Helsinki (HEL) Hong Kong (HKG) Sydney (SYD) Boston (BOS) London (LCY) Wellington (WLG) London (LON) Chicago (CHI) London (LHR) Mumbai (BOM) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Osaka (ITM) Marseille (MRS) Milan (MXP) Columbus (CMH) Oslo (OSL) Columbus (LCK) Tokyo (HND) Dallas (DFW) Denver (DEN) Tokyo (TYO) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) San Jose (SJC) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
12 January 2021, 15:25 UTC
We are aware of a possible issue and are working to determine the scope and impact.
 
12 January 2021, 15:29 UTC
We're currently investigating potential impact to performance with our CDN services.
 
12 January 2021, 15:38 UTC
We're currently investigating potential impact to performance with our CDN services.
 
12 January 2021, 15:50 UTC
We are continuing to investigate this issue.
 
12 January 2021, 16:03 UTC
We are continuing to investigate this issue.
 
12 January 2021, 16:04 UTC
We are continuing to investigate this issue.
 
12 January 2021, 16:09 UTC
The issue has been identified and a fix is being implemented.
 
12 January 2021, 16:14 UTC
A fix has been implemented and we are monitoring the results.
 
12 January 2021, 16:51 UTC
This incident has been resolved.

Elevated Errors in Minneapolis (STP)

06 November 2020, 23:20 UTC
Minneapolis (STP)
 
06 November 2020, 23:20 UTC
We're investigating elevated errors in Minneapolis (STP). All other locations and services are unaffected
 
06 November 2020, 23:41 UTC
A fix has been implemented and we are monitoring the results.
 
07 November 2020, 01:52 UTC
This incident has been resolved.

CDN Performance Impact

30 August 2020, 10:22 UTC
Amsterdam (AMS) Bogota (BOG) Chennai (MAA) Buenos Aires (EZE) Ashburn (IAD) Copenhagen (CPH) Curitiba (CWB) Dublin (DUB) Frankfurt (FRA) Frankfurt (HHN) Rio de Janeiro (GIG) Atlanta (PDK) Helsinki (HEL) Santiago (SCL) Boston (BOS) London (LCY) London (LON) Chicago (CHI) London (LHR) Mumbai (BOM) New Delhi (DEL) Madrid (MAD) Manchester (MAN) Milan (MXP) Columbus (CMH) Oslo (OSL) Dallas (DFW) Denver (DEN) Stockholm (BMA) Houston (IAH) Vienna (VIE) Kansas City (MCI) Los Angeles (BUR) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Montreal (YUL) Newark (EWR) New York (LGA) Palo Alto (PAO) San Jose (SJC) St. Louis (STL) Toronto (YYZ) Vancouver (YVR)
 
30 August 2020, 10:22 UTC
We're currently investigating performance impacts in India, Latin America and Northern Europe. All other locations and services are unaffected.
 
30 August 2020, 10:37 UTC
We're currently investigating potential impact to performance with our CDN services.
 
30 August 2020, 10:51 UTC
The issue has been identified and a fix is being implemented.
 
30 August 2020, 11:06 UTC
We're continuing to work on a fix for this issue.
 
30 August 2020, 11:27 UTC
Fastly is observing increased errors and latency across multiple regions due to a common IP transit provider experiencing a widespread event. Fastly is actively working on re-routing traffic in affected regions.
 
30 August 2020, 12:04 UTC
Fastly is continuing global mitigation efforts due to a common IP transit provider experiencing a widespread event. Error rates and congestion are elevated but improving as Fastly re-route traffic.
 
30 August 2020, 12:38 UTC
Fastly is continuing global mitigation efforts due to a common IP transit provider experiencing a widespread event. Error rates and congestion remain elevated.
 
30 August 2020, 13:14 UTC
Fastly is continuing global mitigation efforts due to a common IP transit provider experiencing a widespread event. Traffic has been re-routed in CMH, CPH, and MSP. Error rates and congestion remain elevated in multiple regions.
 
30 August 2020, 14:42 UTC
Fastly is continuing global mitigation efforts due to a common IP transit provider experiencing a widespread event. Traffic has been re-routed in CMH, CPH, and MSP. We are seeing some signs of improvement but continue to see elevated errors in multiple regions.
 
30 August 2020, 14:49 UTC
Fastly is continuing global mitigation efforts due to a common IP transit provider experiencing a widespread event. Traffic has been re-routed in CMH, CPH, and MSP. We are seeing some signs of improvement but continue to see elevated errors in multiple regions.
 
30 August 2020, 15:39 UTC
Fastly has observed a decrease in errors for most customers. Some customers may experience additional impact as global backbones continue to adjust routing. We are monitoring closely and will update as information becomes available.
 
30 August 2020, 15:42 UTC
Fastly has observed a decrease in errors for most customers. Some customers may experience additional impact as global backbones continue to adjust routing. We are monitoring closely and will update as information becomes available.
 
30 August 2020, 16:02 UTC
We are continuing to monitor for any further issues.
 
30 August 2020, 17:10 UTC
This incident has been resolved.