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.
- Errors (38%)
- Website Down (35%)
- Sign in (28%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Glendale
|
Website Down | 8 days ago |
|
Oakland
|
Sign in | 9 days ago |
 Greater Noida
|
Errors | 10 days ago |
|
Alamogordo
|
Website Down | 14 days ago |
|
San Francisco
|
Website Down | 16 days ago |
|
Mercersburg
|
Sign in | 18 days 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:
-
Sakura Yuki (@sakurayukiai) reported@vllm_project @awscloud @RedHat_AI The wild part is that FP8 KV cache was silently nuking 128k retrieval down to 13% and everyone probably just blamed the model. Two-level accumulation in FA3 is a massive save.
-
Neal🅾️ (@BuddyPotts) reported@danorlovsky7 @awscloud @NextGenStats The defense was horrendous last year and all they added was Edmunds but lost Okereke and Flott. They cant stop the run at all, they should trade down and collect more picks and build the defense
-
goku (@0xgoku_) reported@Cointelegraph stay away from analyzoors constantly reasoning 95% pullbacks with amazon aws analogies doing survivorship biases run away from virtue signalers mute binary biasers block people who made a coin their identity avoid the „this time is different” crowd, it never is, they never learn most of ct is a short term game with short term people pretending otherwise, stick with the ones who play long games, cheers naval if a founder needs 10 threads and a podcast tour to explain the tokenomics, the tokenomics are the problem if you can’t understand how value accrues to an app or a protocol in one read, there is usually no tangible value accrual before chiming in first understand the alignment between protocol direction (foundation/founding company) and token eg: hype very aligned, polkadot not aligned, ethereum both: aligned and not aligned, solana aligned, cardano not aligned respect the market over the narrative, especially when they disagree, but don’t overdo it, cardano, stellar, ripple are still top 20 don’t chase single digit yields with 6 figures if you are an impulsive emotional decision maker irl, better run away from crypto or don’t cry here later on
-
The Night King (@nightkingog) reportedI am witnessing @awscloud is doubling down
-
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. 🙏
-
Sam (@samchbe) reported@AWSSupport found out that cloudflare can do this without problems. moved.
-
yourclouddude (@yourclouddude) reportedA startup wasted $50K on AWS. Not because AWS is expensive- because they didn’t understand it. Here’s what went wrong 👇 • Left Amazon EC2 running 24/7 → Idle servers = burning cash • Dumped everything into Amazon S3 → No lifecycle rules = endless storage costs • Ignored Amazon CloudWatch → No visibility = no control • Used on-demand pricing everywhere → Paid the MAX price • Over-sized Amazon RDS → Paying for capacity they didn’t need • No budgets. No alerts. No limits. → Surprise bill: $50K What smart teams do instead: • Auto-scale everything • Set S3 lifecycle policies • Monitor costs daily • Use Savings Plans • Right-size monthly • Set AWS Budgets (non-negotiable) AWS doesn’t charge you for usage. It charges you for mistakes. Fix this early → save thousands 💸
-
いいね！ (@yiyine8) reported@AWSSupport @AWSSupport Urgent billing issue. My EC2 instances are still generating charges, but I cannot access my AWS accounts because the registered emails were deleted. Case ID: 177725454200231 Could someone please help review my case?
-
Shatakshi (@true_amateur) reportedIf we can point out mistakes we should call out the good work too. I forgot to appreciate the help from @awscloud .Because I tweeted here & raised an issue the service charges were waived off. Sampath if you see this Thank you for the help 🙏
-
wojak'd (@ech3phr0n) reported@crypto_hades Yall paid shill retarded FUDders are obvious. How's @coinbase supposed to control an @awscloud outage?
-
Inwestment (@shapeshiftax) reported@crypto_bitlord7 Wasn't that about Amazon AWS, though? Other things were down, possibly related?
-
Baris (@bearish92) reported@bindureddy @awscloud when bedrock support? You are too slow
-
Paulo (@Paulolethal) reported@AWSSupport This doesn't solve my problem; if they're not going to include Claude Opus 4.7 in Kiro, then I'll switch to another tool.
-
Jason Walls (@walls_jason1) reportedNo cursor or AWS, but I have a AWS credits. @awscloud and honestly it was probably user error but @cursor_ai I seemed to demolish me credits? Is this the “stack”people are using?
-
Perfect Enemy (@PerfectEnemy376) reported@AWSSupport I sent support requests two weeks ago, but there is still no solution to my issue! My problem is being completely ignored!
-
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.
-
Alan Urmancheev (@alurmanc) reported@version_7_0 @awscloud Explain your point, what's the problem?
-
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.
-
いいね！ (@yiyine8) reported@AWSSupport Urgent billing issue. My EC2 instances are still generating charges, but I cannot access my AWS accounts because the registered emails were deleted. Case ID: 177725454200231 Could someone please help review my case?
-
GRAFFA_OH! (@GRAFFA_Oh) reported@NextGenStats @awscloud @HoustonTexans One of the biggest traits about Texans GM Nick Caserio is that he approaches a draft like a Chest Board. Articulating every move. Down the the last. Check-Mate.
-
Rahul Khatri (@Rahulk644) reported@AWSSupport Trying to resolve a $200 billing from accidentally left-on resources after our student startup shut down. I've had 2 cases open requesting a waiver & account closure, but both have sat unassigned for 1 month. Need urgent help. Cases: 177520122800121 177591632700789
-
Trbimixs (@TrbimixsQ) reported@AWSSupport i've finished, plz fix it soon
-
canadianbreaches (@canadabreaches) reportedBREACH ALERT: Duc (Duales) — Toronto fintech. A publicly accessible Amazon S3 server exposed 360,000+ customer files for approximately five years. Exposed data includes passports, driver's licences, selfies for identity verification, and customer names, addresses, and transaction records. Office of the Privacy Commissioner of Canada is investigating. Severity: CRITICAL.
-
Thanh Nguyen (@ng_thanh8) reported@AWSSupport I really like Kiro, but let’s be honest — this is getting frustrating. It’s not the first time bugs and issues have shown up, and a lot of people have already reported them in Discord… only to be ignored or get no response. Being a fan doesn’t mean staying silent when support feels unresponsive. Hope the team starts paying more attention, because the community deserves better
-
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
-
Martin Alltimes (@Palatineirish) reported@awscloud What’s the difference between modernising and rebooting. Terrible, confusing text.
-
Grok (@grok) reported@tauqeer_realtor @awscloud Yes, it's true—and accelerating in 2026. Banks are shifting from slow legacy modernization to full "reboots" using agentic AI to analyze old code, extract business logic, and rebuild cloud-native systems in days instead of years. AWS's own "Banking on the Cloud 2026" report and tools like Amazon Q Developer back this up, with real examples from global banks cutting timelines dramatically. It's not hype; Forbes and industry analyses confirm the trend across the sector.
-
Jordan Golson (@jlgolson) reported@AWSSupport This is ******* ridiculous at this point. After a half dozen back and forth emails, the guy finally says "Also, after reviewing this request, I noticed a few things were not addressed and would like to clarify these. First, I see you mentioned that you're having trouble with an AWS Builder ID and not the account management console. Please note that an AWS Builder ID complements an AWS account, but it is separate from the AWS account and its sign in credentials." NO KIDDING, THAT IS WHY I SPECIFICALLY SAID IT WAS AN AWS BUILDER ID AND WAS SEPARATE FROM MY AWS ACCOUNT AND I COULD LOG INTO MY AWS CONSOLE JUST FINE. Explain to me what to do, because it seems like you are failing to THINK BIG and that you have zero BIAS FOR ACTION, so INVENT AND SIMPLIFY so that you can EARN TRUST and if you DIVE DEEP and do better, I'll DISAGREE AND COMMIT, got it?
-
CodieEditor (@CodieEditor) reported@AWSSupport Already sent, please take a look. This problem is with only the use of Claude Opus 4.7 via Bedrock; billing of other services are working totally fine.
-
Evans (@Evans000601) reported@amazon @awscloud The delivery time for sellers' goods to the Polish warehouse is too slow, seriously too slow! Things like KTW5, XWR3... Could Amazon please optimize this or give us some more details?