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.

  • 78% Website Down (78%)
  • 11% Sign in (11%)
  • 11% Errors (11%)

Live Outage Map

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

CityProblem TypeReport Time
Ciudad Jardín Website Down 22 days ago
Kyiv Sign in 2 months ago
Chennai Website Down 2 months ago
Point Pleasant Beach Website Down 2 months ago
Little Rock Errors 2 months ago
Atlanta 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:

  • thewebbie
    Matthew Feinberg (@thewebbie) reported

    @infoscav @awscloud 28 Billion! AWS has acknowledged there is a problem with the billing console.

  • korayyersel
    Koray Yersel (@korayyersel) reported

    @AWSSupport My balance went down to zero. Time to the delete aws account

  • edwarddonner
    Edward Donner (@edwarddonner) reported

    @BaconOverflow @awscloud I'm an experienced technologist. Yes a bug was likely. My fear was I'd made a terrible mistake or leaked credentials. AWS customers are on the hook for either. AWS has no hard caps. My initial alerts were high but not billions. For 10 mins I thought this just might be real.

  • deibeat_13
    deibeat (@deibeat_13) reported

    @AWSSupport I did the same exactly, and really panicked when I saw that, thought someone got access or something. Tried to contact billing support, removed s3 bucket, turned off a personal website using it, asked Claude for guidance until I finally found it was a global issue…

  • dvtoever
    Daniël (@dvtoever) reported

    @marcelocantos @awscloud Totally agree. I my took hours for the stress to leave my body. I tought i was hacked and my services were abused. They didnt bother to take down the billing page temporarily with a warning or sent a follow up mail pointing out this bug.I am going to close down my account as well

  • mdw864
    M (@mdw864) reported

    @AWSSupport Either that or ask me to login, which I keep telling you I cannot login. It has nothing to do with 2FA. That is not the issue.

  • ant_dracula
    AntDracula (@ant_dracula) reported

    @_LeadPoisoning_ @awscloud That’s because it’s never up long enough to generate an error

  • senorculver
    Robert Culver (@senorculver) reported

    @awscloud Wow, that’s it, no explanation? No, and for your trouble, and extra work and panic, a free month of service or anything. Just our bad, see you next month?

  • RickDavis404
    RickDavis404 (@RickDavis404) reported

    @awscloud I left an EKS cluster running while waiting for my Fable 5 limit to reset...only been a few days, but Opus says my aws bill was pretty accurate, just a small rounding error, still over 950 trillion dollars 🤑

  • santhoshv
    Santhosh (@santhoshv) reported

    @D8118199174282 @AWSSupport Many stopped services, also I never assumed health issues with billing itself

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

  • CaptAmericaTx
    CaptainAmericaTex (@CaptAmericaTx) reported

    @LayoffAI During the last 12 months Amazon AWS had outages directly caused by initiatives from the AI group (with associated revenue impact). No surprise they are down sizing the snake oil sales men group.

  • pcgamer11
    Steven Coburn (@pcgamer11) reported

    @PlayStation We can't play the open beta rn because PSN IS DOWN. Yes, it uses/runs on @awscloud but you could at least ACKNOWLEDGE the issue!!!

  • vaibhavkhatrii
    Vaibhav Khatri (@vaibhavkhatrii) reported

    @AWSSupport Believe me when I saw this, I had to check my BP. No issue is more than someone’s life.

  • melon_thief
    bittermelon (@melon_thief) reported

    @AWSSupport Moving my domains and hosting to Cloudflare. There should have been a service bulletin on the billing page explaining the issue

  • GettingMyGlitch
    GettingMyGlitchOff (@GettingMyGlitch) reported

    @AWSSupport Again there is a mass wave of suspensions like in May, I'm assuming in error as I've been on this platform for over 10 years and this seems to be happening more frequently. Emails from mturk-noreply havent worked in a long time so any updates on this situation?

  • pintofbeer
    David Madelin 🇺🇦 (@pintofbeer) reported

    @AWSSupport I just can't fathom how you are STILL showing these broken numbers in the dashboard, for god's sake, hide them! This is no joke; people will be really stressed out about this and might do irrational things.

  • indy_singh_uk
    Indy Singh (@indy_singh_uk) reported

    .@awscloud you might want to update your status page. Cloudfront is down.

  • JaoyadCode
    Md Jaoyad (@JaoyadCode) reported

    @awscloud you should fix it otherwise people will become sick after watching the bill!

  • mdw864
    M (@mdw864) reported

    @awscloud can you PLEASE answer me? You’ve just turned off my Business because you will not help me. I need you to stop charging me. Do not tell me to login because I do not know the email address that was used to open the account. All I know is my bank account is being charged

  • D8118199174282
    D (@D8118199174282) reported

    @AWSSupport Will the affected accounts be compensated for this issue?

  • perezcarreno
    Armando J. Perez-Carreno (@perezcarreno) reported

    @ngriffin_uk @awscloud The problem wasn’t only the billing page. Many people received billing usage alerts with tremendous spend. In our case, it was additionally frustrating because we couldn’t log in due to an MFA bug while we were about to board a ten hour flight. Some of us do care.

  • JeffBVockrodt
    Jeff B. Vockrodt (@JeffBVockrodt) reported

    @AWSSupport You should send follow up emails alerting all your customers to this issue. I woke up to a $719 million billing estimate which although absurd conjures a potential nightmare of getting it worked out

  • edwarddonner
    Edward Donner (@edwarddonner) reported

    @darkosubotica @awscloud @AWSSupport Thanks Darko. I'm keen to be involved. I'm aware there are challenges. A billing bug shouldn't cause a global outage or delete backups. I believe these are solvable. I don't want the possibility of financial ruin from a mistake or hack. Will DM.

  • devXritesh
    Ritesh Roushan (@devXritesh) reported

    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.

  • AnotherRadProd
    Wordy (@AnotherRadProd) reported

    @AWSSupport OMG... I was gonna have a heart attack! I haven't looked at this project for years and I can't even remember how to login!

  • jbodl
    Jan Jezek (@jbodl) reported

    @awscloud First you sent alerts that the account was over budget by 6-figure numbers. When the user logged in, the billing console confirmed the same. No banner there was an issue, no followup email, nothing. Just wannabe funny jokes on X. Seriously, AWS?

  • anondis1122
    kyun anon (Gobhi ka fool ) (@anondis1122) reported

    @AWSSupport @ashu_sharma17 Yeah. Why tf not send an email.. that there is an issue. I have a medical condition. It put my life in danger

  • Param_eth
    Param (@Param_eth) reported

    The downfall of Storj Labs (bankruptcy): - launches Storj in 2014 to build a decentralised alternative to cloud storage - promises a blockchain based competitor to Amazon S3. - attracts thousands of node operators across the world - raises around $35 million in funding - secures roughly $30 million through its 2017 token sale - spends years building its decentralised storage network - the DePIN business model proves difficult to scale profitably 2021: - $STORJ reaches its all time high 2022–2025: - the token enters a prolonged decline - node operators report declining rewards and operational issues - Storj begins selling non-core assets and right sizing operations October 2025: - Inveniam Capital Partners acquires Storj Labs - the acquisition is expected to strengthen the company's future - financial pressures remain unresolved July 2026: - Storj Labs files for Chapter 11 bankruptcy protection - the company says legacy liabilities can no longer be outgrown - assets and liabilities are estimated between $1 million and $10 million > operations > customer services > the storage network continue running - Inveniam backs the restructuring process - Storj proposes a plan that could give STORJ token holders equity in the reorganised company - $STORJ falls another 14–15% after the bankruptcy announcement - the token is down roughly 99% from its 2021 all time high

  • _ggbridge
    golden gate bridge (@_ggbridge) reported

    @litteralyme0 this happens to me everytime Amazon AWS has an outage