Amazon Web Services status: access issues and outage reports

Problems in the last 24 hours

Amazon Web Services signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

• Service-wide signals
• Service-wide baseline

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	15 days ago
Pottstown	Website Down	19 days ago
Iztacalco	Website Down	23 days ago
Boca da Mata	Errors	1 month ago
Township of Evan	Website Down	2 months ago
New York City	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:

• 
  Payal (@payal_codes) reported 2 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.

• 
  masaki (@silenthill_x) reported 3 minutes ago

  @AWSSupport Could someone please take a look at my support case? I opened a case 6 days ago because my RDS Reserved Instance is showing "Payment failed", but the case is still unassigned. The automated AWS Support response confirmed that my account is in good standing, my payment method is valid, and my invoices are fully paid. It also indicated that this appears to be a reservation processing issue rather than a payment issue. I've tried both Phone and Chat but haven't been able to reach an associate. Could you please help me get this case assigned? I can provide the Case ID via DM.

• 
  Zenwatts 🇺🇸 (@BullCall101) reported 4 minutes ago

  @awscloud Not my problem. Maybe sell a yacht or two and fix it yourself.

• 
  Sumedh More (@DroidBoyJr) reported 7 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

• 
  Jacklyn Taylor (@Ronindrake2) reported 8 minutes ago

  @awscloud @AmazonHelp @amazon Yo, can any of yall explain why a review that gets flagged for "community guidelines" refuses to tell you what the issue is? Like yall's bot goes "it violates rules!" But cant tell me what part? It obviously had to note what the issue was...

• 
  Yuyun Francis (@FrancisYuyun) reported 10 minutes ago

  @AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."

• 
  krrawn (@krrawn) reported 10 minutes ago

  I was wondering why @awscloud support was slow the other day

• 
  Adam 🤗 (@AdamMolnarHF) reported 15 minutes ago

  @cgeorgiaw @AnthropicAI @awscloud ooh, I've actually been working on an autoresearch space for a different problem (math) using Kimi k3 + inference providers, I could try forking and seeing if I can reshape the structure around this with this data + build it fully in the open!

• 
  Ohm Patel (@Techieohm) reported 17 minutes ago

  “Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”

• 
  zarrakh (@zarrakh) reported 18 minutes ago

  @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws

• 
  Prateek Gupta (@p_valuee) reported 18 minutes ago

  AWS suspended my account for billing. I have zero due invoices and zero past-due invoices. Their own Amazon Q agent confirmed it in writing. P1 case 178635853400575, day 3, production still down. @AWSSupport what is the actual reason?

• 
  Chris (@Mcatbeast) reported 18 minutes ago

  @awscloud has to have the worst sign-in page EVER. Every time I try to login as an IAM user it’s a complete headache and takes 30 minutes to figure out

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

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

• 
  Graham Christensen (@grhmc) reported 21 minutes ago

  @apparentorder @QuinnyPig @awscloud I'm sure they'll fix it after they're done at the discotheque

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

  @AWSSupport No it errors server side it doesn't work.

• 
  jayesh somani (@Jayesh_Somani_) reported 34 minutes ago

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

• 
  Harikrishna KP (@harikp2002) reported 35 minutes ago

  @AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!

• 
  Gopal Goti (@gopal_goti) reported 36 minutes ago

  @AWSSupport @AWSSupport Thank you for the update, but 'high volume' cannot justify a support case sitting completely 'Unassigned' for over 4 days for a basic account verification issue. This is not a complex technical issue. it is a backend system error on the AWS verification form.

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

  @QuinnyPig @awscloud Are they gonna fix logging me out and then redirecting to the root console login? Are they gonna fix having links shareable and login to the right account? **** is such a **** show idk why I even cope

• 
  Jaimin Vaghani (@jaiminvaghani) reported 39 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.

• 
  Matthew (@OneShotCaller) reported 44 minutes ago

  @ZZiata15569 @awscloud I have billing and budget alerts set up with AWS already. Main problem with a lot of tools I’ve used is too much noise in the alerts vs AWS option. Still, I think every AWS customer gets at least 1 surprise lol… part of initiation (onboarding?)

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

  @AWSSupport , got no replies on this upon follow up message. Please look into it. Why is it so tough to resolve an issue?

• 
  PHICER (@phicerhq) reported 48 minutes ago

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

• 
  M (@mdw864) reported 49 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.

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

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

• 
  zarrakh (@zarrakh) reported 50 minutes ago

  @AWSSupport @awscloud @AWSSupport as I told before, It will be just a correspondence and no solution. I have been getting correspondence since feb 2026 but no refund, despite of your team confirmed that the issue is on your side.#aws

• 
  Jonny Castles (@jonny_castles) reported 51 minutes ago

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

• 
  Jacklyn Taylor (@Ronindrake2) reported 51 minutes ago

  @awscloud hey, got a simple question When your moderation refuses to post a review of a book, can you do everyone a favor and instead of saying "one of these things" Say "here is the specific part that violates our guidelines. Pls fix it" It would be, so much more helpful

• 
  Vera ¤⩊¤ (@VeraSimila) reported 53 minutes ago

  @awscloud L+ Ratio Fix Twitch please, nobody wants AI hype beast corpo speak

• 
  Arick Goomanovsky (@g00manoid) reported 53 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.