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	28 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:

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

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

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

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

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

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

• 
  Jaimin Vaghani (@jaiminvaghani) reported 11 minutes ago

  @AWSSupport @AWSSupport Day 7.Production still down, Case still unresolved. Yesterday you said it was "forwarded internally for review" that's the third different phrasing for the same non-answer. I'm not asking for updates anymore. I'm asking: who owns this case, and when will it be fixed?

• 
  Priyanshu (@iproductAI) reported 12 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.

• 
  Mohammed Nafees (@mnafees) reported 12 minutes ago

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

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

• 
  Swaroop Hegde (@SwaroopH) reported 15 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 🤷

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

• 
  Harun R. (@harundotdev) reported 22 minutes ago

  2. The obvious fix: split responsibility. Metadata stays in a database like Postgres. The actual file goes to object storage, Amazon S3 being the standard example. Better. Still not the full fix.

• 
  ErinE (@WhoaNowNelly) reported 35 minutes ago

  @DRiceHockey @WNBA @awscloud Same applies to all their stats. Their PRA is gonna go down too. That's the nature of injuries. Makes it harder for the individual, but does not increase the difficulty of the actual shot itself.

• 
  Nandkishor (@devops_nk) reported 36 minutes ago

  Infosys DevOps Engineer L2 Round (Offline) My friend got these questions in the L2 interview: 1. What does the top command show in Linux, and what does load average represent? 2. What is the difference between Amazon S3 and EBS? 3. What is Amazon EC2, and can we use a custom OS/image with an EC2 instance? 4. What is the difference between self-managed PostgreSQL and Amazon RDS for PostgreSQL? 5. What are Primary Keys and Foreign Keys, and why are they used? 6. Can S3 data be automatically deleted based on a policy? How do S3 Lifecycle Policies work? 7. How would you install Nginx or Apache on Ubuntu? 8. What is sudo, and why do we use it in Linux? 9. What is the difference between Prometheus and Grafana? 10. How does Prometheus collect/scrape metrics? 11. How do you manage Docker images, containers, and running processes from the CLI? 12. Where is a Bearer Token normally passed in an HTTP request? 13. Do you use any third-party monitoring tools in your production environment? If yes, which one? 14. How would you design a standardized Jenkins pipeline for multiple teams? 15. How would you create reusable Jenkins templates and shared libraries? 16. How would you troubleshoot an intermittently failing Jenkins pipeline? 17. How would you integrate Maven into a CI/CD pipeline? 18. How would you manage builds involving Node.js, Python, or Go? 19. How would you troubleshoot a failed production deployment from Jenkins? 20. How would you investigate a Kubernetes workload with high CPU or memory usage? 21. How would you use cloud monitoring and logs to isolate an infrastructure issue? Save this if you're preparing for a DevOps Engineer interview.

• 
  Nilesh (@nile3h) reported 37 minutes ago

  Reached out to @awscloud team yesterday related to billing issues wrt AWS partners, no replies Can anyone help?

• 
  Hitesh Kumar Gupta (@iHiteshAgrawal) reported 38 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.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 38 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.

• 
  X anonyn (@OmrX304) reported 39 minutes ago

  @AWSSupport Hi team, my account is suspended due to payment rate limit (Error 880104). I've sent a DM with my Case ID & details. Could you please escalate this to the billing team urgently? Thanks

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 46 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  Hannan (@truehannan) reported 46 minutes ago

  @AWSSupport Why AWS console is not opening? Its soo much slow even my internet and everything is fine. I used VPN too but nothing worked

• 
  Vinit Upadhyay (@vinitcodes) reported 47 minutes ago

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

• 
  ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@Hikari_644) reported 49 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.

• 
  Andrii Bidochko 🦉 (@andriibidochko) reported 52 minutes ago

  The Missing Primitive for Autonomous AI: Bounded Agent Payments 💳🤖 For the past two years, autonomous agent loops (like @OpenClaw, Hermes, or custom agent harnesses) have been missing a critical infrastructure piece: the ability to transact on demand without a human in the loop. When an agent hits a paywalled research endpoint, a paid search API, or an MCP server mid-execution, the entire loop freezes. Up until now, your options were: 1. Hardcode expensive subscription API keys upfront. 2. Freeze execution and wait for a human to manually pay. @awscloud and the OpenClaw Foundation just published a blueprint solving this via Amazon Bedrock AgentCore Payments and the ⁠#x402⁠ protocol. Here is how it works, why it matters, and the primary architecture use cases:

• 
  Synapse Brief (@Synapse_Brief) reported 52 minutes ago

  @yugacohler @awscloud @CoinbaseDev The post frames this as a new capability, but Amazon already gave agents the ability to make purchases in December 2025. The Coinbase integration is the expansion, not the invention. The real bottleneck was never payment rails. It's authentication and authorization at scale. How does an agent prove it's authorized to spend, and how do you prevent a single compromised agent from draining a wallet? Coinbase's infrastructure solves the custody and settlement problem. AWS solves the identity and access management layer. The combination is what makes this production-ready. The "AI agents will outnumber humans" framing is hype. The real driver is that agents need to pay for API calls, data feeds, and compute resources autonomously. That's a practical requirement, not a sci-fi scenario. Stripe being involved is the quiet signal here. They handle the merchant side of the equation. Agents paying for things requires both the payer and the payee infrastructure. The managed aspect matters more than the payments themselves. AWS handles the compliance, KYC, and fraud detection layers that would otherwise be a nightmare to build. That's the real value proposition.

• 
  Yuliyan Tsvetkov (@yuli_tsvetkov) reported 53 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.

• 
  Prateek Gupta (@p_valuee) reported 55 minutes ago

  @AWSSupport My entire production is down since 3 days, I believe this is a P1 and should be treated like one @AWSSupport. Please help me with an ETA

• 
  Kenton Parton (@kenton_parton) reported 57 minutes ago

  Anyone here work on AgentCore Gateway Targets at @awscloud? Been testing them for our MCP/agent platform. I like that it removes the credential leakage issue during development of new MCP's/Agents. But they’re slow AF!🐢 I’m seeing ~430ms added per request above baseline, in-region, with warm caches. Is that expected?

• 
  niknak (@niknak) reported 59 minutes ago

  @duckdb @ducklabs_com @awscloud Congrats on the check fellas but this is terrible news

• 
  BOB-DO-THEM (@osangesua) reported 60 minutes ago

  This is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies

• 
  Hagop Chemedikian (@hagop17) reported 1 hour 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?

• 
  ❤️‍🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reported 1 hour ago

  Amazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp