Netlify: Degraded performance for hosted DNS changes
Timeline of updates
- resolved
Our DNS provider has mitigated the issues and so we have re-enabled DNS changes through our API and UI. If you created or modified any records in our Hosted DNS service between 1600 UTC and 1745 UTC, you should confirm them with a dns lookup and if the response does not seem correct, remove and recreate them. Note that our system automatically creates records as you apply custom domains and domain aliases to your sites, so if you see a name you applied to a site in our system not working well during those times, you would instead remove and re-add the name in the Site's Domain Settings panel. Our support team is standing by in the helpdesk (support@netlify.com for our paying customers) and our forums (for our free customers) to help if you have any trouble!
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 2021-10-07 17:34 UTC, resolved after 47 min, 1 update(s).
- Title
- Degraded performance for hosted DNS changes
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/59p58bfdcswc
Netlify profileRecent Netlify incidentsAll outages on October 7, 2021Netlify in October 2021MarkdownJSON