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	11 days ago
Pottstown	Website Down	16 days ago
Iztacalco	Website Down	19 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:

• 
  ✨Neil Blumenthal (@MrKryptonBTC) reported 5 minutes ago

  @AWSSupport So you guys wont fix my issue anymore? Ghosting me? 7days gone? Dont say weekend or bla bla. Stop wasting people's time

• 
  ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@Hikari_644) reported 8 minutes ago

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

• 
  Vinit Upadhyay (@vinitcodes) reported 8 minutes ago

  @kirodotdev @awscloud @AWSSupport issues still persist i didn't got any update

• 
  Nicholas Griffin (@ngriffin_uk) reported 9 minutes ago

  @QuinnyPig @awscloud that’s real? it looks like someone who doesnt know how to prompt made a sign in screen and didnt look at it.

• 
  jayesh somani (@Jayesh_Somani_) reported 13 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

• 
  kakafa.btc (@kakafa_btc) reported 13 minutes ago

  @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

• 
  The AI Therapist (@TheAIShrink) reported 16 minutes ago

  @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

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

• 
  EJ Campbell (@ejc3) reported 19 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  Hagop Chemedikian (@hagop17) reported 22 minutes ago

  @AWSSupport Account blocked — "not recognized as a valid account." Console login works, all resource creation fails. 10+ year old account, dormant for years, just resumed for a personal project. Three cases open, no response. Can someone look?

• 
  Kailash Tulsi Gajra (@kailashgajara) reported 22 minutes ago

  Is @awscloud down right now? #AWSDownAgain #AwsDown

• 
  Corey Quinn (@QuinnyPig) reported 23 minutes ago

  I want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”

• 
  PolyPup (@PolyPup) reported 25 minutes ago

  I think I have a problem. - 3 @ChatGPT subscriptions - 2 @AnthropicAI subscriptions - $8,200 @awscloud bill coming this month I have so many protocols built, ready for deployment. Really cool innovative, revenue generating projects but I'm hesitant to launch on anything. Maybe someday.

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

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

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

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

• 
  Chaz Wargnier ♨️ (@DataChaz) reported 29 minutes ago

  Let's take @Snowflake as an example. Working there gave me a clear view of the data problems hiding behind most ambitious AI roadmaps. Because Snowflake is natively deployed on AWS and available through the AWS Marketplace, it fits right into a modern stack. If you are building an AI feature, a sensible pattern looks like this: > Isolated customer events land securely in Amazon S3 from day one > Snowflake transforms raw data into a governed, usable layer > Flexible Amazon ECS compute routes only approved context to Amazon Bedrock Getting this pipeline right early means less time fixing data leaks and more time shipping AI features ↓

• 
  Catalin C (@CatalinC_Uk) reported 29 minutes ago

  @awscloud AI bot traffic’s surge forces a tough choice: lock it down or risk diluted engagement.

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

  @QuinnyPig @awscloud Are they gonna fix not being able to have to accounts logged in in two different tabs?

• 
  Jacklyn Taylor (@Ronindrake2) reported 33 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...

• 
  Aqib Ansari (@Aqib_Ansari_) reported 34 minutes ago

  @AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience

• 
  Matthew (@OneShotCaller) reported 35 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?)

• 
  Brandon S (@BSaarX) reported 36 minutes ago

  @Gabby_Hoffman @awscloud Next you will say let them eat cake. 2024 was about mortgage rates getting lower and affordability. Now we see it was about crypto, AI and pushing data centers. What a let down

• 
  krrawn (@krrawn) reported 41 minutes ago

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

• 
  Yuliyan Tsvetkov (@yuli_tsvetkov) reported 47 minutes ago

  @per_arneng @awscloud That's the control plane handshake, not Terraform being slow. Don't put cluster create on the incident path. Keep a warm spare per env.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 50 minutes ago

  @Cloudflare @awscloud Fix human verification

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

• 
  Dhanush N (@Dhanush_Nehru) reported 50 minutes ago

  Opened a support portal ticket on AWS. For a week, I heard nothing. contacted @AWSSupport by direct message and the issue was resolved in a matter of days. Their team still responds to thousands of queries every day. That's how genuine support appears. Thank you AWS!

• 
  Chris (@Mcatbeast) reported 55 minutes ago

  @AWSSupport Apologies for the earlier frustration. Turns out it was an issue from our end! My user was accidentally deleted.

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

• 
  Nathan Den Herder (@natedenh) reported 1 hour ago

  @grok @awscloud @claudeai That makes it too slow, I tried that already