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 (80%)
• Errors (20%)

Live Outage Map

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

City	Problem Type	Report Time
Iztacalco	Website Down	1 day ago
Boca da Mata	Errors	13 days ago
Township of Evan	Website Down	27 days ago
New York City	Website Down	1 month ago
Ciudad Jardín	Website Down	2 months ago
Kyiv	Sign in	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:

• 
  Corey Quinn (@QuinnyPig) reported 6 minutes ago

  I’m going to get a job at @awscloud, immediately fix one bug, then resign. Which bug should it be?

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 7 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

• 
  Onkar Deshpande (@i_am_onkar) reported 10 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

• 
  Ritesh Roushan (@devXritesh) reported 11 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.

• 
  MrWho (@Mrwho23) reported 12 minutes ago

  @AWSSupport I create a case for your support and till now waiting for the reply My whole system and company is waiting for your support, but you are so slow

• 
  Jaimin Vaghani (@jaiminvaghani) reported 12 minutes ago

  @AWSSupport @AWSSupport Day 6. Production down. Same templated reply on Twitter, in the case, everywhere. If a multi-day production outage doesn't qualify for real escalation, what does? Asking someone with authority to review Case 178738643800497 and respond with an actual ETA.

• 
  Jonny Castles (@jonny_castles) reported 15 minutes ago

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

• 
  Hitesh Kumar Gupta (@iHiteshAgrawal) reported 17 minutes ago

  @kunalstwt @WeMakeDevs @awscloud Tried registering but the form needs a student email ID. My college doesn't issue one, which is common in tier 2 and 3 colleges. Happy to send university marksheets or college ID instead. Otherwise the online-for-all-India part misses the students who'd benefit most.

• 
  Bob Tong (@bob80924) reported 18 minutes ago

  @Cloudflare @awscloud genuinely curious how tax/vat treatment works when your buyer is an anonymous agent wallet with no jurisdiction attached to it, feels like the accounting problem is way behind the payment rail problem right now

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

• 
  Amanda (@AMyrick1989) reported 20 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.

• 
  Eemanuel (@Chukwunons63680) reported 22 minutes ago

  @nvidia @awscloud @grok what is the CPU server for?

• 
  Somers (@jake__somers) reported 24 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

• 
  Mahadev Vyavahare (@mahadevkv) reported 28 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

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

• 
  TechThought.org (@TechThought_org) reported 36 minutes ago

  An era ends for human data annotation. @awscloud is shutting down Mechanical Turk after 21 years as LLMs take over micro-tasks, per @techradar. What happens to training baselines when synthetic data completely replaces human feedback? #AI #Automation #AIeconomy techradar .com/pro/aws-is-shutting-down-mechanical-turk-which-let-humans-beat-ai-at-certain-work-tasks

• 
  Stephen “The Yellow Dart” Schutt (@schuttsm) reported 38 minutes ago

  @QuinnyPig @awscloud I get charged $0.55 every month. Fix that

• 
  banhchung (@banhchugxanh) reported 39 minutes ago

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

• 
  Dhanush N (@Dhanush_Nehru) reported 39 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!

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

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

• 
  Don KofiAdM1N 🎖️🎖️🎖️ (@DonKofiAdM1n) reported 43 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.

• 
  Base Builder (@basedbuilder_io) reported 43 minutes ago

  What happens when agent payments go from "works on testnet" to "GA on AWS"? AgentCore Payments just shipped general availability via @awscloud and @CoinbaseDev. CDP Embedded Wallets handle the key material, x402 encodes the payment terms, and the whole thing runs as a single runtime-to-settlement flow on Base. No testnet disclaimer, no "coming soon" asterisk. The end-to-end shape: your agent detects a payable event, opens an x402 payment channel with the recipient, and settles in USDC through the embedded wallet, all without the user touching a key or approving a transaction. That's the runtime plumbing. What it unlocks is agents that can pay for services mid-execution without a human in the loop. API credits, inference time, data access, compute, whatever someone x402-wraps. The integration gotcha to watch is spending limit enforcement at the wallet layer. x402 handles the invoice generation and the payment terms, but the CDP embedded wallet's permissioning lives one layer up. If your agent holds a wallet with a default spend cap and then processes a batch of x402 invoices in sequence, the cumulative settlement can blow past the limit before the wallet context re-checks. The outcome is partial payment batches where some invoices clear and others bounce, and your error handling needs to know which ones landed. The dependent abstraction this pushes into focus is agent-to-rail routing: your agent picks a payment path based on cost, speed, and counterparty, not just a static USDC address. That's the next layer to wire.

• 
  Swaroop Hegde (@SwaroopH) reported 44 minutes ago

  TIL: @awscloud has been racking up ipv4 charges on an old test instance of mine even though it uses dynamic IP. Just checked that their launch wizard deployed new instances with the same issue without warning 🤷

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

• 
  Chris (@Mcatbeast) reported 47 minutes ago

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

• 
  EJ Campbell (@ejc3) reported 48 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.

• 
  Aqib Ansari (@Aqib_Ansari_) reported 52 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

• 
  Ranbir Mahapatra (@ranbirnxt) reported 53 minutes ago

  @QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?

• 
  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?

• 
  ✨Neil Blumenthal (@MrKryptonBTC) reported 1 hour 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