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 (80%)
• Sign in (10%)
• Errors (10%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Website Down	7 hours ago
Ciudad Jardín	Website Down	25 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

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:

• 
  Drate Berry (@drateberry) reported 4 minutes ago

  Is anyone else experiencing issues with the @awscloud Billing system? I’m trying to add a new card and both the physical and virtual versions are throwing a verification issue. Bank is saying they don’t see anything on their end. Waiting to hear back from AWS Support.

• 
  kyun anon (Gobhi ka fool ) (@anondis1122) reported 7 minutes ago

  @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

• 
  Naren Bao 包娜仁 | Physical AI Agents (@NarenBao) reported 7 minutes ago

  @awscloud please fix your Cost Explorer bug asap!

• 
  JoeFromSJersey (@JoeFromSJersey) reported 9 minutes ago

  @AWSSupport Good morning folks, I appreciate the help getting things working for me yesterday as I was able to use Kiro! I'm not unable to upgrade from free tier though and get an error that says unable to upgrade. I've a case for that too and was hoping you could also get eyes on that.

• 
  J (@kankerhoerrrrrr) reported 9 minutes ago

  @marcelocantos @awscloud you're a moron. it was a known, and widespread issue, and they even had a notice in the health dashboard. this is a skill issue.

• 
  Fikri Firdaus (@fikrfird) reported 9 minutes ago

  @awscloud This really isn’t something to joke about. A false billing alert at this scale can cause genuine panic and even serious health consequences. Some users may have rotated credentials, shut down workloads, or deleted services because they feared their accounts had been compromised.

• 
  Kartik Jain (@kartikjain0101) reported 10 minutes ago

  @awscloud you guy has lost your mind. payment got missing so team told me they will raising the request. account got hold, we have 250K unused credits, and now they are not initiation the account. wtf. our whole production is down.

• 
  Adam Peterson (@_adam_here_) reported 12 minutes ago

  @AWSSupport Even the AWS health page was down. Total AWS system downtime for 12-13 minutes. AWS appears back now.

• 
  IDrabs (@drabs_i) reported 13 minutes ago

  @PlayStation @awscloud Wtf you playing at fix the outage.

• 
  Ritesh Roushan (@devXritesh) reported 15 minutes ago

  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.

• 
  Abdul Rauf (@armujahid) reported 18 minutes ago

  @miserer3_mei @AWSSupport It's a known issue that they are already checking

• 
  Nil (@slowalgorithm) reported 20 minutes ago

  @awscloud The LEAST you can do is to give some compensation. This mistake caused operational issues for several companies across the globe.

• 
  Param (@Param_eth) reported 23 minutes ago

  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

• 
  AntDracula (@ant_dracula) reported 25 minutes ago

  @kankerhoerrrrrr @marcelocantos @awscloud And you had no response for "what's the alternative to shutting down services, just pay the bill?" Maybe you really are an AI bot instead of a retard.

• 
  Aaryan Bansal (@NotUnHackable) reported 25 minutes ago

  @awscloud that issue was happening since yesterday dude. why tf did it take so much time?

• 
  Mario Giampieri (@mario_giampieri) reported 26 minutes ago

  @AWSSupport Another update- I received a canned response explaining to me what sign in credentials are and sending me a link to open a new account. Eleven months of this.

• 
  golden gate bridge (@_ggbridge) reported 27 minutes ago

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

• 
  Harikrishna KP (@harikp2002) reported 28 minutes ago

  @AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!

• 
  PositiveVibes (@KPTheFighter) reported 31 minutes ago

  @awscloud @AWS You guys almost gave me heart attack today morning. When saw the email from you with billing about $192 million, I got shaken up, frozen. Logged into dashboard , and saw same amount. Imagine what would have been the state of mind. This is not done!! Mistakes do happen, being in tech industry, I do understand that. But once you recognised that mistake, you did not have courtesy to send an email to all users asking not to Panic. That is not acceptable. Before one could reach to support page, his soul would leave the body. Immediately you should have put a banner on dashboard reporting about the potential issue and could have sent a next communication to users informing them. You didn’t do anything of that sort and left users in panicked state. This is so unprofessional. Really disappointed!!! You would have been responsible if anything tragic happened to me today just because of your negligence. A communication asking users to ignore the faulty email was due. You didn’t do that. Shameful!! #awsbilling #aws

• 
  D (@D8118199174282) reported 32 minutes ago

  @awscloud No, you still haven’t compensated users for the cost bug error

• 
  billy (@Billy17979063) reported 33 minutes ago

  @fortniteleaksmy It’s up for some down for some @awscloud ******* decides to shut down not just PlayStation but other platforms too

• 
  Sudeep (@sudee1285) reported 34 minutes ago

  I need assistance to access existing APN account...it's getting error.. please help me. @awscloud

• 
  The AI Therapist (@TheAIShrink) reported 35 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

• 
  Matthew (@OneShotCaller) reported 44 minutes ago

  @CalebChamberla6 It’s an AWS billing error (see @awscloud)

• 
  Mike Webb (@themikebwebb) reported 45 minutes ago

  @awscloud You should be the first cloud provider to issue a billing usage reset.

• 
  mark seery (@140ismymax) reported 45 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 #AI

• 
  AntDracula (@ant_dracula) reported 50 minutes ago

  @kankerhoerrrrrr @marcelocantos @awscloud "skill issue" is a term only unironically used by losers and AI bots. I can take a guess at which one you are.

• 
  Eszter Morvay (@eszter_morvay) reported 51 minutes ago

  @AWSSupport Also - apologies for the DM issues, i just changed my settings, so DMs should work now

• 
  Gabriel (@doktorgphd) reported 55 minutes ago

  @awscloud wow really??? i had to search x for the reason?? not even an email?? I saw the email sent yesterday about the cost alert and I spend the last hour trying to work out what is going on because it looks very legit and I only find out it was an error on x! Just had to send an email!!

• 
  Luke Skywalker (@LSF4Life1981) reported 1 hour ago

  @RinoTheBouncer Just like you can't be bothered to Google anything PSN issue was @awscloud which doesn't say anything either