Amazon Web Services status: access issues and outage reports

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.

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

• Website Down (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

The most recent Amazon Web Services outage reports came from the following cities:

City	Problem Type	Report Time
Township of Evan	Sign in	2 days ago
Pottstown	Website Down	7 days ago
Iztacalco	Website Down	10 days ago
Boca da Mata	Errors	22 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	1 month 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:

• 
  Jonny Castles (@jonny_castles) reported 5 minutes ago

  Not seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud

• 
  The Trading Guy (@thetradingguy_) reported 5 minutes ago

  @AWSSupport I need resolution on this asap as I am having problem deploying my services. I am using alternative services which are costing a lot. So please resolve this and verify my account for cloudfront Case ID: 178582104300071

• 
  Don KofiAdM1N 🎖️🎖️🎖️ (@DonKofiAdM1n) reported 6 minutes ago

  @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.

• 
  Ivan Toma (@FounderRAVERK) reported 9 minutes ago

  @awscloud @Google @Microsoft The water problem is only going to get bigger. We already have technology that can help data centers produce their own cooling water from the sea. Let’s solve this together.

• 
  Keith (@happy_keith) reported 10 minutes ago

  @amazon @awscloud @AmazonUK What does it take to get you to respond to a serious problem DO NOT tell me to go to customers services AI as it is incapable of responding to the issue This is a complete farce !!!!!!

• 
  mail box (@mailbox28564784) reported 13 minutes ago

  @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

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 15 minutes ago

  @AWSSupport There is no way to get a call back I have tried many different ways. And it always show's this issue

• 
  Arian van Putten (@ProgrammerDude) reported 15 minutes ago

  @QuinnyPig @awscloud Not randomly redirecting to root console login page if I logged in with IAM identity center

• 
  Jaimin Vaghani (@jaiminvaghani) reported 16 minutes ago

  @AWSSupport 5+ days, Case 178738643800497. Production down, customers impacted. Same scripted answer daily: no ETA, no updates, just "check back in a couple of hours." This needs real escalation. Please have someone with authority look at this.

• 
  Rohit Dhawan (@rohitdhawan26) reported 16 minutes ago

  @AWSSupport @awscloud I send a DM on 17th july with same issue but no one responded to that.

• 
  Babak (@bbkhbb) reported 20 minutes ago

  @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

• 
  Synapse Brief (@Synapse_Brief) reported 21 minutes ago

  @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.

• 
  Payal (@payal_codes) reported 21 minutes ago

  Day 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.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 21 minutes ago

  @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.

• 
  Maciej Wilczyński (@wilczynski24) reported 22 minutes ago

  @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.

• 
  𝙵𝚊𝚒𝚣𝚎𝚕 𝙿𝚊𝚝𝚎𝚕 ⚡️ (@FaizelPatel143) reported 23 minutes ago

  “AI will solve real problems, for the continent.” #AWSSummit2026 @awscloud

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 23 minutes ago

  @AWSSupport now at 3:13 and counting with production server down

• 
  David Bauer (@realDavidBauer) reported 26 minutes ago

  Hey @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:

• 
  Alvaro Villalba (@alvarovillalbap) reported 29 minutes ago

  @philipkung @awscloud @amazon Technical support has being helpful historically for me (with smaller problems than yours) But it did cost us a lot of $$$ for something I feel should be included Did they charge for your technical support?

• 
  John Darin Holloway (@bofkentucky) reported 44 minutes ago

  @QuinnyPig @awscloud Hopefully better than the "new" broken elastic beanstalk console experience.

• 
  M (@mdw864) reported 46 minutes ago

  @googlecloud @GoogleCloudTech do you accommodate customers with disabilities? In case we have problems and need to speak to you? I think I may have to switch to you because @awscloud has not provided accommodations for people with disabilities.

• 
  Onkar Deshpande (@i_am_onkar) reported 48 minutes ago

  @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

• 
  Arick Goomanovsky (@g00manoid) reported 50 minutes ago

  @awscloud It's worse than technical debt in one way - sprawl compounds through the connections, not just the count. Ten agents with no shared context or ownership isn't ten problems, it's every pair of them. The fix is a connective layer that makes them a network instead of scattered debt.

• 
  Somers (@jake__somers) reported 52 minutes ago

  AWS 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

• 
  Milan Jovanović (@mjovanovictech) reported 54 minutes ago

  @mrwcjoughin @awscloud @Azure I doubt this is a compute issue, looks like a bottleneck from past choices coming to bite you

• 
  X anonyn (@OmrX304) reported 57 minutes ago

  @AWSSupport @RahulMatta1994 @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!

• 
  Sumedh More (@DroidBoyJr) reported 58 minutes ago

  Hey @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

• 
  Ricci Research (@ricci_nov) reported 60 minutes ago

  @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.

• 
  Carlos DP 🤖🇺🇸 (@carlosdponx) reported 1 hour ago

  @MarwaEldiwiny They’re not hiding it’s a G1, it’s obviously a G1 and they don’t lie if asked. I don’t advertise explicitly my robots are built on G1 either, because it’s a distraction when marketing like this. The end user doesn’t care. It’s like if you sold a SaaS product and mentioned the servers run on Amazon AWS, it’s irrelevant to the user. Their tweets are marketing posts, not technical reports. Also idk what you mean by the G1 “having a lot of issues”. It’s the most reliable and mature humanoid platform you can actually buy today (and we have no data on reliability of closed platforms).

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 1 hour ago

  @meaningoflights @jpschroeder @awscloud what issue do you have with that?