Cloudflare DNS failures hit .co domains April 17-18 2024

What happened

Cloudflare experienced intermittent DNS resolution failures for websites using .co top-level domains between April 17 21:50 UTC and April 18 02:00 UTC. The incident lasted approximately 4 hours and 10 minutes, affecting DNS queries for Colombian country code domains globally. Cloudflare implemented a fix by 21:55 UTC on April 17 and monitored results before declaring the incident resolved. This was separate from an earlier Analytics API availability issue on April 16 that affected reporting func

Business impact

Enterprise websites using .co domains faced potential complete inaccessibility during the outage window, resulting in lost revenue and user abandonment. Teams relying solely on Cloudflare DNS had no failover option, exposing critical gaps in infrastructure redundancy. The 4-hour duration exceeded ty

Background

Colombia's .co domain gained popularity as a generic alternative to .com, with major brands adopting it for brevity and brand recognition. Cloudflare handles DNS for millions of domains globally, making single points of failure particularly damaging. DNS outages are among the most severe infrastructure failures because they prevent all website access regardless of server health.

What this means for your team

Implement multi-provider DNS strategies using services like Amazon Route 53 or NS1 alongside Cloudflare to prevent single points of failure. Configure DNS monitoring tools like Pingdom or Datadog to alert on resolution failures within minutes rather than waiting for user reports. Test DNS failover p

What to watch

Monitor Cloudflare's postmortem analysis for root cause details and prevention measures. Track whether similar ccTLD-specific failures occur with other country codes in Cloudflare's infrastructure.