For service srv-brojois1do6unkrsjnt0, I used to have custom domains with staging.foo setup to redirect to www.staging.foo. I’ve recently tried to invert it, deleting both custom domains and re-adding staging.foo. However, the 301 from staging.foo to www.staging.foo still exists, causing the site to 404 (as there’s now only 1 custom domain).
I have confirmed that this happens when curling the site directly, so it’s unlikely to be a local cache issue. This only happens on the root path, when I fetch other paths it works as expected (does not 301).