Milan (LIN)

Platform Europe Milan (LIN)
 
02 May 2024, 00:00 UTC
[in progress]

Fastly will be adding capacity at our Milan (LIN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 02 May 2024 at 00:00 UTC.

Our estimated duration is 4h. 

When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).

17 April 2024, 20:45 UTC
Platform Europe Milan (LIN)
 
17 April 2024, 20:45 UTC

We are investigating elevated errors to our Milan (LIN) Point of Presence (POP).

 
17 April 2024, 20:50 UTC

Our engineers have identified the contributing factor and are applying a fix to our Milan (LIN) Point of Presence (POP).

All other locations and services are unaffected.

 
17 April 2024, 20:55 UTC

Engineering has confirmed the impact to our Milan (LIN) Point of Presence (POP) has been mitigated.

 
17 April 2024, 21:00 UTC

Engineering has confirmed that our Milan (LIN) Point of Presence (POP) has been fully restored. Customers may have experienced degraded performance from 20:45 to 21:00 UTC.

This incident is resolved.

Platform North America Europe Milan (LIN) New York (LGA)
 
10 July 2023, 21:48 UTC

Fastly Engineering is investigating CDN performance impacting events affecting our Milan (LIN), New York (LGA) POP. Customers may see intermittent periods of latency or elevated errors as traffic has been temporarily rerouted from the POP.

All other regions and services are currently unaffected.

Please subscribe to this status post at https://www.fastlystatus.com/incident/375953 for further updates, and if errors continue or become more frequent contact our support team at https://support.fastly.com 

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.

12 April 2023, 19:07 UTC
Platform Europe Milan (LIN) Milan (MXP)
 
12 April 2023, 19:07 UTC

We are currently investigating elevated errors in our Milan (LIN) Point of Presence (POP).

All other locations and services are unaffected

 
12 April 2023, 19:20 UTC

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

 
12 April 2023, 20:53 UTC

This incident has been resolved.

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

16 September 2022, 19:20 UTC
Platform Europe Milan (LIN)
 
16 September 2022, 19:20 UTC

We're investigating elevated errors in Milan (LIN). All other locations and services are unaffected

 
16 September 2022, 19:33 UTC

This incident has been resolved.

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.

Fujairah (FJR) New Delhi (DEL) Marseille (MRS) Milan (LIN)
 
09 June 2022, 14:10 UTC
Fastly Engineers detected a performance impacting event affecting the Marseille (MRS), Milan (LIN), New Delhi (DEL) and Dubai (FJR) data center from approximately 2022-06-09 10:10 UTC to 2022-06-09 10:16 UTC. All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.