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 (67%)
• Errors (22%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Boca da Mata	Errors	15 hours ago
Township of Evan	Website Down	15 days ago
New York City	Website Down	18 days ago
Ciudad Jardín	Website Down	1 month ago
Kyiv	Sign in	3 months ago
Chennai	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:

• 
  The Trading Guy (@thetradingguy_) reported 4 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

• 
  Indrani Som (@indrani_som2004) reported 4 minutes ago

  @AWSSupport please look into this issue

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

  Is @awscloud down right now? #AWSDownAgain #AwsDown

• 
  Aaryan Bansal (@NotUnHackable) reported 10 minutes ago

  @awscloud that issue was happening since yesterday dude. why tf did it take so much time?

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 12 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?

• 
  zarrakh (@zarrakh) reported 12 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

• 
  TeeBeeCTO (@TeeBeeCTO) reported 13 minutes ago

  Setting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!

• 
  DeeDee Armstrong (@deedeeafton) reported 13 minutes ago

  @Gozieuk @awscloud You felt they were transparent? I got the anomaly detection email from AWS last night. Dashboard had an outrageous $$ number. Spun up devs to find out problem. And- then AWS posted a joke here on X, and still no email as a follow up to their first one. Doesn’t seem transparent

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

• 
  Ashmit Dutta (@ashmit105) reported 18 minutes ago

  @awscloud keeps charging me $60 a month. I can’t login to my account due to a deprecated email. Making support tickets goes nowhere. Anyone got advice on what to do?

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

• 
  Ritesh Roushan (@devXritesh) reported 34 minutes ago

  A good architecture starts by separating document storage, signing, identity verification, and notifications into independent services. 1. API Gateway All requests (upload, sign, download, share) pass through the API Gateway. It handles authentication, rate limiting, request validation, and routing. 2. Document Service Contracts are uploaded directly to object storage (Amazon S3/GCS/Azure Blob). Metadata such as owner, participants, document status, and version history is stored in PostgreSQL. Large files never pass through application servers. 3. Identity Verification Service Before signing, users verify their identity using email OTP, SMS OTP, OAuth, or KYC providers depending on compliance requirements. A verified identity token is issued before allowing signatures. 4. Signing Service Each signature request creates an immutable signing event. Documents are locked while applying a signature to prevent conflicts when multiple users sign simultaneously. Optimistic locking or version numbers help resolve concurrent updates. 5. Audit Log Service Every action upload, view, download, sign, reject, revoke is published to Kafka. Events are stored in an append-only audit database with timestamps, signer identity, IP address, and device information, creating a tamper-resistant audit trail. 6. Notification Service Kafka events trigger email, SMS, and push notifications asynchronously so users are notified instantly without slowing down API responses. 7. Security • Encrypt files at rest (AES-256) • TLS for data in transit • Short-lived signed URLs for downloads • RBAC for document access • Hash every signed document (SHA-256) to detect tampering • Store digital certificates securely using a KMS/HSM 8. Scalability Deploy services independently behind load balancers. Use Redis for caching document metadata and sessions. Object storage handles millions of documents, while Kafka decouples services and absorbs traffic spikes. Read replicas improve download performance, and multi-region replication ensures disaster recovery. This architecture provides secure storage, concurrent signing, legal compliance, high availability, and scales to millions of contracts worldwide.

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

• 
  Babak (@bbkhbb) reported 42 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

• 
  Brandon James (@brandonajames) reported 45 minutes ago

  @callmeauntie218 Yes global outage from Amazon AWS.

• 
  DeeDee Armstrong (@deedeeafton) reported 46 minutes ago

  @t1097s @larunachalam @awscloud Tyler, are you an AWS actual customer, or just someone who thinks real people should “chill out” when a vendor causes actual business trouble and then jokes about it?

• 
  Maurizio Santamicone (@santamm) reported 49 minutes ago

  @awscloud And while you fix it, you can credit us for those amounts.

• 
  Priyanshu (@iproductAI) reported 52 minutes ago

  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.

• 
  Jonny Castles (@jonny_castles) reported 52 minutes ago

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

• 
  Vinit Upadhyay (@vinitcodes) reported 54 minutes ago

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

• 
  Abhijit Tripathy (@AbhijitTripat13) reported 55 minutes ago

  @awscloud @awscloud still no response. You guys are so slow

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

• 
  Siddartha DevOps (@SiddarthaDevops) reported 57 minutes ago

  @AWSSupport link is not working

• 
  Amanda (@AMyrick1989) reported 57 minutes ago

  @krassenstein @Tesla Be careful. All these at the same time makes me think they are hacked, I’m fairly certain Amazon AWS was hacked that day when everything when down, given my Grok we hacked and no one ever gave explanation. I’m no expert but ya know, all these signs are pointing to this. Also, the Obamas helped produce a movie where someone hacked our satellites and alluded to it being the Middle East and all the teslas went haywire and self drive themselves to pile up on all the freeways. I wish I remembered the name however I made note of this terrifying movie given Obama clearly knows things we don’t. Just sayin, these incidents aren’t scattered. I would not be driving that ***** if I were you.

• 
  Siya (@reze_xqc) reported 59 minutes ago

  @AWSSupport @AWSSupport @awscloud Case 178653274100402, 4 days old. Got a copy-paste "noted for awareness" reply, no actual fix. Still locked out of AWS Builder ID, still can't access AWS Academy courses. This is blocking coursework. Fix it.

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

• 
  banhchung (@banhchugxanh) reported 60 minutes ago

  @POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch

• 
  Certified AI Dev (@MisterPrashant) reported 1 hour 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 their 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.

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 1 hour ago

  @AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?

• 
  Edward Donner (@edwarddonner) reported 1 hour ago

  @darkosubotica @awscloud @AWSSupport Thanks Darko. I'm keen to be involved. I'm aware there are challenges. A billing bug shouldn't cause a global outage or delete backups. I believe these are solvable. I don't want the possibility of financial ruin from a mistake or hack. Will DM.