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 (83%)
- Errors (17%)
Live Outage Map
The most recent Amazon Web Services outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
 Pottstown
|
Website Down | 4 days ago |
 Iztacalco
|
Website Down | 7 days ago |
 Boca da Mata
|
Errors | 19 days ago |
|
Township of Evan
|
Website Down | 1 month ago |
|
New York City
|
Website Down | 1 month ago |
|
Ciudad Jardín
|
Website Down | 2 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:
-
David Bauer (@realDavidBauer) reportedHey @BrianRoemmele two surprising things with Grok Bot I wanted to share and get your thoughts. 1) A lot of systems online use Cookie IP Validation, as you probably know. You log in, if your IP address changes, you're prompted to log in again. Grok Bot seems to use a different IP address at almost every interaction so it fails where IP validation is used. Sometimes it fails silently. I had to temporarily disable IP validation on some of my systems to work with Grok Bot. If it wasn't my systems and I hadn't seen the problem, an average user might just blame Grok Bot. Grok Bot just sat there waiting 30 minutes for connections to respond that would never have responded until I recognized it. 2) Grok Bot is hosted at Amazon AWS! Shocking. I consider that a potential reliability issue. I would've expected Grok Bot to be hosted on X servers. Screenshot:
-
🦋Kieran🦋 💻 (@sir_divs_alot) reported🚨 @AWSSupport I've been unable to create a Kiro subscription for 2+ weeks, getting error"account is not authorized to make this call." I have an active account, valid billing, and correct IAM Identity Center Organization instance setup. Case #178567212700620 escalate urgently.
-
Nathan Den Herder (@natedenh) reported@xai @awscloud grok-4.6 on Bedrock us-east-1 is unusable today. 5-token prompt, maxTokens=16: claude-sonnet-4-5 → 3.0s us.xai.grok-4.6 → 150s timeout global.xai.grok-4.6 → 150s timeout Same account, region, creds. No throttle error, no 5xx — it just hangs.
-
Stephen “The Yellow Dart” Schutt (@schuttsm) reported@QuinnyPig @awscloud I get charged $0.55 every month. Fix that
-
Ranbir Mahapatra (@ranbirnxt) reported@QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?
-
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.
-
ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@Hikari_644) reported@ishanxtwt Simply DNS server problem never take down an entire website. Except, like amazon AWS, are using domain and dynamic name resolve to working correctly between multiple servers and services.
-
jayesh somani (@Jayesh_Somani_) reportedHey @awscloud I have lost access to the email id using which i have created an aws account and when i am trying to login with the id and password its redirecting us to reset passoword and the password is going to the email id which we have lost access here how can we solve this
-
Somers (@jake__somers) reportedAWS keeps charging me 1000x what it should be for inference I try to use the new "generally available" Grok 4.6 Prompt caching doesn't work at all I spend $1.9 worth of inference testing caching I see my AWS bill is now $3400 This was an issue months ago as well. @AWSSupport
-
Drama Memes (@drama_meme) reported@cgeorgiaw @AnthropicAI @awscloud Someone tell me why this is a hard problem and you can’t just do $ diff normal.genome sick.genome ? I am guessing it’s a statistical thing, but, if it were random then how would you figure out what’s different??
-
Siddartha DevOps (@SiddarthaDevops) reported@AWSSupport link is not working
-
X anonyn (@OmrX304) reported@AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks
-
Synapse Brief (@Synapse_Brief) reported@yugacohler @awscloud @CoinbaseDev The post frames this as a new capability, but Amazon already gave agents the ability to make purchases in December 2025. The Coinbase integration is the expansion, not the invention. The real bottleneck was never payment rails. It's authentication and authorization at scale. How does an agent prove it's authorized to spend, and how do you prevent a single compromised agent from draining a wallet? Coinbase's infrastructure solves the custody and settlement problem. AWS solves the identity and access management layer. The combination is what makes this production-ready. The "AI agents will outnumber humans" framing is hype. The real driver is that agents need to pay for API calls, data feeds, and compute resources autonomously. That's a practical requirement, not a sci-fi scenario. Stripe being involved is the quiet signal here. They handle the merchant side of the equation. Agents paying for things requires both the payer and the payee infrastructure. The managed aspect matters more than the payments themselves. AWS handles the compliance, KYC, and fraud detection layers that would otherwise be a nightmare to build. That's the real value proposition.
-
mark seery (@140ismymax) reportedPeter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI #AI
-
❤️🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reportedAmazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp
-
Babak (@bbkhbb) reported@ajassy @AWSSupport what happened to customer obsession? I would like to invite you to review the interactions on AWS support case #178605390000779. There's no better way to put this, it's a sad joke. Reps don't appear to be incentivized to solve the problem nor to do the reading
-
Graham Christensen (@grhmc) reported@apparentorder @QuinnyPig @awscloud I'm sure they'll fix it after they're done at the discotheque
-
Swaroop Hegde (@SwaroopH) reportedTIL: @awscloud has been racking up ipv4 charges on an old test instance of mine even though it uses dynamic IP. Just checked that their launch wizard deployed new instances with the same issue without warning 🤷
-
Jaimin Vaghani (@jaiminvaghani) reported@AWSSupport @AWSSupport Appreciate the reply, but I've heard this exact message every day this week. At what point does a 5+ day production-down case qualify for actual escalation? Please have an escalation manager or TAM contact me directly, the Support Center loop isn't working.
-
Vinit Upadhyay (@vinitcodes) reported@AWSSupport @kirodotdev @awscloud I’ve already raised a case explaining the entire issue. Case ID: 178664512400070. Unfortunately, I still haven’t received any genuine help, which is really disappointing. I’m not the only one facing this issue-many others are experiencing the same problem. Please look into this.
-
Don KofiAdM1N 🎖️🎖️🎖️ (@DonKofiAdM1n) reported@anonymo6575 @AsakyGRN lol even a Jss2 can go all you just mentioned right now seriously you have no idea. Do you even know anything about Amazon aws javasscript c++ building a valid algorithm or a bank website that you login in with on your phone you think yahoo guys can do this ? lol your Knowledge is limited.
-
Art Vandelay (@john15489) reported@amazon @awscloud @nvidia I need an actual customer service phone number so I can actually speak to a ******* rep regarding 4 orders now. Your email help system is broken.
-
PHICER (@phicerhq) reported@awscloud Resolving issues before customers notice is valuable, but proactive agents need clear consent, confidence thresholds, escalation paths, and reversible actions. Observability should explain not only what happened, but why the agent was allowed to act.
-
lak-alak (@baricadelane) reported@IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?
-
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
-
Ricci Research (@ricci_nov) reported@nvidia @awscloud The buried detail is "Vera CPU server" — NVIDIA hand-delivering an ARM CPU to the company that built Graviton to escape CPU vendors. The GPU is the ticket; the CPU is the trojan horse into the one socket AWS thought it had reclaimed.
-
The AI Therapist (@TheAIShrink) reported@MikeLongTerm @amazon @awscloud EC2 on AMD CPUs. The cloud bill goes down, the margins go up. aws is quietly fixing its cost structure while everyone watches the models. smart
-
Weird Things (@weird747) reported@AWSSupport I submitted all the required verification documents for my suspended AWS account as requested. I was told I would receive a response within 24 hours, but it has now been more than 48 hours with no update or resolution. Please review my case and help restore access to my account as soon as possible. I can provide any additional information if required. My website server down from last 3 days no response by aws support tried contacting everywhere .
-
Sumedh More (@DroidBoyJr) reportedHey @awscloud @AWSSupport im trying Bedrock with root user and getting NOT_AUTHORISED error with 400. Tried support and the ai assistant couldn't find anything. Tried raising ticket, it asked me to upgrade support plan. Plan upgrade failing with error. Going nowhere #SOS
-
Kenton Parton (@kenton_parton) reportedAnyone here work on AgentCore Gateway Targets at @awscloud? Been testing them for our MCP/agent platform. I like that it removes the credential leakage issue during development of new MCP's/Agents. But they’re slow AF!🐢 I’m seeing ~430ms added per request above baseline, in-region, with warm caches. Is that expected?