Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".
Problems in the last 24 hours
The graph below depicts the number of Amazon Web Services reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Amazon Web Services. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Amazon Web Services users through our website.
- Website Down (78%)
- Sign in (11%)
- Errors (11%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Township of Evan
|
Website Down | 10 days ago |
|
New York City
|
Website Down | 13 days ago |
 Ciudad Jardín
|
Website Down | 1 month ago |
 Kyiv
|
Sign in | 2 months ago |
 Chennai
|
Website Down | 3 months ago |
|
Point Pleasant Beach
|
Website Down | 3 months ago |
Full Outage Map
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Amazon Web Services Issues Reports
Latest outage, problems and issue reports in social media:
-
Ignacio Cassinelli (@igncass) reported@awscloud What a terrible response
-
Daniël (@dvtoever) reported@marcelocantos @awscloud Totally agree. I my took hours for the stress to leave my body. I tought i was hacked and my services were abused. They didnt bother to take down the billing page temporarily with a warning or sent a follow up mail pointing out this bug.I am going to close down my account as well
-
metis (@metis00001) reportedI can't understand why AWS has not been able to resolve my issue of payment method. Whatever credit card I put, they are not able to verify it and they keep asking me to call the card issuer. It's not card issuer issue! @awscloud
-
Param (@Param_eth) reportedThe downfall of Storj Labs (bankruptcy): - launches Storj in 2014 to build a decentralised alternative to cloud storage - promises a blockchain based competitor to Amazon S3. - attracts thousands of node operators across the world - raises around $35 million in funding - secures roughly $30 million through its 2017 token sale - spends years building its decentralised storage network - the DePIN business model proves difficult to scale profitably 2021: - $STORJ reaches its all time high 2022–2025: - the token enters a prolonged decline - node operators report declining rewards and operational issues - Storj begins selling non-core assets and right sizing operations October 2025: - Inveniam Capital Partners acquires Storj Labs - the acquisition is expected to strengthen the company's future - financial pressures remain unresolved July 2026: - Storj Labs files for Chapter 11 bankruptcy protection - the company says legacy liabilities can no longer be outgrown - assets and liabilities are estimated between $1 million and $10 million > operations > customer services > the storage network continue running - Inveniam backs the restructuring process - Storj proposes a plan that could give STORJ token holders equity in the reorganised company - $STORJ falls another 14–15% after the bankruptcy announcement - the token is down roughly 99% from its 2021 all time high
-
Armando J. Perez-Carreno (@perezcarreno) reported@ngriffin_uk @awscloud The problem wasn’t only the billing page. Many people received billing usage alerts with tremendous spend. In our case, it was additionally frustrating because we couldn’t log in due to an MFA bug while we were about to board a ten hour flight. Some of us do care.
-
Ondřej Flídr (@snipercze) reportedHello @AWSSupport, is there any problem with EBS subsystem in us-east-2 (Ohio region)? Cannot resize volume (ending with internal error, same for console and CloudFormation), new volume is created but stuck in "Attaching" to the EC2. Thanks for check
-
ErinE (@WhoaNowNelly) reported@DRiceHockey @WNBA @awscloud Same applies to all their stats. Their PRA is gonna go down too. That's the nature of injuries. Makes it harder for the individual, but does not increase the difficulty of the actual shot itself.
-
Omni (@omnishredder_) reported@AmazonUK @Twitch @awscloud sort yo ****, I'm getting tired of ironically the last two days unable to watch twitch without lag or buffering at random with no explanation, it's almost like the ******* AI training is the problem that nobody wanted! How about ******* remove it!
-
Onkar Deshpande (@i_am_onkar) reported@bilal_akh @awscloud what were potential issues? account compromised? keys exposed? last time this happened for me was when some keys got leaked and someone emptied my startup credits -this was 8years ago tho
-
sof ࿔˚⋆ (@sophia_ray_17) reported@awscloud until the cloud has a power outage and i can't get into my car
-
kakafa.btc (@kakafa_btc) reported@AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud
-
Ashutosh Dubey (@_virusbug_) reported@AWSSupport I’ve already emailed the AWS Receivables team but haven’t received a reply yet, it’s been 3 days now. The support engineer only advised me to contact them about this issue.
-
Yuyun Francis (@FrancisYuyun) reported@AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."
-
Harikrishna KP (@harikp2002) reported@AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!
-
The Trading Guy (@thetradingguy_) reported@AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?
-
Nil (@slowalgorithm) reported@awscloud How are you planning to compensate all your customers who panicked and started deleting resources since the email was legit and there was not a second email notifying of the issue. Your support bot itself claimed the expenses were legit.
-
Brandon James (@brandonajames) reported@callmeauntie218 Yes global outage from Amazon AWS.
-
Corey Quinn (@QuinnyPig) reportedI want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”
-
Ohm Patel (@Techieohm) reported“Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”
-
Anjishnu Ganguly (@Anjishnu46) reportedHey @AWSSupport, Our Case 178452910500907 is still not resolved, and we've been left waiting without any meaningful update. Because of this, we're also unable to apply for AWS Activate, which is directly impacting our business operations and slowing down our workflow. This delay is becoming unacceptable. Please look into this urgently and help resolve it as soon as possible.
-
devastatindave.eth (@NftCelestials) reported@awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually
-
Payal (@payal_codes) reportedDay 1 : "How to Scale an App to 10 Million Users on AWS" If I have to design a system for 10 million users, I won't build everything on Day 1 because it will add unnecessary complexity and cost. I'll start simple with one application server and one database. As traffic grows, if the server starts reaching its CPU, memory, or storage limits, I'll first scale vertically by moving to a bigger instance. Once that is not enough, I'll separate the backend and database so both can scale independently. To avoid a single point of failure, I'll deploy the application across multiple Availability Zones and put a Load Balancer in front so if one server or AZ goes down, traffic is automatically routed to healthy servers. As the number of users keeps increasing, I'll make my application stateless by storing sessions in Redis. This allows me to add multiple application servers behind the Load Balancer and scale horizontally. If my database starts getting overloaded with reads, I'll use Redis to cache frequently accessed data and add read replicas to distribute read traffic. For static assets like images, CSS, and JavaScript, I'll store them in Amazon S3 and serve them through CloudFront so requests don't keep hitting my application servers. If traffic suddenly spikes during sales or events, I'll enable Auto Scaling with CloudWatch metrics so AWS automatically adds or removes servers based on demand. As the application becomes larger, I'll split the monolith into microservices. This allows each service, like authentication, payments, or notifications, to scale independently instead of scaling the entire application. If the database becomes the bottleneck, especially for write operations, I'll use sharding or federation depending on the data and business requirements. Finally, when users are spread across the world, I'll deploy the application in multiple AWS Regions to reduce latency and improve availability. My approach is always the same: find the bottleneck, solve that bottleneck, and only introduce more complexity when the current architecture can no longer handle the traffic.
-
Anjishnu Ganguly (@Anjishnu46) reportedI posted again that day because the same issue was blocking our AWS Activate application too. @AWSSupport said it had been passed along again. Another public reply, same unusable account.
-
Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported@jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)
-
Gabriel (@doktorgphd) reported@awscloud wow really??? i had to search x for the reason?? not even an email?? I saw the email sent yesterday about the cost alert and I spend the last hour trying to work out what is going on because it looks very legit and I only find out it was an error on x! Just had to send an email!!
-
Maurizio Santamicone (@santamm) reported@awscloud And while you fix it, you can credit us for those amounts.
-
krrawn (@krrawn) reportedI was wondering why @awscloud support was slow the other day
-
Aramis Official (@AramisToken) reported@NoaSanderskyo7 @F1 @awscloud He was slow af, actually
-
Piragash Velummylum (@piragash) reportedAt @awscloud we call this undifferentiated heavy lifting. @Cometml Opik does the hard work, so you can focus on the customer problems.
-
J Bret Edwards (@jbecompslns) reporteddid @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.