
Domain Stuck on Deleted Netlify Account
TL;DR: A developer's production site went offline after they deleted their Netlify account without first removing a custom domain. Despite changing nameservers, Netlify's network continued to intercept traffic, serving a 404 error. The issue required manual intervention from Netlify support to purge the DNS zone.
Key facts
- Category
- Infrastructure
- Impact
- Low
- Published
- Source
- Netlify Community
Full summary
A developer reports a critical production site is down after a domain became stuck on a deleted Netlify account, causing a persistent 404 error.
A user reported a critical issue where a custom domain remained associated with a Netlify account that had already been deleted. The developer had forgotten to manually remove the domain before closing the account. Although the domain's nameservers were updated to point to Cloudflare, Netlify's Anycast network continued to route traffic for the domain. This resulted in all visitors seeing a Netlify 404 error page instead of the live site, causing a complete outage for a client's production environment. The core of the problem was that the DNS zone was not automatically purged from Netlify's systems upon account deletion, leaving it in a "stuck" state requiring manual support intervention.
This incident highlights a potential operational pitfall for teams using managed hosting platforms. It underscores the importance of following a strict offboarding checklist when migrating services or closing accounts, specifically ensuring all assets like custom domains are properly dissociated before termination. For businesses, this type of configuration error can lead to significant downtime, impacting revenue and customer trust. The problem is particularly subtle because standard DNS changes may not be sufficient to resolve it if the platform's internal routing retains a claim on the domain. This situation creates a dependency on the platform's support team for resolution, which can introduce unpredictable delays in restoring a critical service.
Why it matters
This incident highlights a critical operational risk where improper account decommissioning on a managed platform can lead to prolonged service outages, even after DNS records are updated. It underscores the need for careful offboarding procedures.
Business impact
A misconfiguration during account closure led to a complete production site outage, causing potential revenue loss and reputational damage. The resolution required manual support intervention, introducing unpredictable recovery times for a critical business asset.
Tags
Primary source: Netlify Community