NEW YORK – A widespread outage affecting Amazon’s CloudFront content delivery network (CDN) left users globally unable to access a range of websites and online services for a period on Wednesday, March 25, 2026. The disruption, which began around 10:00 AM EST (1400 UTC), impacted everything from major news outlets to streaming platforms and gaming services, highlighting the critical role CDNs play in modern internet infrastructure.
The error message displayed to users, as reported across social media and confirmed by Archysport, simply stated, “The request could not be satisfied.” Further details indicated a blocked request, suggesting a server-side issue preventing connections. The error message also included a Request ID: EBLujTz575rxIzhLrXR_U-HYVh6PZaQz_7ZzFIVdResBEpF3Wn9jJw==, which Amazon uses for troubleshooting.
What is CloudFront and Why Does This Matter?
Amazon CloudFront is a key component of the internet’s architecture, functioning as a content delivery network. As explained by Amazon Web Services, CloudFront speeds up the distribution of web content – including images, videos, and application code – by caching it on servers located in numerous data centers around the world, known as edge locations. When a user requests content, CloudFront delivers it from the nearest edge location, reducing latency and improving performance. Essentially, it brings the internet closer to the user.
This system is crucial for handling traffic spikes and ensuring reliable access to online services. Without a CDN like CloudFront, websites would be significantly slower and more prone to outages, particularly during periods of high demand. The outage underscores the concentration of internet infrastructure in the hands of a few major providers.
The Scope of the Disruption
While the full extent of the impact is still being assessed, reports quickly surfaced indicating widespread issues. Users attempting to access popular websites encountered the “request could not be satisfied” error. Initial reports focused on disruptions to services reliant on Amazon Web Services (AWS), but the issue quickly expanded to affect a broader range of online platforms.
The outage also impacted several sports-related websites and streaming services, causing frustration for fans attempting to follow live scores, news, or watch games. The timing of the disruption, coinciding with the early stages of several major league spring training schedules, added to the inconvenience for sports enthusiasts.
Amazon’s Response and Potential Causes
Amazon Web Services acknowledged the issue and stated that they were investigating. According to the error message itself, the problem could stem from “too much traffic or a configuration error.” Amazon’s documentation suggests that troubleshooting steps involve reviewing CloudFront configurations to facilitate prevent similar errors in the future.
In a blog post from November 2025, Amazon announced flat-rate pricing plans for CloudFront, along with new features including support for Lambda@Edge, CAPTCHA, and mutual TLS (mTLS). While the outage doesn’t appear directly related to these new features, it highlights the complexity of managing a global CDN infrastructure. The company has also been focused on improving security, offering features like DDoS protection through AWS Shield Standard.
Experts suggest several potential causes, ranging from a software bug to a misconfiguration of network settings. The possibility of a distributed denial-of-service (DDoS) attack, while not confirmed, was also raised as a potential factor, given the scale of the disruption.
What Happens Now?
As of 1:30 PM EST (1730 UTC) on March 25, 2026, Amazon reported that the issue had been resolved and services were returning to normal. However, the incident serves as a stark reminder of the fragility of the internet and the dependence on a small number of key infrastructure providers.
The incident is likely to prompt further scrutiny of CDN infrastructure and the require for greater redundancy, and resilience. Companies relying on CloudFront and other CDNs will likely review their disaster recovery plans and consider diversifying their infrastructure to mitigate the risk of future outages.
The next scheduled update from Amazon regarding the incident is expected at 4:00 PM EST (2000 UTC), where they are expected to provide a more detailed post-mortem analysis of the cause and the steps taken to prevent a recurrence. Archysport will continue to monitor the situation and provide updates as they grow available.
Users experiencing lingering issues are advised to clear their browser cache and cookies, or contact their internet service provider for assistance.
Related reading
