Amazon Web Services outages and problems
User reports, last 24 hours
204 reports in total, counted in 15-minute windows
In the last hour, 7 problem reports came in for Amazon Web Services, against about 12 at this time on a usual day. Over the last 24 hours there were 204 reports. Worldwide, most recent reports were about EC2 (25%) and cloudfront (13%). The last spike in reports was 49 h ago and lasted 19 min. These are user reports from the US, where most people report Amazon Web Services problems.
Around the world right now: normal in 71 other countries. Most reports in the last hour: Japan 3 · Brazil 1 · Mexico 1. By country
- NormalClose to the usual level24 h · 204 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAbout 12 an hour now
In the past 24 hours, 204 user reports came in for Amazon Web Services. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.
The busiest 15-minute window had 9 reports, about 13 hours ago. That stays below our outage threshold, so it doesn't count as downtime.
Amazon Web Services in November 2026
- Problem reports in November
- 42,453
- Outage spikes
- 10
- Periods of elevated reports
- 23
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for Amazon Web Services worldwide.
Share of 16 recent reports that said what was wrong, from every country listed below.
Amazon Web Services reports around the world
In the last 24 hours, 469 problem reports about Amazon Web Services came in from 45 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| The US numbers above | Normal | 13 | 218 |
| Japan | Normal | 3 | 31 |
| Brazil | Normal | 1 | 52 |
| Mexico | Normal | 1 | 10 |
| Indonesia | Normal | 1 | 2 |
| Thailand | Normal | 1 | 2 |
| Chile | Normal | 1 | 2 |
| Saudi Arabia | Normal | 1 | 1 |
| The UK | Normal | 0 | 21 |
| India | Normal | 0 | 18 |
| Germany | Normal | 0 | 12 |
| Italy | Normal | 0 | 9 |
Each country's status compares its reports with the usual level there. 60 more countries had 91 reports in the last 24 hours. Map outlines: Natural Earth.
Amazon Web Services problem spikes, last 30 days
In the last 30 days, Amazon Web Services had 11 outage spikes and 33 periods of elevated reports. The longest lasted 35 h 47 min, on 12 November.
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 3 reports
- Tue 27 Oct: 5 reports (elevated reports that day)
- Wed 28 Oct: 300 reports (elevated reports that day)
- Thu 29 Oct: 1,254 reports (outage spike that day)
- Fri 30 Oct: 849 reports (elevated reports that day)
- Sat 31 Oct: 265 reports
- Sun 1 Nov: 241 reports (elevated reports that day)
- Mon 2 Nov: 679 reports (elevated reports that day)
- Tue 3 Nov: 689 reports (elevated reports that day)
- Wed 4 Nov: 873 reports (outage spike that day)
- Thu 5 Nov: 634 reports (elevated reports that day)
- Fri 6 Nov: 591 reports (outage spike that day)
- Sat 7 Nov: 1,392 reports
- Sun 8 Nov: 161 reports (elevated reports that day)
- Mon 9 Nov: 1,554 reports (outage spike that day)
- Tue 10 Nov: 638 reports (elevated reports that day)
- Wed 11 Nov: 625 reports (outage spike that day)
- Thu 12 Nov: 16,420 reports (outage spike that day)
- Fri 13 Nov: 5,693 reports
- Sat 14 Nov: 1,351 reports (elevated reports that day)
- Sun 15 Nov: 1,059 reports (outage spike that day)
- Mon 16 Nov: 2,746 reports (outage spike that day)
- Tue 17 Nov: 2,783 reports (outage spike that day)
- Wed 18 Nov: 2,299 reports (outage spike that day)
- Thu 19 Nov: 950 reports (elevated reports that day)
- Fri 20 Nov: 756 reports (elevated reports that day)
- Sat 21 Nov: 264 reports
- Sun 22 Nov: 55 reports
-
Elevated reports
Fri 20 Nov, 05:11–05:30Lasted 19 min11peak reports
-
Elevated reports
Thu 19 Nov, 22:30–22:56Lasted 26 min26peak reports
-
Elevated reports
Thu 19 Nov, 21:10–21:36Lasted 26 min29peak reports
-
Elevated reports
Thu 19 Nov, 17:25–17:42Lasted 17 min32peak reports
-
Elevated reports
Thu 19 Nov, 03:10–03:56Lasted 47 min15peak reports
-
Outage
Wed 18 Nov, 20:45–00:39Lasted 3 h 54 min62peak reports
-
Elevated reports
Wed 18 Nov, 15:20–15:36Lasted 17 min34peak reports
-
Elevated reports
Wed 18 Nov, 08:21–08:47Lasted 26 min14peak reports
36 earlier spikes in this period.
By country
In the last 25 days, most Amazon Web Services problem reports came from the US (44,661), Brazil (8,970) and Japan (7,443). Brazil had the most days at outage level: 11 of 25. The latest outage spike was on Thursday 19 November, in Brazil and India.
- The US10 outage days · 2 elevated44,661
- Brazil11 outage days · 1 elevated8,970
- Japan6 outage days7,443
- The UK4 outage days3,846
- Canada4 outage days · 1 elevated3,560
- India5 outage days3,243
- Mexico2 outage days1,624
- Israel1 outage day1,431
- Outage spike
- Elevated reports
- Normal
- No data yet
Each square is one day. It turns red when reports stayed at outage level for half an hour or more, and amber when they stayed above the usual level for an hour or more. The number on the right is the country's total since 29 October 2026, when country history starts. A wider gap marks a Monday. Point at a square, or tap it, for that day's numbers. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. Monthly reports for all services
How to fix Amazon Web Services not working
Amazon Web Services is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach aws.amazon.com over your own connection, right now. Nothing is sent to us or stored.
Open the AWS Health Dashboard
Open the official status page at health.aws.amazon.com/health/status and check for open events in your region. If an event is listed, wait for the provider to resolve it before you change your own configuration.
Confirm the console region
Look at the region selector in the top right of the Management Console. Switch to the region where your resources live; a wrong choice makes healthy services look missing, and the CLI needs the same value in --region or your profile config.
Refresh your AWS credentials
Sign out of the Management Console. Clear cookies for the sign-in domain if the page loops, then sign in again; CLI or SDK errors such as ExpiredToken usually need fresh credentials in ~/.aws/credentials. Run aws sts get-caller-identity to confirm the active identity.
Test from another network
Load the console on mobile data or a home connection. If it works there, your office network or proxy is blocking console.aws.amazon.com. For private resources, check the route table and security group rules for the subnet before you open a ticket with your network team.
Common Amazon Web Services error messages
What each message means and what to try. The wording can differ a little between app versions.
-
An error occurred (AccessDenied) when calling the ListBuckets operation: Access Denied
- Means
- Your AWS credentials reached the service, but the identity you signed in with is not allowed to run that operation.
- Fix
- Check the IAM policy attached to your user or role and add the permission you need, or sign in with an identity that already has it. If you do not manage permissions yourself, ask whoever runs the account.
-
You are not authorized to perform this operation.
- Means
- The console or API blocked the action because your account, role, or organization policy does not grant it.
- Fix
- Confirm you are signed in to the correct account and region, since permissions can differ between them. Then review the attached policy for the missing action.
While Amazon Web Services is down: what to use instead
- Microsoft Azure Use Azure if you need cloud computing, storage, or application hosting while AWS is unavailable.
- Google Cloud Use Google Cloud to run workloads or store data that you can move from AWS.
- Local development Run a local copy of your application for testing while AWS-hosted services are unavailable.
- Wait and retry Save your work and retry the AWS service once it responds again.
Fix Amazon Web Services on Windows, Mac, Android and iPhone
Amazon Web Services on Windows
- Fix
- Clear your web browser cache and cookies, or check that your Windows Firewall is not blocking connections to Amazon Web Services. Also, ensure your system clock is synchronized, as incorrect time settings can cause AWS authentication errors.
- Check
- Visit the official AWS Service Health Dashboard to check for active outages affecting your region. You can also use the command prompt to test your network connection to the Amazon Web Services console.
ping aws.amazon.comTest whether Amazon Web Services's servers replynslookup aws.amazon.comCheck that Amazon Web Services's DNS resolvestracert aws.amazon.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadAmazon Web Services on Mac
- Fix
- Clear your browser cache and verify that your macOS network settings or firewall are not blocking Amazon Web Services. If you are using the AWS CLI, make sure your profile credentials are correct and active.
- Check
- Check the AWS Service Health Dashboard using Safari or another browser to see if there is an ongoing outage. You can also use the terminal to test your connectivity to Amazon Web Services endpoints.
ping -c 4 aws.amazon.comTest whether Amazon Web Services's servers replynslookup aws.amazon.comCheck that Amazon Web Services's DNS resolvestraceroute aws.amazon.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadAmazon Web Services on Android
- Fix
- Force stop the AWS Console app and clear its cache in your device's application settings. If problems persist, check for updates in the Google Play Store or reinstall the app.
- Check
- Open the AWS Console app to see if it reports connection failures, or use your mobile browser to check the Amazon Web Services status page.
Amazon Web Services on iPhone and iPad
- Fix
- Restart the AWS Console app or reinstall it from the App Store to clear corrupt temporary files. You can also try switching from Wi-Fi to cellular data to rule out local network issues.
- Check
- Look for pending updates for the AWS Console app in the App Store. Alternatively, visit the Amazon Web Services status page on Safari to check for platform-wide issues.
Biggest Amazon Web Services problems so far
-
1
1,398reports in 15 min
-
2
207reports in 15 min
-
3
178reports in 15 min
Ranked by the most problem reports in one 15-minute window. Our archive started on 5 October 2026, so earlier problems are not counted. Times are Central European time.
Problems at the same time as Amazon Web Services
In the last 30 days, all 44 of Amazon Web Services's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Archive of Our Own30 times
- Bank of America28 times
- ADP28 times
- Microsoft 36526 times
- USPS26 times
- OpenAI25 times
How many of Amazon Web Services's spikes overlapped one of theirs.
During the latest spike
Amazon Web Services: Fri 20 Nov, 05:11 to 05:30
- Microsoft Outlook, outage,12 Nov 17:42 to 21 Nov 13:37
- Chase, outage,16 Nov 15:26 to 10:34
- PlayStation Network, outage,17 Nov 09:05 to 21 Nov 01:17
- Amazon, outage,17 Nov 11:42 to 09:04
- Microsoft 365, outage,19 Nov 11:52 to 08:44
- Gmail, outage,19 Nov 12:15 to 07:58
- Bank of America, outage,19 Nov 12:15 to 05:52
- Bell MTS, outage,19 Nov 12:26 to 06:02
56 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report Amazon Web Services problems
The busiest hour for reports about Amazon Web Services is 17:00 to 18:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 11 reports on an average day
- 01:00 to 02:00: 10 reports on an average day
- 02:00 to 03:00: 9.5 reports on an average day
- 03:00 to 04:00: 7.7 reports on an average day
- 04:00 to 05:00: 7.1 reports on an average day
- 05:00 to 06:00: 6.1 reports on an average day
- 06:00 to 07:00: 5.3 reports on an average day
- 07:00 to 08:00: 4.5 reports on an average day
- 08:00 to 09:00: 4.1 reports on an average day
- 09:00 to 10:00: 3.3 reports on an average day
- 10:00 to 11:00: 3.2 reports on an average day
- 11:00 to 12:00: 2.9 reports on an average day
- 12:00 to 13:00: 4.4 reports on an average day
- 13:00 to 14:00: 7.8 reports on an average day
- 14:00 to 15:00: 14 reports on an average day
- 15:00 to 16:00: 21 reports on an average day
- 16:00 to 17:00: 30 reports on an average day
- 17:00 to 18:00: 35 reports on an average day
- 18:00 to 19:00: 28 reports on an average day
- 19:00 to 20:00: 26 reports on an average day
- 20:00 to 21:00: 24 reports on an average day
- 21:00 to 22:00: 18 reports on an average day
- 22:00 to 23:00: 15 reports on an average day
- 23:00 to 00:00: 12 reports on an average day
By day of the week
- Monday: 419 reports on an average Monday
- Tuesday: 252 reports on an average Tuesday
- Wednesday: 441 reports on an average Wednesday
- Thursday: 434 reports on an average Thursday
- Friday: 345 reports on an average Friday
- Saturday: 173 reports on an average Saturday
- Sunday: 146 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 42 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when Amazon Web Services goes down
Teams of every size run production apps on Amazon Web Services, a cloud platform for compute, storage, databases, and networking. An outage interrupts console access, API calls, and the workloads behind them; the status above tracks whether user problem reports are above their usual level in 15-minute windows over the last 24 hours, and it does not monitor the service itself.
You may see the management console hang on sign-in while API calls return server errors, because control-plane actions like launching an EC2 instance or changing a security group depend on those endpoints. Existing workloads may keep serving traffic while new launches and autoscaling events fail. S3 uploads stall, Lambda invocations time out, RDS connections drop, and CloudFront requests return errors. Trouble is usually regional or tied to one service, so a failed call in one availability zone does not mean every workload is down.
Amazon Web Services IP address, servers and network
- IPv4 addresses
- 13.32.121.33
Show all 4
- 13.32.121.41
- 13.32.121.53
- 13.32.121.54
- IPv6 addresses
- 2600:9000:2240:8400:1c:a813:8500:93a1
Show all 8
- 2600:9000:2240:c600:1c:a813:8500:93a1
- 2600:9000:236e:2e00:1c:a813:8500:93a1
- 2600:9000:236e:5400:1c:a813:8500:93a1
- 2600:9000:236e:5800:1c:a813:8500:93a1
- 2600:9000:236e:da00:1c:a813:8500:93a1
- 2600:9000:236e:e200:1c:a813:8500:93a1
- 2600:9000:236e:ec00:1c:a813:8500:93a1
- Network
- AS16509 · Amazon.com, Inc., registered in the United States
- Served through
- Amazon CloudFront · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Amazon Route 53
- HTTPS certificate
- Issued by Amazon, valid until 5 Mar 2027 (102 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 140 ms
Checked from our server in Frankfurt, Germany, 20 h ago, for aws.amazon.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from aws.amazon.com. Fastest from Dallas (71 ms), slowest from Tokyo (1,596 ms). Every location connected through Amazon.com, Inc. (AS16509), using 12 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 326 ms | 13.32.121.33data centre in Frankfurt |
| ViennaAustria | Up | 201 ms | 3.165.206.65data centre in Vienna |
| MilanItaly | Up | 155 ms | 99.86.171.80data centre in Milan |
| ParisFrance | Up | 153 ms | 3.162.38.14data centre in Paris |
| AmsterdamNetherlands | Up | 157 ms | 18.65.39.29data centre in Amsterdam |
| MadridSpain | Up | 180 ms | 13.224.83.66data centre in Madrid |
| WarsawPoland | Up | 218 ms | 3.165.206.28data centre in Vienna |
| DallasUSA | Up | 71 ms | 13.225.61.95data centre in Dallas |
| Los AngelesUSA | Up | 77 ms | 3.167.192.114data centre in Los Angeles |
| São PauloBrazil | Up | 171 ms | 13.227.207.112data centre in São Paulo |
| SingaporeSingapore | Up | 254 ms | 13.35.163.22data centre in Singapore |
| TokyoJapan | Up | 1,596 ms | 143.204.238.22data centre in Stockholm |
Checked with check-host.net from its servers in these cities 20 h ago, for aws.amazon.com. Time is how long each server took to load the page. Data-centre cities come from the names the network gives its servers.
Amazon Web Services FAQ
Is Amazon Web Services down right now?
Why does the AWS Management Console reject my sign-in when my password is correct?
Why can my EC2 instance or S3 bucket fail from one region while other AWS services work?
Why does my Lambda function time out when the rest of the console works?
How do I get help when my AWS account is locked or billing blocks access?
Service updates from @awscloud
No posts about problems from @awscloud in the last 14 days. The latest is from .
Contact Amazon Web Services support
- Official status pagehealth.aws.amazon.com/health/status
- Help centreaws.amazon.com/support
- Contact formaws.amazon.com/contact-us
- Websiteaws.amazon.com
- X (Twitter)x.com/awscloud
Tip: when Amazon Web Services is down, its official status page is the quickest way to confirm the cause and see when a fix is expected.
About Amazon Web Services
- Category
- Cloud Platform
- Founded
- 2006
- Country
- United States
How we track Amazon Web Services
The status on this page comes from user-submitted problem reports for Amazon Web Services, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Amazon Web Services, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from Amazon Web Services's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.