Amazon Web Services status: access issues and outage reports
Some problems detected
Users are reporting problems related to: website down, errors and sign in.
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.
May 21: Problems at Amazon Web Services
Amazon Web Services is having issues since 02:40 AM EST. Are you also affected? 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 (40%)
- Errors (35%)
- Sign in (25%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Website Down | 27 minutes ago |
|
|
Website Down | 6 days ago |
|
|
Website Down | 9 days ago |
|
|
Website Down | 20 days ago |
|
|
Sign in | 21 days ago |
|
|
Errors | 22 days 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:
-
TechBrosTechBro (@WE2SeriousConvo) reported@JeffBezos We need to give everyone in the world 1VCPU for free for life from amazon aws. That will solve all world problems. People can rent them out or host their websites and or business ideas. Call me Jef..
-
aem (@aemukit) reportedI guess @awscloud is down and that's why everything is down.
-
Maynor Henríquez (@maynor_8795) reported@AWSSupport @AWSSupport Day 4 of complete silence on Case 177754503800193. My account is STILL locked, and we are literally bleeding money. Critical infrastructure for international logistics and clinical dental systems are entirely DOWN. Your "internal review" is destroying a real business.
-
Eochu Ollathair (@TheDagda___) reported@awscloud Who do you want to be able to blame yourself or them? That is the decision. If you aren't confident in yourself, use them, but at the same time, maybe you are letting your customers down by not using the tools you have.
-
عبدالله (@oSkyUpo) reported@awscloud Middle East FC 26 Pro Clubs players are being routed to EU servers instead of Bahrain/UAE servers, causing high ping and delay. The issue is widespread across Gulf players. Please investigate.
-
chen (@chen10075495) reported@awscloud Amazon AI Pricing Is Killing the Buy Box Losing Buy Box because AI compares my product to cheaper, non-equivalent listings — even external ones. To compete = sell at a loss. This punishes real brands. Fix this. #AmazonSeller
-
Justin (@Justin__Co) reported@AWSSupport I've been trying since May 9th to get my SMTP for SES in production and I'm still in sandbox. I verified everything from the start. I submitted follow ups 33 hours ago that have still gone unanswered. I require email verification for my site, so I'm effectively down until you get this running. Please respond!
-
Hailo Berto, yê Elî (@hailo_berto_9) reported@AWSSupport I did add a new credit card, but I cannot do payment! this is the issue!! this is not very helpful!
-
عبدالله (@oSkyUpo) reported@awscloud @EASFCDirect Middle East FC 26 Pro Clubs players are being routed to EU servers instead of Bahrain/UAE servers, causing high ping and delay. The issue is widespread across Gulf players. Please investigate.
-
Woods (@RyanRael16) reported@Midnight_Captl The irony is genuinely remarkable. Every hyperscaler on earth confirms they cannot build infrastructure fast enough. Azure supply constrained at 40% growth. Meta raising capex to $145B. Amazon AWS growing 28% with no signs of slowdown. Google Cloud up 63%. All four saying they need more chips faster than anyone can deliver them. And Nvidia is down 4%. The only rational explanation is the market is pricing in custom silicon risk. If Microsoft, Meta, and Google are all building their own chips to supplement GPU supply the fear is Nvidia's pricing power erodes over time even as demand grows. That is a legitimate long term concern dressed up as a short term sell. But in the near term supply constrained hyperscalers raising capex is the single most bullish data point for Nvidia that exists. The market will figure that out. It usually does. Just not on the same day.
-
Goksal (@goksaladiguzel) reported@awscloud If banks, especially those relying on COBOL-based legacy systems, replace them with modern software, they would most likely require 20–30 times more computing capacity than their current server infrastructure, and in general they still wouldn’t reach COBOL’s level of performance. And also, every time we go to an ATM to withdraw money, we will most likely see a “null point exception.”
-
Trevor Skinner (@PrometheusAIsec) reportedI’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.
-
InnoCommerce (@InnoCommerce) reported@AWSSupport It's been almost 2 weeks and nobody is helping me while i have some serious problems with my AWS account. That's unbelievable
-
Winston (@winstonalien) reportedHey @AWSSupport, case #177739024400953 open for 2 days, AISPL account blocking all Bedrock access, Founders Program member. Daniel escalated but still no fix. Can someone help?
-
Henrique Lima (@HenriqueLi88059) reported@AWSSupport @AWSSupport with all due respect, we are blocked with no plausible justification. AWS suspended our account without warning, without explanation, and our Medical Imaging platform has been down for 36+ hours due to AWS's actions. We submitted every document requested. We opened
-
AI..AND METAVERCE.. (@bad_sin90451) reported@AWSSupport @imTkorde I do not trust you. What exactly is your “special unit”? Is it some kind of global intelligence agency? Why are the server company and Amazon not kept separate? You want my case number? Go ask Jeff Bezos and Andy Jassy. Ask your special unit as well.
-
Andrew Sam (@egy_pl_eagle) reported@WhoisNuel @awscloud that's scary cause banking are known to be stable and bug free ... also with AI we will still have a maintainability issue
-
None (@BourDeniz) reported@AWSSupport @AWSSupport We are a research center at McGill University. Our infrastructure has been down for 5 days and case 177833537500006 still hasn't been assigned to an agent. We may be small users, but researchers are waiting on this. All security remediation is complete please escalate
-
Rafael Nascimento (@rafaelever) reported@AWSSupport I'm a Brazilian customer locked out of my account due to a lost MFA device. Cases: 177385435200586 & 177738241200052. Free tier expiring — I can't shut down my server and will be charged unfairly.
-
XALE (@InvincibleXALE) reported@AWSSupport Hi again, Its been over 2 days now, and over 30+ customers are affected of ours and its been critical And our account is still the same Feeling kind of hopeless on this.. I need this issue resolved ASAP, PLEASE Before the week starts or this issue can force us to lose clients
-
Maroun Mourani (@MarounMourani) reported@AWSSupport account 608789101967 has 2 unassigned cases - one is 29 days old (cannot terminate EC2 instance - mec1-az2). The AZ outage prevent me from terminating an impaired instance and AWS keeps charging me. Can someone please look at this ?
-
Tejas Korde (@imTkorde) reported@AWSSupport hello AWS despite asking for multiple times to connect with the customer care executive I'm just getting we are working on it and I have to solve the issue today only please connect with the team it's highest priority task !
-
wojak'd (@ech3phr0n) reported@crypto_hades Yall paid shill retarded FUDders are obvious. How's @coinbase supposed to control an @awscloud outage?
-
Alex Joshua (@JoshuaAlex91434) reported@awscloud This integration could really streamline how we identify issues in workflows. Less time on data means more time for action.
-
Henrique Lima (@HenriqueLi88059) reported@AWSSupport @awscloud Update: our account has been reactivated! ✅ After 36+ hours down, our Medical Imaging platform is back online. Thank you to @AWSSupport and the verification team for resolving this. We hope no other healthcare platform has to go through this. 🙏
-
Tofu (@tofujson) reported@AWSSupport No, it's a problem you need to solve, you know there is, you've already received feedback and reports.
-
Forengi, The Grand Nagus zek (@Elvismen) reported@AWSSupport Very concerning: AWS won’t let me pay an outstanding balance due to a billing issue. My account is closed, I’ve updated my card, opened a case, and still no human response. This is urgent and unacceptable. @AWSSupport please assist immediately.
-
NUEVE (@Nader7x) reported@AWSSupport trying to sign in to my account and do the root verification using the mail and then the sms or call I don't receive any
-
Ankur Agrahari (@agrahariankur21) reported@AWSSupport Yes it's really really frustrating as my 15+ clients website applications and all the mobile apps are not working since 12 hours and 500+ employees salaries were not disbursed due to this issue, but no instant help from your service team. Case Id sent privately.
-
Vinit Taneja (@vinit_taneja) reported@amazonIN @awscloud @JioHotstar I got the tech help from a group of movie buffs. The problem originated because of a glitch at your end. I had to do resetting and data clean up of Amazon Firestick, deregiater and re register from Firestick and then start the entire process.