Netlify: DNS Resolver And 404 Errors
Timeline of updates
- resolved
We looked into an issue causing some pages to be cached as 404s on at least one CDN node. We identified and reconfigured a bad DNS resolver, and we refreshed all active sites. Follow-up: This was a side effect of a larger Google DNS outage that ended up affecting DNS lookups between our origin servers and the object store that holds uploaded files, causing the 404s some users were seeing. Normally we would have gotten spikes in our exception logging service, but their service was affected by the same Google DNS issue, and that meant they never received our exception reports. We’ve now setup alerting for any spike in these kinds of exceptions on our internal log processing software and will be alerted if something like this happens again. We’re also looked into and repaired the behavior of our (some of) our origin servers not correctly failing over to a secondary DNS service once Google started giving errors.
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: minor) posted by Netlify, started 2017-03-21 12:14 UTC, resolved after 0 min, 1 update(s).
- Title
- DNS Resolver And 404 Errors
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/20wqrbytdrb7
Netlify profileRecent Netlify incidentsAll outages on March 21, 2017Netlify in March 2017MarkdownJSON