1. Home
  2. Companies
  3. Amazon Web Services
Amazon Web Services

Amazon Web Services status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Amazon Web Services (AWS) offers a suite of cloud-computing services that make up an on-demand computing platform. They include Amazon Elastic Compute Cloud, also known as "EC2", and Amazon Simple Storage Service, also known as "S3".

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.

At the moment, we haven't detected any problems at Amazon Web Services. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Amazon Web Services users through our website.

  • 71% Website Down (71%)
  • 14% Sign in (14%)
  • 14% Errors (14%)

Live Outage Map

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

CityProblem TypeReport Time
Township of Evan Sign in 13 days ago
Pottstown Website Down 18 days ago
Iztacalco Website Down 21 days ago
Boca da Mata Errors 1 month ago
Township of Evan Website Down 2 months 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:

  • mjovanovictech
    Milan Jovanović (@mjovanovictech) reported

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

  • harundotdev
    Harun R. (@harundotdev) reported

    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.

  • kenton_parton
    Kenton Parton (@kenton_parton) reported

    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?

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

    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

  • ProgrammerDude
    Arian van Putten (@ProgrammerDude) reported

    @QuinnyPig @awscloud Are they gonna fix people needing to know what region their orgs IAM identity center is deployed in order to set up cli login? (How the heck would an employee know this??)

  • ranbirnxt
    Ranbir Mahapatra (@ranbirnxt) reported

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

  • Mrwho23
    MrWho (@Mrwho23) reported

    @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

  • john15489
    Art Vandelay (@john15489) reported

    @amazon @awscloud @nvidia I need an actual customer service phone number so I can actually speak to a ******* rep regarding 4 orders now. Your email help system is broken.

  • mailbox28564784
    mail box (@mailbox28564784) reported

    @amazonIN @amazon @awscloud But in my personal experience, this response has never led to a real solution. They keep asking for the same details again and again, yet my issue remains unresolved. My ₹1,400 refund is still pending, and I have neither received a replacement nor-2

  • reze_xqc
    Siya (@reze_xqc) reported

    @AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.

  • TeeBeeCTO
    TeeBeeCTO (@TeeBeeCTO) reported

    Setting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!

  • omnishredder_
    Omni (@omnishredder_) reported

    @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!

  • p_valuee
    Prateek Gupta (@p_valuee) reported

    AWS suspended my account for billing. I have zero due invoices and zero past-due invoices. Their own Amazon Q agent confirmed it in writing. P1 case 178635853400575, day 3, production still down. @AWSSupport what is the actual reason?

  • niknak
    niknak (@niknak) reported

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

  • truehannan
    Hannan (@truehannan) reported

    @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

  • natedenh
    Nathan Den Herder (@natedenh) reported

    @xai @awscloud grok-4.6 on Bedrock us-east-1 is unusable today. 5-token prompt, maxTokens=16: claude-sonnet-4-5 → 3.0s us.xai.grok-4.6 → 150s timeout global.xai.grok-4.6 → 150s timeout Same account, region, creds. No throttle error, no 5xx — it just hangs.

  • schematical
    Matt Lea (@schematical) reported

    @PhilipAnderse @awscloud @amazon What's the problem? I know a thing or two about AWS.

  • wilczynski24
    Maciej Wilczyński (@wilczynski24) reported

    @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.

  • natedenh
    Nathan Den Herder (@natedenh) reported

    I realize that I use @awscloud Bedrock, and this may be part of the issue, but @grok 4.6 is not usable on this platform compared to @claudeai Opus 5. I've really tried everything to make it work but I don't think there is any comparison.

  • basedbuilder_io
    Base Builder (@basedbuilder_io) reported

    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.

  • RWayodi
    Bravo One💀 (@RWayodi) reported

    @AWSSupport Hello. I received a charge on my credit card to Amazon EMEA but I do not have an Amazon AWS account. I am unable to create a case as it requires me to sign in. How is this even possible?

  • hsnice16
    Himanshu Singh (@hsnice16) reported

    Been using LLMs a lot to write code recently. Sometimes I learn a few new things, and sometimes it just confuses itself and me, maybe because there is no one right way to do things. Recently, while working on a pricing page for a new product we've been developing, a senior team member suggested that it would be better to extract it into a separate codebase and deploy the frontend separately. He would then route it through CloudFront under the same origin to avoid cross-origin issues when transferring credentials. I learned that using `*` for `Access-Control-Allow-Origin` doesn't work for credentialed CORS requests. But before all of this worked, I had extracted the pricing frontend into the same codebase, just in a new folder with the required files, and was trying to deploy it on the same infrastructure the rest of the application was using on @awscloud. It wasn't working because there were some issues between the build output and the CDK synthesis/deployment stages. Eventually, I extracted the code into a completely new repository and deployed it on @vercel.

  • g00manoid
    Arick Goomanovsky (@g00manoid) reported

    @awscloud It's worse than technical debt in one way - sprawl compounds through the connections, not just the count. Ten agents with no shared context or ownership isn't ten problems, it's every pair of them. The fix is a connective layer that makes them a network instead of scattered debt.

  • jcastillo4tx
    Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported

    @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.

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

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

  • CatalinC_Uk
    Catalin C (@CatalinC_Uk) reported

    @awscloud AI bot traffic’s surge forces a tough choice: lock it down or risk diluted engagement.

  • DataChaz
    Chaz Wargnier ♨️ (@DataChaz) reported

    Let's take @Snowflake as an example. Working there gave me a clear view of the data problems hiding behind most ambitious AI roadmaps. Because Snowflake is natively deployed on AWS and available through the AWS Marketplace, it fits right into a modern stack. If you are building an AI feature, a sensible pattern looks like this: > Isolated customer events land securely in Amazon S3 from day one > Snowflake transforms raw data into a governed, usable layer > Flexible Amazon ECS compute routes only approved context to Amazon Bedrock Getting this pipeline right early means less time fixing data leaks and more time shipping AI features ↓

  • OmrX304
    X anonyn (@OmrX304) reported

    @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

  • baricadelane
    lak-alak (@baricadelane) reported

    @IanCarrollShow @BacklotOPS @NickJFreitas They must think we are stupid Tyler Robinson decoys all over the place d captured on camera all doing their part for 1990s pixalated images produced and sold as 4k in 2026 lmao. Why did Amazon aws services shut down 9/10 - 9/25? Who owns discord?

  • FrancisYuyun
    Yuyun Francis (@FrancisYuyun) reported

    @AWSSupport case ID (178590975600210) "account activation blocked 2+ weeks by Error 880104, case escalated internally Aug 5, no update since."