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

Is Amazon Web Services down?

Service-wide status: Amazon Web Services

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

Amazon Web Services signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

  • Service-wide signals
  • Service-wide baseline

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 15 days ago
Pottstown Website Down 20 days ago
Iztacalco Website Down 23 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:

  • orvi_onethread
    Robat Das Orvi (@orvi_onethread) reported

    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.

  • ssybb1988
    ShenYubao (@ssybb1988) reported

    @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

  • hagop17
    Hagop Chemedikian (@hagop17) reported

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

  • AMyrick1989
    Amanda (@AMyrick1989) reported

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

  • HandbrakeHarry
    Haresh Kukkreja (@HandbrakeHarry) reported

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

  • jaiminvaghani
    Jaimin Vaghani (@jaiminvaghani) reported

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

  • iproductAI
    Priyanshu (@iproductAI) reported

    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.

  • jaiminvaghani
    Jaimin Vaghani (@jaiminvaghani) reported

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

  • Ronindrake2
    Jacklyn Taylor (@Ronindrake2) reported

    @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

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

    @AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?

  • ngriffin_uk
    Nicholas Griffin (@ngriffin_uk) reported

    @QuinnyPig @awscloud that’s real? it looks like someone who doesnt know how to prompt made a sign in screen and didnt look at it.

  • QuinnyPig
    Corey Quinn (@QuinnyPig) reported

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

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

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

  • chintan86
    Chintan Shah (@chintan86) reported

    @AWSSupport @awscloud Dues cleared, reinstatement requested — still waiting with no movement. My production workloads are down and every hour is costing us. Can someone please prioritise this? Case ID ready to share over DM.

  • PolyPup
    PolyPup (@PolyPup) reported

    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.

  • Bethco2257
    Pixi Dust (@Bethco2257) reported

    @FmrRepMTG @amazon @awscloud walk into any Amazon office building at Seattle HQ and South Lake Union Amazon Seattle offices and instantly you can see with your own eyes… nearly 80% of staff are HB1 visa holders!!!! So yes, we have a big problem.

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

  • QuinnyPig
    Corey Quinn (@QuinnyPig) reported

    I’m going to get a job at @awscloud, immediately fix one bug, then resign. Which bug should it be?

  • randomfrequency
    @Randomfrequency@mastodon.social (@randomfrequency) reported

    @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

  • Aqib_Ansari_
    Aqib Ansari (@Aqib_Ansari_) reported

    @AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience

  • Southclaws
    barney (@Southclaws) reported

    @jonny_castles @awscloud I am seeing this too, ECR and S3 in eu-west-1, lots of "service unavailable" errors

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

  • jake__somers
    Somers (@jake__somers) reported

    AWS keeps charging me 1000x what it should be for inference I try to use the new "generally available" Grok 4.6 Prompt caching doesn't work at all I spend $1.9 worth of inference testing caching I see my AWS bill is now $3400 This was an issue months ago as well. @AWSSupport

  • DroidBoyJr
    Sumedh More (@DroidBoyJr) reported

    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

  • VeraSimila
    Vera ¤⩊¤ (@VeraSimila) reported

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

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

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

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

    @Cloudflare @awscloud Fix human verification

  • Ronindrake2
    Jacklyn Taylor (@Ronindrake2) reported

    @awscloud @AmazonHelp @amazon Yo, can any of yall explain why a review that gets flagged for "community guidelines" refuses to tell you what the issue is? Like yall's bot goes "it violates rules!" But cant tell me what part? It obviously had to note what the issue was...

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

  • adelbucetta
    Adel Bucetta (@adelbucetta) reported

    @Deeen_Codes @awscloud @devpost the real unlock here isn't just solving the hackathon prompt but figuring out what problems to automate first

Amazon Web Services detected incident history

These records describe service-wide increases in reported problems. They do not confirm an outage at every address. Recorded end times describe our detection window, not a provider-confirmed repair.

  • Detected:
    Detection ended: (24 minutes)
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.
  • Detected:
    No end recorded. This alone does not establish the current status.

What to do if Amazon Web Services is not working

Compare your issue with the local reports and map. Note the affected service and when the problem began before contacting Amazon Web Services; report your own experience using the report button above.

How to interpret these reports

Direct reports are submitted by visitors. Locations may be estimated from their connection or supplied by the reporter. A low local count does not establish that service is working; the service-wide status and local report totals describe different areas. How our outage detection works