Milan (MXP)

Platform Europe Milan (BGY) Milan (MXP)
 
20 October 2026, 01:18 UTC
[in progress]

Our previous status post about this migration said no action was required. That was incorrect for Compute services that use mxp-milan-it as a shield location. If you have a Compute service that shields at Milan (MXP), you need to update it by November 2, 2026. Fastly can’t make this change for you because the shield location is set in your service’s code or Compute Config Store. We’re sorry for the confusion.

What’s changing?

Fastly is decommissioning the Milan (MXP) POP. Beginning October 26, 2026, and concluding by November 2, 2026, Fastly will gradually redirect shield traffic for the mxp-milan-it shield location to our Milan (BGY) POP.

During this migration period, Compute services that reference mxp-milan-it will be redirected to bgy-milan-it. After the migration period ends, mxp-milan-it will no longer be a valid shield location, and Compute services that still reference it will get an error when creating the shield. How your service behaves after that depends on how your code handles that error.

What’s next? What do I have to do?

Compute services

If your Compute service uses mxp-milan-it as a shield location, update it to bgy-milan-it before November 2, 2026. We recommend making this change as soon as possible.

  1. Find every place your service sets mxp-milan-it as a shield location, including shield names in your code and any values your code loads from a config store.

  2. Replace mxp-milan-it with bgy-milan-it.

  3. If you changed your code, build and deploy a new version of your service. If the shield name comes from a config store, update the stored value.

  4. If you manage your service with Terraform or other automation, update the shield name there too, so a later deployment doesn’t restore mxp-milan-it.

For details on Compute services, see our Shielding documentation.

Varnish Configuration Language (VCL) services

If your VCL service uses standard shielding configuration, no action is required. Fastly will redirect your shield traffic to Milan (BGY) automatically.

If your custom VCL or VCL snippets reference mxp-milan-it or the MXP POP in your own logic, update those references to bgy-milan-it before November 2, 2026.

You can also switch your shield location to “bgy-milan-it” yourself in the Fastly control panel. See our Shielding documentation.

When you switch to bgy-milan-it, your origin servers may see a temporary increase in requests while the cache fills in Milan (BGY).

If you have any questions, please contact our Support team through https://support.fastly.com or your account team.

Platform Europe Milan (BGY) Milan (MXP)
 
08 October 2026, 00:10 UTC

Our engineers are conducting scheduled maintenance to decommission the Milan (MXP) POP. This update will help to consolidate our network footprint in the Italy region. To learn more about shielding concepts, please read: https://www.fastly.com/documentation/guides/getting-started/hosts/shielding/

What’s changing?

Beginning October 26, 2026, and concluding by November 2, 2026, Fastly will gradually redirect shield traffic for the mxp-milan-it shield location to our Milan (BGY) POP. Services that use mxp-milan-it will continue to reference it, and the redirect will happen automatically.

What’s next? What do I have to do?

No action is required. You may update your service configuration to select the new shield location (bgy-milan-it) if you do not want Fastly to automatically transition your shielded content. If you elect to change your shield selection, your origin servers may experience a temporary increase in request volume while the cache re-establishes in BGY.

If you have any questions or concerns, please contact our Support team through https://support.fastly.com or your account team.


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

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.

 
16 April 2026, 18:22 UTC

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.

 
16 April 2026, 18:28 UTC

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.

 
16 April 2026, 18:29 UTC

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.

Status Post, Created Date/Time:    2026-04-16 18:21:26 UTC    

08 December 2025, 19:45 UTC
Platform Europe Milan (MXP)
 
08 December 2025, 19:45 UTC

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

All other products and services are unaffected by this incident.

 
08 December 2025, 20:08 UTC

Our engineers believe they have identified contributing factor causing the issue impacting the Milan (MXP) 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.

 
08 December 2025, 20:10 UTC

Engineering has confirmed the impact to Milan (MXP) (POP)  has been mitigated.

 
08 December 2025, 20:11 UTC

Engineering has confirmed that Milan (MXP) (POP) has been fully restored. Customers may have experienced elevated errors and latency from 19:45 to 19:58 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-12-08 19:56:29 UTC 



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.


15 September 2025, 17:08 UTC
Platform Europe Amsterdam (AMS) Amsterdam (RTM) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Frankfurt (FRA) Helsinki (HEL) London (LCY) London (LHR) London (LON) Lisbon (LIS) Madrid (MAD) Madrid (TOJ) Manchester (MAN) Marseille (MRS) Milan (LIN) Milan (MXP) Oslo (OSL) Munich (MUC) Paris (PAR) Rome (FCO) Sofia (SOF) Stockholm (BMA) Vienna (VIE)
 
15 September 2025, 17:08 UTC

We're currently investigating performance impacts in Europe.

All other locations and services are unaffected.


 
15 September 2025, 17:46 UTC

Our engineers have identified the contributing factor and are developing a fix to our Europe POPs.

All other locations and services are unaffected.

 
15 September 2025, 18:13 UTC

Engineering has confirmed the impact to Europe POPs has been mitigated.

 
15 September 2025, 18:23 UTC

