Disruption at 11:08 UTC — 11 reports over 16m. Most common: 'Network' (14%); reports from India, Ukraine and Spain.
No problems reported at Amazon Web Services right now
Problem reports for Amazon Web Services are at their usual level right now. The most recent incident was about 71 days ago.
reports · 24 h · /15 min
1h–15m–5m–
Amazon Web Services not working for you?
what people report · last 24 h
Not working100%
where from · last 24 h
no located reports in this window
outage map · last 24 h
live pulse
- report🇺🇸Slow / glitchy71d
- report🇱🇻Problem report - Riga71d
- report🇮🇳API errors - Bengaluru71d
- report🇪🇸API errors - Madrid71d
- report🇮🇳Service - Mumbai71d
- report🇮🇳Website - Hyderabad71d
catalogHosted on Amazon Web Services: Fortnite.
patternThe Amazon Web Services outage of 20 Oct 2025 took down Snapchat and Amazon.
Amazon Web Services outage record
all services by year →6 incidents in the past 12 months — 2 major, the worst on 2025-10-20 with 1,569 reports over 7h 15m.
Since 2017, down.now has recorded 13 outage days on Amazon Web Services, 2 of them major; the largest was Oct 20, 2025 with 1,569 reports.
Incident at 02:20 UTC — 32 reports over 1h 23m.
Incident at 13:54 UTC — 59 reports over 1h 36m.
Incident at 16:09 UTC — 85 reports over 2h 33m.
Major outage — problem reports stayed above normal; 1,520 reports over 23h 12m.
- reports
- 1,520
- duration
- 23h 12m
- peak
- 25 / 15 min @ 00:30 UTC
reports · 2025-10-21 · /15 min
incident timeline
- 19:34Problem reports started climbing.
- 18:47Problem reports faded.
outage map
Major outage — problem reports stayed above normal; 1,569 reports over 7h 15m.
- reports
- 1,569
- duration
- 7h 15m
- peak
- 125 / 15 min @ 09:45 UTC
Amazon Web Services outage — also down: Snapchat and Amazon.
Incident at 18:22 UTC — scattered reports over 2h 42m.
2021
biggest outages of 2021 →
2 recorded outage days — the worst on Dec 7, 165 reports, mostly from the United States.
Disruption at 15:38 UTC — 29 reports over 23m. Most common: 'Not working' (54%); reports from the United States, Chile, Algeria and 5 more countries.
Outage at 15:40 UTC — 165 reports over 2h 6m. Most common: 'Not working' (33%); most reports from the United States.
2019
biggest outages of 2019 →
1 recorded outage day — 79 reports on Apr 25, mostly from the United States.
Outage at 16:17 UTC — 79 reports over 1h 31m. Most common: 'Not working' (1%); most reports from the United States.
2018
biggest outages of 2018 →
2 recorded outage days — the worst on Mar 2, 65 reports, mostly from the United States.
Outage at 07:27 UTC — 39 reports over 22m. Most common: 'Not working' (56%); reports from India, the United States, Türkiye and 10 more countries.
Disruption at 19:37 UTC — 65 reports over 52m. Most reports from the United States.
2017
biggest outages of 2017 →
1 recorded outage day — 111 reports on Feb 28, mostly from the United States.
Outage at 18:02 UTC — 111 reports over 2h 46m. Most reports from the United States.
Amazon Web Services comments
anonymous · no accountcommon questions
Is Amazon Web Services down right now?
Problem reports for Amazon Web Services are at their usual level right now. The most recent incident was about 71 days ago.
Is Amazon Web Services down for everyone or just me?
Right now down.now isn't seeing a broad Amazon Web Services outage, so the problem is most likely local to you — your connection, your device, or the app itself. Try the app on mobile data instead of Wi-Fi, then restart the router. If reports start arriving from other people, this page flips to an outage within minutes.
When did Amazon Web Services last go down?
The last recorded Amazon Web Services incident was about 71 days ago, on 2026-07-24. The outage record below has the peak time, duration and what people reported.
How can I report a problem with Amazon Web Services?
Use the report panel on this page and pick what's not working — it takes one tap and no account. Reports are anonymous, and they feed the live signal on this page immediately.
How does down.now know if Amazon Web Services is down?
Down.Now watches two crowd signals for Amazon Web Services — anonymous reports submitted here, and public social-media posts about it — and compares the live volume against what's normal for that hour of the day. A sustained spike above that baseline opens an incident, which is usually visible before an official confirmation. We measure what users report, not Amazon Web Services's servers directly.