Netlify: Missing redirects and headers in some deploys
Timeline of updates
- resolved
Between 17:47 and 20:49 UTC, any deploys that were intended to contain more than 100 redirects and/or 100 custom header rules specified were instead deployed with only their first 100 redirects and/or header rules. New deployments will no longer be affected, and we recommend a new deploy to repair any builds made during that time with larger intended lists.
From Netlify’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.netlifystatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Netlify, started 2022-02-21 17:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Missing redirects and headers in some deploys
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/90pny6kdbb79
Netlify profileRecent Netlify incidentsAll outages on February 21, 2022Netlify in February 2022MarkdownJSON