[Action Required] Compute services: Shielding migration from Milan (MXP) to Milan (BGY)
[Action Required] Compute services: Shielding migration from Milan (MXP) to Milan (BGY)
20 October 2026, 01:18 UTC
20 October 2026, 01:18 UTC
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.