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
Township of Evan	Sign in	10 days ago
Pottstown	Website Down	14 days ago
Iztacalco	Website Down	17 days ago
Boca da Mata	Errors	29 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	2 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:

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

• 
  Base Builder (@basedbuilder_io) reported 8 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.

• 
  Nandkishor (@devops_nk) reported 8 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.

• 
  Kenton Parton (@kenton_parton) reported 9 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?

• 
  Corey Quinn (@QuinnyPig) reported 12 minutes ago

  @awscloud You have all the tools to fix this, someone’s just apparently too scared to give Charlie a crossbow and diplomatic immunity. Give him the crossbow and stand back, @satyanadella.

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

  Is @awscloud down right now? #AWSDownAgain #AwsDown

• 
  Ricci Research (@ricci_nov) reported 16 minutes ago

  @nvidia @awscloud The buried detail is "Vera CPU server" — NVIDIA hand-delivering an ARM CPU to the company that built Graviton to escape CPU vendors. The GPU is the ticket; the CPU is the trojan horse into the one socket AWS thought it had reclaimed.

• 
  Ümit Kaan Usta (@umitkaanusta) reported 18 minutes ago

  @AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like “An error occurred calling the API: describeAddresses.” Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1

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

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

• 
  Robat Das Orvi (@orvi_onethread) reported 22 minutes ago

  Does @awscloud have any real people in support? 😤 Frustrated after trying to reach a human for over an hour. Our server is completely down right now, and we can't get through. Terrible experience. We might finally have to switch away from AWS.

• 
  Synapse Brief (@Synapse_Brief) reported 22 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.

• 
  Omni (@omnishredder_) reported 24 minutes ago

  @AmazonUK @Twitch @awscloud sort yo ****, I'm getting tired of ironically the last two days unable to watch twitch without lag or buffering at random with no explanation, it's almost like the ******* AI training is the problem that nobody wanted! How about ******* remove it!

• 
  Corey Quinn (@QuinnyPig) reported 25 minutes ago

  I want to hear the inside story of the largest @awscloud project. Not bill run, nor S3. I’m talking about what it took to fix all the hardcoded “jeff@“ userID stuff when @ajassy rose. Not kidding: it woulda been orders of magnitude easier for him to change his name to “Jeff.”

• 
  Vera ¤⩊¤ (@VeraSimila) reported 26 minutes ago

  @awscloud L+ Ratio Fix Twitch please, nobody wants AI hype beast corpo speak

• 
  Krishna.Ki.Shor (KK) (@kkbava) reported 27 minutes ago

  @AmazonHelp You are still giving me work!😡 Why not look inwards and check if order was indeed delivered? And tell the software geeks and nerds that there is a problem with conflicting messages? Learn from failures guys! That's what I learnt from @awscloud

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

• 
  Jose njui (@jsnjui) reported 34 minutes ago

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

• 
  mark seery (@140ismymax) reported 35 minutes ago

  Peter DeSantis talking at #agenticaisummit There will NOT be one AI chip type. If multiple AI chips take multiple years to bring to market, you have to be making assumptions about model requirements in that time frame. It's a systems problem, including the network. Constraint drives innovation. Future is bright and built together. Peter DeSantis SVP, Foundational AI Models, Custom Silicon, Quantum Computing, Amazon @awscloud @amazon @BerkeleyRDI

• 
  Dan Lynch (@danlynch) reported 35 minutes ago

  @QuinnyPig @awscloud I need to sign in with LEGO 😎

• 
  Ondřej Flídr (@snipercze) reported 38 minutes ago

  Hello @AWSSupport, is there any problem with EBS subsystem in us-east-2 (Ohio region)? Cannot resize volume (ending with internal error, same for console and CloudFormation), new volume is created but stuck in "Attaching" to the EC2. Thanks for check

• 
  Jonny Castles (@jonny_castles) reported 39 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 47 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.

• 
  absk (@abskwdkr) reported 49 minutes ago

  My ec2 ssh logs in too slow and lags @AWSSupport

• 
  niknak (@niknak) reported 50 minutes ago

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

• 
  Mr Sage (@GreatSage_0x) reported 52 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

• 
  Joy | 🔥 (@JoyKingdomx) reported 52 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.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 56 minutes ago

  @AWSSupport @AWSSupport Appreciate the reply, but I've heard this exact message every day this week. At what point does a 5+ day production-down case qualify for actual escalation? Please have an escalation manager or TAM contact me directly, the Support Center loop isn't working.

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

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

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