Redirect rules not applied on newly deployed Static Sites

We have monitored deployments since the fix and confirmed redirects are working correctly. We apologize for the disruption.

The fix is fully deployed. Static Site deployments completed between June 11, 04:14 UTC and 11:52 UTC did not apply `_redirects` rules (custom redirects, rewrites, and SPA fallbacks), which could cause unexpected 404 errors. Deployments outside this window were not affected.

If your site was deployed during this window, simply trigger a new deployment - redirects will work again immediately. No repository or configuration changes are needed.

We are monitoring deployments and confirming full recovery. If you still see issues after redeploying, please contact support.

Since June 11, 2026, 04:14 UTC, an update to the Static Site deployment pipeline contains a regression that causes _redirects rules to be ignored on newly completed deployments.

Affected sites may see:
- 404 errors on all pages except files that exist in the build output - most visibly on single-page applications relying on a /* /index.html 200 fallback
- Custom redirect rules (301/302), rewrites, and proxy rules not taking effect

Who is affected
Only sites that completed a deployment after June 11, 2026, 04:14 UTC and use a _redirects file. Sites that have not deployed since then are not affected. Site files themselves are served normally and no data was lost. _headers rules are not affected.