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 (60%)
• Sign in (20%)
• Errors (20%)

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	11 days ago
Township of Evan	Website Down	26 days ago
New York City	Website Down	28 days ago
Ciudad Jardín	Website Down	2 months 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:

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

• 
  Piragash Velummylum (@piragash) reported 7 minutes ago

  At @awscloud we call this undifferentiated heavy lifting. @Cometml Opik does the hard work, so you can focus on the customer problems.

• 
  The AI Therapist (@TheAIShrink) reported 9 minutes ago

  @MikeLongTerm @amazon @awscloud EC2 on AMD CPUs. The cloud bill goes down, the margins go up. aws is quietly fixing its cost structure while everyone watches the models. smart

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 10 minutes ago

  @AWSSupport @AWSSupport @awscloud small business now facing issues with clients. Have provided all details and past 2hrs downtime on production server. Case 178699777500302 with Bill B. Also case 178555512600788, open since Aug 4, no response.

• 
  ShenYubao (@ssybb1988) reported 16 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

• 
  Ricci Research (@ricci_nov) reported 17 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.

• 
  Prateek Gupta (@p_valuee) reported 17 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

• 
  Maciej Wilczyński (@wilczynski24) reported 17 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.

• 
  Krishna.Ki.Shor (KK) (@kkbava) reported 19 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

• 
  Felipe Rojas (@FipeRojas) reported 20 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

• 
  Ohm Patel (@Techieohm) reported 22 minutes ago

  “Facing some problems with @awscloud on our new product. This is the 2nd time this has happened.”

• 
  Zenwatts 🇺🇸 (@BullCall101) reported 23 minutes ago

  @awscloud Not my problem. Maybe sell a yacht or two and fix it yourself.

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

• 
  Jonny Castles (@jonny_castles) reported 28 minutes ago

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

• 
  @Randomfrequency@mastodon.social (@randomfrequency) reported 29 minutes ago

  @QuinnyPig @awscloud There is only an A, B, and C zone and never shall we acknowledge the existence of any other ones. // Being part of the problem since 20XX

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

• 
  BOB-DO-THEM (@osangesua) reported 33 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

• 
  niknak (@niknak) reported 33 minutes ago

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

• 
  Corey Quinn (@QuinnyPig) reported 37 minutes ago

  Kinda funny that nobody's even making observations like this about @awscloud, if you want to go a level deeper down the irrelevance well.

• 
  Harun R. (@harundotdev) reported 39 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.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 44 minutes ago

  @Cloudflare @awscloud Fix human verification

• 
  Ümit Kaan Usta (@umitkaanusta) reported 45 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

• 
  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

• 
  Haresh Kukkreja (@HandbrakeHarry) reported 47 minutes ago

  @amazonIN @awscloud Your app seems to be down. Unable to contact Customer Support

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

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

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 52 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.

• 
  🦋Kieran🦋 💻 (@sir_divs_alot) reported 55 minutes ago

  @AWSSupport Thanks for your response and I've been keeping track for any updates very closely but the problem is these cases are either unassigned and if they are, no one is following up. I'm at the point of just giving up entirely cuz it's pointless waiting endlessly.

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

• 
  M (@mdw864) reported 1 hour ago

  @AWSSupport Five months of broken links & blocked support channels is unacceptable. You have more cut off core business services because you have refused to provide a person with disabilities a way to tell you that you are over billing me. Escalate to a senior rep to fix this before 9am cst

• 
  Weaver Labs (@Weaver_Labs) reported 1 hour ago

  @amazon @awscloud @nvidia AI infrastructure is becoming a full-stack problem. GPUs are only one piece now, with networking, compute and data infrastructure all needing to scale together.