AWS CloudFront Outage History
3 incidents recorded over the last 365 days, 3 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded AWS CloudFront Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 16, 2026 | Increased 5xx ErrorsIncreased 5xx Errors | 443h 17m | Resolved |
| Mar 2, 2026 | Increased Error RatesIncreased Error Rates | 3854h 40m | Resolved |
| Mar 1, 2026 | Increased Error RatesIncreased Error Rates | 3871h 45m | Resolved |
How to Read This CloudFront Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CloudFront acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single CloudFront outage in this window ran 161d 7h, against a mean recovery of 113d 11h. If you depend on CloudFront in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.