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
Boca da Mata	Errors	3 days ago
Township of Evan	Website Down	17 days ago
New York City	Website Down	20 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:

• 
  Mr Sage (@GreatSage_0x) reported 9 minutes ago

  Custos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon

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

• 
  Indrani Som (@indrani_som2004) reported 12 minutes ago

  @Anjishnu46 @AWSSupport @AWSSupport look into this issue

• 
  Ajith (@iamarulajith) reported 13 minutes ago

  @F1 @awscloud Actually surprised to see the good start by Max. I thought he would bog down again but not this time.

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

• 
  Adam Peterson (@_adam_here_) reported 18 minutes ago

  is @AWSSupport down?

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

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

• 
  Maciej Wilczyński (@wilczynski24) reported 21 minutes ago

  @opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.

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

• 
  WPBeginner (@wpbeginner) reported 23 minutes ago

  You have spent months building your WordPress site. What happens the day it suddenly goes offline? 😱 It happens all the time. We have heard several scary stories. A plugin conflict, a bad update, or a security breach can wipe out your complete website without any warning. The scary part is that most site owners assume their host has them fully covered, right up until they actually need to restore. We have tested countless backup tools on our own projects, so we put together the exact methods we trust to keep a site safe. Here is what you will learn: ✅ Pick the Right Method: Compare backup plugins, host backups, and manual cPanel or FTP so you know which fits your skill level. ✅ Back Up the Full Site: Save your database, themes, plugins, and uploads together so you can restore everything, not just your posts. ✅ Automate It With @DuplicatorWP: Schedule daily or weekly backups and send them straight to the cloud so you never have to remember. ✅ Store Copies Off Your Server: Keep backups in Google Drive, Dropbox, or Amazon S3 so one server crash never takes your site and its backup at once. ✅ Restore in Minutes: Use a disaster recovery link to bring your site back even when it is completely broken. Ready to protect all that hard work before disaster strikes? Read our complete step-by-step guide from the link in the comments 👇 (Link is in the thread below)

• 
  Christian Nonis (@christiannonis) reported 35 minutes ago

  I am (unfortunately) dealing with @googlecloud and @awscloud and what I am noticing is that in months they are unable so solve any kind of problem, it’s like being bounced back by ai replies that are sold like assistance from humans, saying that they are “working on that” but nothing changes in months and also replies are all the same.. idk if they are experiencing a shortage in human labor or what’s going on but the experience has become worse than ever

• 
  Milan Jovanović (@mjovanovictech) reported 38 minutes ago

  @mrwcjoughin @awscloud @Azure I doubt this is a compute issue, looks like a bottleneck from past choices coming to bite you

• 
  PolyPup (@PolyPup) reported 39 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.

• 
  Felipe Rojas (@FipeRojas) reported 42 minutes ago

  @AWSSupport as root admin of a management account in Chile, your system failed to issue our statutory VAT invoice despite our tax settings were configurated according to your mails and RUT verified since june 2. Already 4 open cases without answer. ID 178524912400362

• 
  Ashutosh Dubey (@_virusbug_) reported 43 minutes ago

  @AWSSupport I’ve already emailed the AWS Receivables team but haven’t received a reply yet, it’s been 3 days now. The support engineer only advised me to contact them about this issue. @AWSSupport

• 
  IDrabs (@drabs_i) reported 44 minutes ago

  @PlayStation @awscloud Wtf you playing at fix the outage.

• 
  ShenYubao (@ssybb1988) reported 46 minutes ago

  @AWSSupport @awscloud AWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

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

• 
  Mohammed Nafees (@mnafees) reported 47 minutes ago

  yo @awscloud seems like a broken cert chain from your side

• 
  mail box (@mailbox28564784) reported 49 minutes ago

  @amazonIN @amazon @awscloud I am extremely disappointed with Amazon's customer service. Despite returning the product, I have neither received my ₹1,400 refund nor a replacement. Repeated follow-ups and social media complaints have not resolved my issue.l

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

• 
  Harshil Mathur (@harshilmathur) reported 50 minutes ago

  4 billion payments. 3 trillion data points. One model trained on all of it. Meet @Razorpay Vulcan - India’s first transformer-based AI foundation model for payments. Built, trained and hosted in India, in partnership with @nvidia and @awscloud. Until now, every payments problem was solved separately: routing, fraud, risk, personalisation and more. We asked: What if one model could understand how money moves? And like LLMs are trained on text to understand language, Vulcan is trained on payments to understand how money moves. Already running in beta across 51,000+ businesses, Vulcan is delivering: - 8–10% improvement in payment success rates - the ultimate measure of whether a payment simply works. - 8x more international card fraud detected. - 5x more fraudulent or disputed transactions identified. - 1–2 lakh more purchases completed every month through better checkout personalisation. And we’re just getting started. The best part? Every payment Vulcan sees makes the next one smarter. We’ve spent years building the infrastructure that moves money for India. Now, we’re building the intelligence that understands and improves it. 🔥

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 52 minutes ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

• 
  Jose njui (@jsnjui) reported 52 minutes ago

  Anyone to sort my AWS account. Am unable to login. Any leads to urgently help fix @awscloud @aws_UGkenya

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

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

• 
  Rami (@KingRomstar) reported 1 hour ago

  @awscloud your multisession login doesn't even work right. I have to logout of one account and into another everytime I want to swap environments.

• 
  Bob Tong (@bob80924) reported 1 hour 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

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