This blip was caused by configuration changes we made to our marketing site (www), which is distinct from any control plane (api/dash) or edge services provided

This blip was caused by configuration changes we made to our marketing site (www), which is distinct from any control plane (api/dash) or edge services provided to our customers. Specifically, we were breaking out our "www" subdomain as a separately managed zone, and some of the configuration wasn't properly migrated. This resolution failure was regrettable, but there was no impact to the service we provide for our customers.