Amazon Web Services suffered a significant CloudFront outage on the morning of the incident, beginning at 0945 UTC and affecting customers using VPC Origins. The disruption caused 5xx server errors that knocked multiple websites and online services offline across various regions. AWS confirmed the issue was limited to CloudFront customers utilizing VPC Origins connectivity, while other origin types remained unaffected.
VPC Origins is a relatively new CloudFront feature that allows customers to serve applications running behind private load balancers through CloudFront without exposing backend infrastructure to the public internet. This architecture provides an additional security layer for organizations wanting to use content delivery network capabilities while maintaining private network configurations. The feature's specialized nature meant the outage had a targeted but significant impact on services relying on this specific configuration.
AWS engineers identified the root cause as a problem with a packet processing subsystem responsible for routing requests from CloudFront edge locations to resources within customer virtual private clouds. The company posted updates on its service status page and recommended affected customers temporarily switch their origin type as a workaround while the engineering team worked on a permanent fix. By 1018 UTC, AWS provided additional technical details but had not yet resolved the underlying issue.
The outage affected several high-profile services. AI developer platform Hugging Face reported its service was unavailable from most regions worldwide. The UK National Lottery confirmed players could not access its website or mobile app, advising users to try again later. Bethesda's Fallout 76 also experienced connectivity problems, with players reporting unusual access difficulties on Reddit. Multiple threads on social media platforms filled with reports from AWS customers describing identical symptoms.
Organizations using CloudFront with VPC Origins should monitor AWS status updates and consider temporarily switching to alternative origin types if business requirements allow. Companies dependent on this specific CloudFront configuration should review their disaster recovery plans and evaluate whether backup content delivery options are necessary. AWS customers should verify their monitoring systems can detect and alert on CloudFront-specific failures to enable faster response during future incidents.
Source: https://www.theregister.com/off-prem/2026/07/16/aws-cloudfront-outage-serves-errors-instead-of-websites/5272421