Fortaleza (FOR)

Retrospective: Impacted Performance in Fortaleza (FOR)
07 July 2023, 17:58 UTC
Edge Cloud Platform South America Fortaleza (FOR)
 
07 July 2023, 17:58 UTC
[closed]

Fastly Engineers detected a performance impacting event affecting the Fortaleza (FOR) data center.

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

 
07 July 2023, 18:03 UTC

This incident has been resolved.

Third Party Service Provider Issues Causing Elevated Errors in South America
10 May 2023, 13:53 UTC
Edge Cloud Platform Third Party Service Provider South America Bogota (BOG) Buenos Aires (EZE) Curitiba (CWB) Fortaleza (FOR) Lima (LIM) Rio de Janeiro (GIG) Santiago (SCL) Sao Paulo (GRU) Sāo Paulo (CGH)
 
10 May 2023, 13:53 UTC
[closed]

We're investigating elevated errors in South America.

All other locations and services are unaffected

 
10 May 2023, 14:23 UTC

Fastly Engineering has observed elevated errors across multiple Points of Presence (POPs) in the region of South America.

This has been identified as an issue with a third party service provider unrelated to Fastly's Edge Cloud Platform, and a fix is being implemented. 

All other locations and services are unaffected.



 
10 May 2023, 14:59 UTC

Traffic in Lima(LIM) has been temporarily rerouted.

All other locations and services are unaffected.

 
10 May 2023, 15:27 UTC

Fastly Engineering has applied our standard acute incident response practices and restored our LIM POP.

Customer services have returned to pre-incident performance levels.

We will continue to monitor the third party service provider issue for recovery. All locations and other services remain unaffected.

 
10 May 2023, 18:18 UTC

This incident has been resolved.

Compute@Edge Configuration Propagation Performance Issues
24 January 2023, 20:52 UTC
Edge Cloud Platform Compute Security Third Party Service Provider Europe Compute@Edge South America NGWAF@Edge Bogota (BOG) Buenos Aires (EZE) Curitiba (CWB) Fortaleza (FOR) Lima (LIM) Rio de Janeiro (GIG) Santiago (SCL) Rome (FCO)
 
24 January 2023, 20:52 UTC
[closed]

We’re currently investigating performance issues with Compute@Edge configuration propagation. All other services are unaffected.


 
24 January 2023, 21:29 UTC

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

 
24 January 2023, 21:56 UTC

Our investigations have identified common network provider issues related to the performance impact for our Compute@Edge services and NGWAF@Edge updates and decision making. Existing rules are operational, but new data is parsed at a slower pace. Fastly Engineering is in the process of performing standard traffic engineering to restore Compute@Edge and NGWAF@Edge services to pre-incident levels. 

 
24 January 2023, 22:22 UTC

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

 
24 January 2023, 23:42 UTC

Fastly has performed traffic engineering to route around the global network provider currently experiencing impact. Our Compute@Edge and NGWAF@Edge services are performing at pre-incident levels. 

This incident is resolved.

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

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

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

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.