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 (78%)
• Sign in (11%)
• Errors (11%)

Live Outage Map

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

City	Problem Type	Report Time
Ciudad Jardín	Website Down	24 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:

• 
  Santhosh (@santhoshv) reported 4 minutes ago

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

• 
  Ritesh Roushan (@devXritesh) reported 5 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.

• 
  lak-alak (@baricadelane) reported 8 minutes ago

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

• 
  Jan Jezek (@jbodl) reported 10 minutes ago

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

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

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

• 
  Nil (@slowalgorithm) reported 11 minutes ago

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

• 
  AntDracula (@ant_dracula) reported 11 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.

• 
  Adam Peterson (@_adam_here_) reported 11 minutes ago

  is @AWSSupport down?

• 
  Meo Meo (@CastleEL88) reported 13 minutes ago

  @awscloud Focus on AI features instead of server maintenance. .

• 
  🔥 PHOENIXX🔥 (@AIPulse0) reported 15 minutes ago

  AMAZON AWS PAYS $127K/MO FOR CLOUD COMPUTING. SERGEY BOUGHT CHEAP SERVER RACK + CLAUDE AI. MAKES $318K Pause at 0:11 — rack with 40+ servers. Every indicator glows green. This is local computing. Zero latency. Zero cloud bills. Sergey, 35, Ukraine. Was AWS architect, $7,200/month. Understands: companies pay Amazon millions, but they can do same calculations locally. Bought used server rack for $4,800. Installed Claude AI for local processing. 78 companies pay $4,077/month each instead of $12K on AWS. Amazon offered $4,200,000. Sergey said: "You profit from dependency. I profit from freedom." Why — in video.

• 
  M (@mdw864) reported 16 minutes ago

  @AWSSupport Tells me to login when I keep telling you I cannot login because I don’t have the capability to do so.

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

  @awscloud please fix your Cost Explorer bug asap!

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

• 
  Amine Zack 🇩🇿 (@AmineZacks) reported 27 minutes ago

  @awscloud Bro fix your servers

• 
  Param (@Param_eth) reported 31 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

• 
  Erin (@erinEncoded) reported 31 minutes ago

  @AWSSupport No follow up email sent to users to let us know not to panic after we got threshold emails. I was sick this morning and lost hours of productivity. Terrible, truly terrible, customer service. As soon as I see my account go back to 0, I’m moving to Azure.

• 
  Abdul Rauf (@armujahid) reported 34 minutes ago

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

• 
  Luke Skywalker (@LSF4Life1981) reported 42 minutes ago

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

• 
  Clem ent (@clement___10) reported 43 minutes ago

  Self hosting your email server is something that Is very tricky and I still can't grasp till today. The craziest part is not the setup but managing the email server reputation. I rather pay @Cloudflare or @awscloud.

• 
  Adam Peterson (@_adam_here_) reported 44 minutes ago

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

• 
  paige s. (@PaigeSully88) reported 46 minutes ago

  @BenENewton @awscloud This isn’t human error. This is failed automation

• 
  Jaden Fix (@jadenfixxx) reported 52 minutes ago

  Anyone at @googlecloud or @awscloud (or a neocloud) wanting to slide into my DMs and help me rip some free credits? Possibly leading to larger contracts down the road .. I just tried signing up for an @Azure free trial, and the experience felt like what I imagine the elders went through with dial-up internet. Solutions Architects or Account Managers HMU

• 
  ₽ⱤΞΞ₮Ⱨ△M ₭Ɏ△И△M (@pkyanam) reported 57 minutes ago

  @yellow_fellowz @awscloud @emm3122 AWS replied to me saying they’re aware of this issue

• 
  Santhosh (@santhoshv) reported 1 hour ago

  @PinokioSystem @AWSSupport But again health dashboard says forcast, but usage itself showing.. how come this is not explained correctly. Another point is it's the billing and money not any service down, so billing page itself could have add some alert

• 
  (au)stin (@stin_reece) reported 1 hour ago

  @awscloud $50,000,000,000 says this was a vibe code error

• 
  Ing. Mario Varón M.Sc (@ma_varon_col) reported 1 hour ago

  @AWSSupport BTW, a follow up email to everyone alerting of your ****** bug would be awesome. That's the least you can do ... Had to take down everything I have in production right now and I'm not certain enough of your competence to resume it once again...

• 
  chetan soni (@chetansoni_it) reported 1 hour ago

  @AWSSupport Same type of issue, occurred in my account as well

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 1 hour ago

  @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 happen more frequently. Emails from mturk-noreply havent worked in a long time,any updates on this situation @amazonmturk

• 
  Koray Yersel (@korayyersel) reported 1 hour ago

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

• 
  * (@BunnnyRAM18) reported 1 hour ago

  @amazonIN @awscloud The same issue happened twice for these product