Skip to main content
awsdown

Is Amazon CloudFront down?

DegradedLast checked Aug 28, 2026, 5:28 PM UTC

Last 90 days

99.899% uptime · 1 incident
2026-05-31: operational2026-06-01: operational2026-06-02: operational2026-06-03: operational2026-06-04: operational2026-06-05: operational2026-06-06: operational2026-06-07: operational2026-06-08: operational2026-06-09: operational2026-06-10: operational2026-06-11: operational2026-06-12: operational2026-06-13: operational2026-06-14: operational2026-06-15: operational2026-06-16: operational2026-06-17: operational2026-06-18: operational2026-06-19: operational2026-06-20: operational2026-06-21: operational2026-06-22: operational2026-06-23: operational2026-06-24: operational2026-06-25: operational2026-06-26: operational2026-06-27: operational2026-06-28: operational2026-06-29: operational2026-06-30: operational2026-07-01: operational2026-07-02: operational2026-07-03: operational2026-07-04: operational2026-07-05: operational2026-07-06: operational2026-07-07: operational2026-07-08: operational2026-07-09: operational2026-07-10: operational2026-07-11: operational2026-07-12: operational2026-07-13: operational2026-07-14: operational2026-07-15: operational2026-07-16: degraded2026-07-17: operational2026-07-18: operational2026-07-19: operational2026-07-20: operational2026-07-21: operational2026-07-22: operational2026-07-23: operational2026-07-24: operational2026-07-25: operational2026-07-26: operational2026-07-27: operational2026-07-28: operational2026-07-29: operational2026-07-30: operational2026-07-31: operational2026-08-01: operational2026-08-02: operational2026-08-03: operational2026-08-04: operational2026-08-05: operational2026-08-06: operational2026-08-07: operational2026-08-08: operational2026-08-09: operational2026-08-10: operational2026-08-11: operational2026-08-12: operational2026-08-13: operational2026-08-14: operational2026-08-15: operational2026-08-16: operational2026-08-17: operational2026-08-18: operational2026-08-19: operational2026-08-20: operational2026-08-21: operational2026-08-22: operational2026-08-23: operational2026-08-24: operational2026-08-25: operational2026-08-26: operational2026-08-27: operational2026-08-28: operational
2026-05-312026-08-28

What Amazon CloudFront does - and how it fails

Amazon CloudFront is AWS’s global CDN - the front door for websites, APIs, and media. Because it runs at hundreds of edge locations, CloudFront incidents tend to be geographic (elevated errors in some regions of the world) or configuration-driven (a bad deployment propagating to the edge).

  • Elevated 5xx rates at a subset of edge locations
  • Increased cache-miss rates pushing load onto origins
  • Slow or stuck configuration/invalidation propagation
  • Origin-side failures that look like CloudFront errors to users

Recent Amazon CloudFront incidents

  • [RESOLVED] Increased 5xx Errors

    July 16, 2026 · 3h 38m

    Between 12:45 AM and 4:18 AM PDT, we experienced increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity. Our engineers were automatically engaged and immediately began investigating the root cause. By 2:57 AM PDT, we identified the root cause of the issue as an internal constraint on the fleet that manages connections to private VPC origins. When this constraint was reached, the system responsible for distributing routing configuration to our network processors failed to load the updated configuration data correctly, affecting routing of VPC Origin connections. At 3:52 AM PDT, we took multiple mitigation actions that led to to full recovery at 4:18 AM PDT. Now that the issue has been mitigated, customers who temporarily changed their origin type can safely revert these changes. Customers utilizing other origin types were not affected by this issue. The issue has been resolved and the service is operating normally.

Full analyses live in the post-mortem archive.

Amazon CloudFront questions

Is CloudFront down right now?

Check the live status above - and remember CloudFront failures are often regional at the edge. Testing from another network or region can localize the problem quickly.

How do I tell a CloudFront problem from an origin problem?

Look at the error: 502/503 with an x-cache header of “Error from cloudfront” but healthy origin logs points at the edge; errors that appear identically when hitting the origin directly point at your origin.

Does CloudFront have an SLA?

Yes - 99.9% monthly uptime, with tiered credits on claim when it is missed.

Get alerted when Amazon CloudFront breaks

Instant email the moment we detect an incident - affected services and regions included.

Get outage alerts