Europe
Fastly will be adding capacity at our Manchester (MAN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 17 November 2026 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 at https://support.fastly.com.
Fastly will be adding capacity at our Manchester (MAN) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 10 November 2026 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 at https://support.fastly.com.
The scheduled maintenance for Manchester (MAN) has been postponed and was not performed. We will announce a new status post once a new date is confirmed.
Traffic in Amsterdam (RTM) has been temporarily rerouted.
All other locations and services are unaffected.
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.
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.
Replace mxp-milan-it with bgy-milan-it.
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.
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.
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.
Fastly will be adding capacity at our Marseille (MRS) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 21 September 2026 at 21:30 UTC.
Our estimated duration is 6h.
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 at https://support.fastly.com.
The scheduled maintenance has been completed.
We have identified an issue that caused elevated error rates (HTTP 429/503) and timeouts for Object Storage in the Frankfurt (FRA), Ashburn (IAD) Points of Presence (POP)s.
All other products and services are unaffected by this incident.
Between 13:00 UTC and 19:12 UTC on June 25, 2026, customers routing traffic through our London City (LCY) and London Heathrow (LHR) Points of Presence (POPs) may have experienced elevated Time to First Byte (TTFB), request timeouts, and HTTP 503 errors. Customers using LHR as a shield origin — including those routing through LCY — were most affected. The highest concentration of errors occurred between approximately 16:00 and 16:40 UTC.
Service degradation began to improve at approximately 16:40 UTC and was fully resolved by 19:12 UTC.
Customer impact: Customers in the affected traffic paths may have observed increased latency, elevated error rates, and in some cases failed requests during this window.
Current status: This incident is fully resolved. All services at LCY and LHR are operating normally.
If you have questions about how this incident affected your services, please contact our support team by emailing us at support@fastly.com.
Traffic in London (QQP) has been temporarily rerouted.
All other locations and services are unaffected.
Fastly will be adding capacity at our Amsterdam (AMS) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 16 June 2026 at 22:00 UTC.
Our estimated duration is 8h.
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 at https://support.fastly.com.
The scheduled maintenance has been completed.