Engineering has confirmed that Europe POPs has been fully restored. Customers may have experienced latency from 17:08 to 18:00 UTC.

This incident is resolved.

To offer feedback on our status page, click "Give Feedback" 

Status Post, Created Date/Time: 2025-09-15 17:35:41 UTC 



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.


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

We are investigating elevated errors to our Platform delivery services.

 
05 September 2024, 21:44 UTC

Our engineers are continuing to investigate the impact to our Platform delivery services.

 
05 September 2024, 22:01 UTC

Our engineers have identified the contributing factor and are applying a fix to our Platform delivery services.

 
05 September 2024, 23:00 UTC

Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Platform delivery services.

 
05 September 2024, 23:34 UTC

Engineering has deployed a fix and have confirmed a gradual recovery to our Platform delivery service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.

 
06 September 2024, 00:48 UTC

Engineering has confirmed that our Platform delivery services have been fully restored. Customers may have experienced elevated errors and latency. In addition, Compute customers may have also experienced delayed configuration deployments from the 5th of September at 19:48 to the 6th of September at 00:48 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

To offer feedback on our status page, click "Give Feedback" 

Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Atlanta (PDK) Boston (BOS) Frankfurt (FRA) Calgary (YYC) Chicago (CHI) Helsinki (HEL) London (LCY) London (LHR) London (LON) Chicago (ORD) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Honolulu (HNL) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) 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)
 
23 July 2024, 12:48 UTC

At approximately 08:00 UTC our engineers began to investigate a large traffic event impacting performance within our Europe and North America regions. 

Standard traffic engineering practices have been deployed in response to this event, in an effort to reduce the potential impact to our customers within the regions. Customer may continue to see elevated errors and latency as mitigation efforts continue to be deployed.

All other products and services are unaffected by this incident.

 
23 July 2024, 14:29 UTC

Our engineers are implementing adjusted mitigation strategies in our North America and Europe regions to continue to balance traffic and manage performance.

Error rates and latency have improved, although customers may still experience intermittent periods of performance impact as traffic engineering continues to be deployed.

 
23 July 2024, 16:37 UTC

Engineering has implemented mitigation strategies and has confirmed a gradual recovery in our North America and Europe regions. 

We are closely monitoring performance in these regions as a top priority as this event continues and will provide a final update once customer and end user experience has been fully restored.

 
23 July 2024, 23:52 UTC

Engineering has confirmed that Europe and North America regions have been fully restored. Customers may have experienced elevated errors and latency from 08:00 to 16:37 UTC.

This incident is resolved.

Affected customers would have experienced impact to varying degrees and to a shorter duration than as set forth above.

To offer feedback on our status page, click "Give Feedback" 

29 June 2023, 18:46 UTC
Platform North America Europe Amsterdam (AMS) Ashburn (IAD) Brussels (BRU) Copenhagen (CPH) Dublin (DUB) Atlanta (PDK) Boston (BOS) Frankfurt (FRA) Calgary (YYC) Chicago (CHI) Helsinki (HEL) London (LCY) London (LHR) London (LON) Chicago (ORD) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Honolulu (HNL) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) 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 Australia / New Zealand South America Africa Amsterdam (AMS) Adelaide (ADL) Seoul (ICN) Bangkok (BKK) Bogota (BOG) Cape Town (CPT) Auckland (AKL) Ghana (ACC) Ashburn (IAD) Dubai (FJR) Brisbane (BNE) Dubai (DXB) Buenos Aires (EZE) Johannesburg (JNB) Brussels (BRU) Christchurch (CHC) Fujairah (FJR) Curitiba (CWB) Copenhagen (CPH) Hong Kong (HKG) Melbourne (MEL) Fortaleza (FOR) Dublin (DUB) Perth (PER) Lima (LIM) Atlanta (PDK) Sydney (SYD) Rio de Janeiro (GIG) Boston (BOS) Frankfurt (FRA) Kuala Lumpur (KUL) Santiago (SCL) Calgary (YYC) Wellington (WLG) Chicago (CHI) Helsinki (HEL) Manila (MNL) Sao Paulo (GRU) Osaka (ITM) London (LCY) London (LHR) London (LON) Chicago (ORD) Chennai (MAA) Singapore (QPG) Columbus (CMH) Lisbon (LIS) Madrid (MAD) Dallas (DFW) Denver (DEN) Manchester (MAN) Detroit (DTW) Marseille (MRS) Tokyo (NRT) Tokyo (TYO) Honolulu (HNL) Hyderabad (HYD) Milan (LIN) Houston (IAH) Milan (MXP) Oslo (OSL) Kansas City (MCI) Munich (MUC) Los Angeles (BUR) Los Angeles (LAX) Paris (PAR) Rome (FCO) Kolkata (CCU) Sofia (SOF) Stockholm (BMA) Miami (MIA) Minneapolis (MSP) Minneapolis (STP) Vienna (VIE) Montreal (YUL) Newark (EWR) Mumbai (BOM) New York (LGA) New York (NYC) Palo Alto (PAO) New Delhi (DEL) 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.
 
20 January 2023, 00:48 UTC

This incident has been resolved.