The August 15, 2026 deadline to migrate from legacy eCDN zones to proxy zones has passed, and legacy zones and HTTP-only traffic are no longer supported. If your site still relies on a legacy zone, or your DNS (including any stacked third-party CDN) still points to a legacy zone’s CNAME, your site is at risk of an outage when that zone is removed or auto-migrated. This risk isn’t always visible: as soon as your proxy zone is active, eCDN routes traffic based on the incoming hostname regardless of what your upstream DNS still points to, so traffic can look normal even when your DNS hasn’t been updated to reflect the migration. Review your configuration and migrate to proxy zones as needed.
Where: This change applies to B2C Commerce.
When: Legacy eCDN zone support ended on August 15, 2026. Salesforce is now proactively migrating legacy zones and removing inactive legacy zones on a rolling basis.
How: In Business Manager, confirm your zone status under Administration | Sites | Embedded CDN Settings. If you’ve already created a proxy zone, verify that your DNS, including any stacked or third-party CDN, points to the proxy zone’s CNAME rather than the legacy zone’s. Once complete, remove the legacy zone. If you haven’t migrated yet, create a proxy zone and copy over your Logpush and Rate Limit rules before you update DNS. Don’t remove a legacy zone until you confirm your DNS points to the proxy zone.