NEW YORK – A widespread outage impacting Amazon CloudFront, a key content delivery network (CDN), left users globally struggling to access numerous online services on February 10, 2026. The disruption, which began around 9:15 PM UTC, affected everything from major platforms like Salesforce and Adobe to streaming services and even communication tools like Discord, highlighting the interconnectedness of modern digital infrastructure. While Amazon Web Services (AWS) restored core DNS resolution within an hour, full recovery, including the propagation of changes to new distributions and TLS certificate provisioning, extended until approximately 4:00 AM UTC on February 11.
The incident stemmed from a DNS resolution failure within CloudFront’s infrastructure, causing the network to return “NXDOMAIN” responses – essentially telling users that the requested services didn’t exist. This cascaded across eight interconnected AWS services, including Route 53, API Gateway, WAF, AppSync, Pinpoint, Transfer Family, and VPC Lattice, according to a report from IsDown.app. The scale of the outage underscores the critical role CDNs play in ensuring a seamless online experience, and the potential for a single point of failure to have far-reaching consequences.
CloudFront, as Amazon explains in its documentation, functions by caching content on servers located in edge locations around the world. When a user requests data – an image, a webpage, a video – the request is routed to the nearest edge location, minimizing latency and improving performance. This system relies heavily on DNS to direct users to the correct server. When DNS resolution fails, as it did on February 10th, the entire network effectively becomes unreachable.
Interestingly, users monitoring services through crowd-sourced platforms like IsDown.app reported problems 23 minutes before AWS issued its first status update. This highlights the growing value of independent monitoring tools in providing early warnings of potential outages, giving teams valuable time to prepare their incident response. The speed with which AWS identified the root cause – a DNS resolution issue – was commendable, but the extended recovery period for change propagation raises questions about the robustness of their update mechanisms.
The outage also brought into focus the security protocols supported by CloudFront. According to AWS documentation, CloudFront supports a range of SSL/TLS protocols, including TLSv1.3, and TLSv1.2, and various ciphers like TLS_AES_128_GCM_SHA256 and ECDHE-RSA-AES128-GCM-SHA256. While these protocols are designed to ensure secure connections, the incident serves as a reminder that even the most sophisticated security measures are vulnerable to underlying infrastructure failures.
The impact wasn’t limited to consumer-facing services. Businesses relying on CloudFront for critical operations, such as content delivery and application performance, experienced disruptions. The incident underscores the demand for organizations to have robust disaster recovery plans in place, including the ability to quickly switch to alternative CDNs or infrastructure providers in the event of an outage.
AWS has not yet released a detailed post-mortem analysis of the February 10th outage, but industry experts anticipate a thorough review of its DNS infrastructure and change management processes. The incident will likely prompt a broader discussion within the cloud computing industry about the need for greater resilience and redundancy in critical infrastructure components.
The recovery process, while ultimately successful, wasn’t without its challenges. New distributions, DNS records, and TLS certificate provisioning were all affected by the change propagation delays, requiring manual intervention and extended monitoring. This highlights the complexity of managing a global CDN and the importance of automated tools for detecting and resolving issues quickly.
Looking ahead, the focus will be on preventing similar incidents from occurring in the future. This will likely involve investments in more robust DNS infrastructure, improved monitoring and alerting systems, and more rigorous testing of change management procedures. The February 10th CloudFront outage serves as a stark reminder that even the most reliable cloud services are not immune to failure, and that proactive planning and resilience are essential for maintaining a stable and secure online environment.
The next scheduled AWS update regarding infrastructure improvements is expected on March 15, 2026. Archysport will continue to monitor the situation and provide updates as they become available.
