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 (82%)
• Sign in (9%)
• Errors (9%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Website Down	4 days ago
New York City	Website Down	7 days ago
Ciudad Jardín	Website Down	1 month ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	2 months ago
Point Pleasant Beach	Website Down	3 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:

• 
  paige s. (@PaigeSully88) reported 3 minutes ago

  @awscloud Your AI sucks and costs more than humans. This sure is not a human error

• 
  mail box (@mailbox28564784) reported 10 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

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 10 minutes ago

  @AWSSupport Again there is a mass wave of suspensions like in May, I'm assuming in error as I've been on this platform for over 10 years and this seems to be happening more frequently. Emails from mturk-noreply havent worked in a long time so any updates on this situation?

• 
  GiveHateAChance (@HelpingHate) reported 12 minutes ago

  @awscloud It's cute how the ***** indians who caused all of this are never at fault and how you dismiss what a huge error this was with an emoji.

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

  @ivanburazin Why are you still using windows server ? It’s less than 10 minutes to fire up a @awscloud ECS cluster running free Linux

• 
  paige s. (@PaigeSully88) reported 20 minutes ago

  @BenENewton @awscloud This isn’t human error. This is failed automation

• 
  Gabe Fletcher (@gabefletcher) reported 21 minutes ago

  @marcelocantos @awscloud bro... touch some ******* grass. OF COURSE IT WAS AN ERROR. WHO REALLY THINKS THEY LOOK AT THEIR AWS BILL FOR A TRILLION DOLLARS AND SAYS "OH THATS DEFINITELY REAL" stop. go **** off to some VPS's or some ****.

• 
  Certified AI Dev (@MisterPrashant) reported 22 minutes ago

  This solution to this problem is AI traffic monetization. If you are an owner of a platform that provides some valuable data, you can put the data behind a paywall for the AI traffic by charging the bot fraction of a penny for using your content. x402 Payment Required protocol tells the bot that the content requires payment and the bot settles the transaction quickly on a stable coin at which point the content becomes accessible. This way,people running their search bots does not require subscription to 10 different services and can easily access data from anywhere at a very minimal cost and the owners of the sites also win as the traffic count to their paywalled site will generate income. This is not a concept. The framework to build this is already available in @awscloud today.

• 
  AntDracula (@ant_dracula) reported 25 minutes ago

  @kankerhoerrrrrr @marcelocantos @awscloud And you had no response for "what's the alternative to shutting down services, just pay the bill?" Maybe you really are an AI bot instead of a retard.

• 
  Jaden Fix (@jadenfixxx) reported 26 minutes ago

  Anyone at @googlecloud or @awscloud (or a neocloud) wanting to slide into my DMs and help me rip some free credits? Possibly leading to larger contracts down the road .. I just tried signing up for an @Azure free trial, and the experience felt like what I imagine the elders went through with dial-up internet. Solutions Architects or Account Managers HMU

• 
  Nil (@slowalgorithm) reported 30 minutes ago

  @awscloud The LEAST you can do is to give some compensation. This mistake caused operational issues for several companies across the globe.

• 
  Zyreon (@Zyreon_trading) reported 34 minutes ago

  @awscloud When i wake up i saw:there is another AWS Bug/Service Down. Lol cannot give up time of 24 hours/7 days/infinity uptime..

• 
  Gopal Goti (@gopal_goti) reported 35 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.

• 
  Mahadev Vyavahare (@mahadevkv) reported 37 minutes ago

  @SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud

• 
  Priyanshu (@iproductAI) reported 42 minutes ago

  Here’s the cleaned-up version with fixed grammar, same hard tone, and no em dashes: I requested @awscloud to increase my Opus 4.6 V1 limit and I’ve been chatting with the AWS support team for almost 4-5 days now. They’re telling me this. Is @awscloud a government company? I mean, you guys can’t just pass the problem from one department to another. I mean, WTF? Now I have to raise my query again to sales? Why can’t you just pass this query? You already have more context about what the issue is. I can’t believe how these big MNCs are working these days. Totally absurd service from @awscloud. One more thing, please educate your support. I mean, she didn’t even know what the TPD limit is in the service quota. She literally replied the first time saying there’s only a TPM limit and no separate TPD limit.

• 
  Joy | 🔥 (@JoyKingdomx) reported 42 minutes ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

• 
  AntDracula (@ant_dracula) reported 45 minutes ago

  @BohemiaTech @awscloud Google just randomly shuts down services for no clear reason. That’s why they’re not trusted

• 
  SwarmOne.ai (@swarmoneai) reported 45 minutes ago

  OpenAI just unveiled Jalapeño - their first custom inference chip with Broadcom. "Substantially better performance per watt." Interesting. But a chip doesn't fix a misconfigured serving stack. Custom silicon with default batching, naive routing, and untuned KV-cache management is still burning money. SwarmOptimizer doesn't care what chip you run. It tunes the deployment layer - batching, caching, routing, concurrency - where most of the waste actually lives. The silicon is one layer. The optimization is another. Now on @awscloud

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

• 
  Naren Bao 包娜仁 | Physical AI Agents (@NarenBao) reported 49 minutes ago

  @awscloud please fix your Cost Explorer bug asap!

• 
  Koray Yersel (@korayyersel) reported 51 minutes ago

  @AWSSupport My balance went down to zero. Time to delete the aws account

• 
  Jack Stone (@c0XhHxvylL) reported 54 minutes ago

  @AWSSupport be honest, how much of this problem was due to ai and/or vibecoding

• 
  hansi flick enjoyer (@sambarvadaii) reported 54 minutes ago

  @santhoshv @AWSSupport @awscloud I had an s3 bucket with some data in worth 2-3 mb at max. At first I thought someone hacked into my account. I raised a billing inquiry, after which I realised that this was an ongoing issue.

• 
  Jeff B. Vockrodt (@JeffBVockrodt) reported 55 minutes ago

  @AWSSupport You should send follow up emails alerting all your customers to this issue. I woke up to a $719 million billing estimate which although absurd conjures a potential nightmare of getting it worked out

• 
  Carlos DP 🤖🇺🇸 (@carlosdponx) reported 56 minutes 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).

• 
  Adam Peterson (@_adam_here_) reported 58 minutes ago

  is @AWSSupport down?

• 
  barney (@Southclaws) reported 59 minutes ago

  @jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors

• 
  Tseng (@TsengSR) reported 59 minutes ago

  @marcelocantos @awscloud I'm 100% certain you'd also crying a river when hard caps are added and the same happens again, because then your services will be shut down immediately until they resolve it and you'll cry too, how they'd dare to take your services offline when reaching the cap due to an error.

• 
  Ben Newton ベン (@BenENewton) reported 59 minutes ago

  @awscloud Somewhere there's an IT guy lying on the ground next to his desk after opening the page with this error on it.

• 
  Jim Osman (@EdgeCGroup) reported 1 hour ago

  @awscloud Real innovation starts with people solving real problems.