San Francisco

29 June 2023, 18:46 UTC
Edge Cloud Platform North America Europe Amsterdam (AMS) Brussels (BRU) Copenhagen (CPH) Ashburn (IAD) Dublin (DUB) Ashburn (WDC) Frankfurt (FRA) Atlanta (ATL) Frankfurt (HHN) Atlanta (FTY) Helsinki (HEL) Atlanta (PDK) Lisbon (LIS) Boston (BOS) Calgary (YYC) London London (LCY) Chicago (CHI) London (LHR) London (LON) Madrid (MAD) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Columbus (CMH) Munich (MUC) Columbus (LCK) Oslo (OSL) Dallas (DAL) 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) 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)
 
29 June 2023, 18:46 UTC
[closed]

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.

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.
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.

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.

20 February 2022, 09:03 UTC
https://fanout.io/ Fanout Control Panel London Singapore San Francisco
 
20 February 2022, 09:03 UTC
[closed] The api.fanout.io domain is not always resolving. We are investigating the issue.
 
20 February 2022, 10:47 UTC
Our DNS provider is failing to respond in certain regions.
 
20 February 2022, 11:37 UTC
Our DNS provider has made a fix and we are monitoring the situation.
28 April 2021, 15:34 UTC
Edge Cloud Platform North America Ashburn (IAD) Ashburn (WDC) Atlanta (ATL) Atlanta (FTY) Atlanta (PDK) Boston (BOS) Calgary (YYC) Chicago (CHI) Columbus (CMH) Columbus (LCK) Dallas (DAL) Dallas (DFW) Denver (DEN) Detroit (DTW) Gainesville (GNV) Honolulu (HNL) Houston (IAH) 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)
 
28 April 2021, 15:34 UTC
[closed] 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.
21 April 2021, 05:00 UTC
San Francisco
 
21 April 2021, 05:00 UTC
[closed] Our hosting provider is performing upgrades, and there may be some latency and packet loss during this period.
 
21 April 2021, 05:00 UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
 
21 April 2021, 09:00 UTC
The scheduled maintenance has been completed.
02 March 2021, 15:53 UTC
https://fanout.io/ Fanout Control Panel London Singapore San Francisco
 
02 March 2021, 15:53 UTC
[closed] Fanout domain names including fanout.io and fanoutcdn.com may not be resolving. We are investigating the issue.
 
02 March 2021, 18:28 UTC
Our DNS provider has fixed the issue, and we are monitoring the situation.
 
02 March 2021, 19:39 UTC
This incident has been resolved.
01 November 2020, 18:46 UTC
https://fanout.io/ Fanout Control Panel London Singapore San Francisco
 
01 November 2020, 18:46 UTC
[closed] Fanout domain names including fanout.io and fanoutcdn.com may not be resolving. We are investigating the issue.
 
01 November 2020, 19:04 UTC
Our DNS provider has acknowledged higher than normal errors.
 
01 November 2020, 22:09 UTC
Our DNS provider is still working on the issue.
 
01 November 2020, 22:55 UTC
The issue has been fixed and we are monitoring it.
 
01 November 2020, 23:21 UTC
This incident has been resolved.
06 October 2020, 08:10 UTC
London San Francisco
 
06 October 2020, 08:10 UTC
[closed] We are experiencing severe connectivity problems right now, possibly due to high load. Originally this started in the London region. Failover to other regions was initiated, but this caused SF to fail. We are still investigating the cause.
 
06 October 2020, 12:49 UTC
Service has stabilized. Some accounts may be getting rate limited.
 
06 October 2020, 19:00 UTC
We determined the problem to be an unexpectedly large amount of traffic near our London region. It defeated our rate limiting by overwhelming our load balancers. In the future we will aim to have far more load balancer capacity than is necessary during normal conditions, to ensure high traffic from one customer doesn't take us down.