Amazon Web Services status: access issues and outage reports
No problems detected
If you are having issues, please submit a report below.
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 (82%)
- Sign in (9%)
- Errors (9%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Website Down | 3 days ago |
|
|
Website Down | 6 days ago |
|
|
Website Down | 1 month ago |
|
|
Sign in | 2 months ago |
|
|
Website Down | 2 months ago |
|
|
Website Down | 2 months ago |
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:
-
D (@D8118199174282) reported@AWSSupport Will the affected accounts be compensated for this issue?
-
Ajith (@iamarulajith) reported@F1 @awscloud Actually surprised to see the good start by Max. I thought he would bog down again but not this time.
-
V0LYX (@0xV0LYX) reported@awscloud clear communication like this builds trust fast the fix matters but the transparency matters more
-
Adam Peterson (@_adam_here_) reported@AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.
-
Mahadev Vyavahare (@mahadevkv) reported@SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud
-
paige s. (@PaigeSully88) reported@awscloud Your AI sucks and costs more than humans. This sure is not a human error
-
Toastie (@hightoastie) reported@marcelocantos @awscloud How would forfieting a chess tournament fix the problem though?
-
Ignacio Cassinelli (@igncass) reported@awscloud What a terrible response
-
golden gate bridge (@_ggbridge) reported@litteralyme0 this happens to me everytime Amazon AWS has an outage
-
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.
-
M (@mdw864) reported@awscloud can you PLEASE answer me? You’ve just turned off my Business because you will not help me. I need you to stop charging me. Do not tell me to login because I do not know the email address that was used to open the account. All I know is my bank account is being charged
-
Nachman Mostofsky ✡︎🇺🇸 (@Mostofsky) reported@awscloud I signed up w/ new account to get @AWS_Gov. Got usual error. Created ticket. At about 3pm. Just got my phone call. At 11:30. AT NIGHT! To then get a message while on hold that there was an error, that a tech was assigned to case & would call me back. C'mon!
-
kyun anon (Gobhi ka fool ) (@anondis1122) reported@AWSSupport @ashu_sharma17 Yeah. Why tf not send an email.. that there is an issue. I have a medical condition. It put my life in danger
-
Har (@duckboy1909) reported@awscloud fix your Alexa servers and fix your Bluetooth on app and devices! #alexadown #alexa #amazon
-
CaptainAmericaTex (@CaptAmericaTx) reported@LayoffAI During the last 12 months Amazon AWS had outages directly caused by initiatives from the AI group (with associated revenue impact). No surprise they are down sizing the snake oil sales men group.
-
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.
-
Maciej Wilczyński (@wilczynski24) reported@opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.
-
devastatindave.eth (@NftCelestials) reported@awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually
-
Indrani Som (@indrani_som2004) reported@Anjishnu46 @AWSSupport @AWSSupport look into this issue
-
Nilesh (@nile3h) reportedReached out to @awscloud team yesterday related to billing issues wrt AWS partners, no replies Can anyone help?
-
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.
-
Edward Donner (@edwarddonner) reported@BaconOverflow @awscloud I'm an experienced technologist. Yes a bug was likely. My fear was I'd made a terrible mistake or leaked credentials. AWS customers are on the hook for either. AWS has no hard caps. My initial alerts were high but not billions. For 10 mins I thought this just might be real.
-
Edward Donner (@edwarddonner) reported@darkosubotica @awscloud @AWSSupport Thanks Darko. I'm keen to be involved. I'm aware there are challenges. A billing bug shouldn't cause a global outage or delete backups. I believe these are solvable. I don't want the possibility of financial ruin from a mistake or hack. Will DM.
-
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. @AWSSupport
-
Okko Ojala @okko@mastodon.social (@okko) reported@edwarddonner @awscloud @AWSSupport Combine a bug like that and spending caps, and the services would have been taken down and caused major losses of services worldwide.
-
Anjishnu Ganguly (@Anjishnu46) reported@AWSSupport @awscloud, please don't reply again just to say this was shared internally. Assign someone who can actually look at the account, explain what's blocking it, and fix it.
-
mail box (@mailbox28564784) reported@amazonIN @amazon @awscloud But in my personal experience, this response has never led to a real solution. They keep asking for the same details again and again, yet my issue remains unresolved. My ₹1,400 refund is still pending, and I have neither received a replacement nor-2
-
𝘋𝘳. 𝙈𝙞𝙘𝙝𝙖𝙚𝙡 𝙅. 𝙋𝙚𝙩͛𝙚𝙧𝙨𝙤𝙣 (@WeatherArchive) reportedSomehow, GOES19 going down wasn’t the craziest thing to happen this week. Happy bankruptcy day to those who celebrate (I.e., have an @awscloud account)
-
Erin (@erinEncoded) reported@AWSSupport No follow up email sent to users to let us know not to panic after we got threshold emails. I was sick this morning and lost hours of productivity. Terrible, truly terrible, customer service. As soon as I see my account go back to 0, I’m moving to Azure.
-
M (@mdw864) reported@AWSSupport Tells me to login when I keep telling you I cannot login because I don’t have the capability to do so.