1. Home
  2. Outages
  3. Amazon Web Services
  4. 29 Oct 2026

OutageThursday 29 October 2026Ended 30 Oct, 01:21

Amazon Web Services outage on 29 October 2026

Problem reports about Amazon Web Services rose to outage level at 21:45 Central European time on Thursday 29 October 2026 and stayed there for 3 h 36 min.

They peaked at 104 reports in 15 minutes at 23:31, about 12 times the usual level for that time of day, and 661 reports came in while the outage lasted.

Reports reached outage level in 4 countries, the US, Mexico, India, Canada.

12 other services had an outage spike at the same time.

Is Amazon Web Services down right now?

Started
21:45
Thu 29 Oct, Central European time
At outage level
3 h 36 min
Ended 01:21 on 30 Oct
Busiest 15 minutes
104
reports, at 23:31
Reports during the outage
661
Peak about 12× the usual level
Timeline

Reports from Thu 15:45 to Fri 07:30

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Problem reports about Amazon Web Services rose to outage level at 21:45 Central European time on Thursday 29 October 2026 and stayed there for 3 h 36 min. They peaked at 104 reports in 15 minutes at 23:31, about 12 times the usual level for that time of day, and 661 reports came in while the outage lasted. Reports reached outage level in 4 countries, the US, Mexico, India, Canada. 12 other services had an outage spike at the same time.
Around the world

Where people reported it that day

Each country's reports on 29 October, against the usual level there. Outage means reports stayed at outage level for half an hour or more; above usual, for an hour or more.

CountryThat dayReports
The USOutage1,228
MexicoOutage305
BrazilNormal223
IndiaOutage222
CanadaOutage120
JapanNormal95
The UKNormal80
ColombiaNormal71
FranceNormal38
SpainNormal29
The PhilippinesNormal23
ItalyNormal22
Same time

Other services with an outage at the same time

Their reports also reached outage level while Amazon Web Services's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

More

Amazon Web Services: live status and other outages

Check whether Amazon Web Services is down right now: the live page shows the last 24 hours and fixes to try.

October 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

Amazon Web Services outage on 29 October 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/aws-amazon-web-services/2026-10-29/" title="Amazon Web Services outage on 29 October 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/aws-amazon-web-services/outages/2026-10-29/">Amazon Web Services outage on 29 October 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/aws-amazon-web-services/outages/2026-10-29/"><img src="https://isitdownrightnow.app/share/aws-amazon-web-services/2026-10-29.png" alt="Amazon Web Services outage on 29 October 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Amazon Web Services outage on 29 October 2026](https://isitdownrightnow.app/share/aws-amazon-web-services/2026-10-29.png)](https://isitdownrightnow.app/services/aws-amazon-web-services/outages/2026-10-29/)Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.