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
Township of Evan	Website Down	9 days ago
New York City	Website Down	12 days ago
Ciudad Jardín	Website Down	1 month ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	3 months ago
Point Pleasant Beach	Website Down	3 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:

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 4 minutes ago

  @AWSSupport Yeah its just getting automated responses to everyone saying "Your account will not be re-opened. We regret that we have not been able to address your concerns to your satisfaction." so can you send the mturk team a message to review the error since its more then just me its

• 
  Anjishnu Ganguly (@Anjishnu46) reported 6 minutes ago

  I posted again that day because the same issue was blocking our AWS Activate application too. @AWSSupport said it had been passed along again. Another public reply, same unusable account.

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

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

• 
  Samrat Singh (Sam) (@isamrats) reported 8 minutes ago

  @KahlonGurshaan @Rushike32313211 Yes its down , but no official confirmation posted by @awscloud yet

• 
  Adel Bucetta (@adelbucetta) reported 10 minutes ago

  @tushaarmehtaa @OpenAIDevs @awscloud back to school is just a Band-Aid on a larger issue: how do we make building with ai accessible for the next 50 million people, not just 50?

• 
  M (@mdw864) reported 11 minutes ago

  @googlecloud @GoogleCloudTech do you accommodate customers with disabilities? In case we have problems and need to speak to you? I think I may have to switch to you because @awscloud has not provided accommodations for people with disabilities.

• 
  Edward Donner (@edwarddonner) reported 11 minutes ago

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

• 
  Mahadev Vyavahare (@mahadevkv) reported 12 minutes ago

  @SarvamAI should learn from American companies on how to and what to document on internet Documentation and visibility is broken compared on sarvam website. Learn from @OpenAI and @awscloud

• 
  devastatindave.eth (@NftCelestials) reported 12 minutes ago

  @awscloud totally avoidable error caused by reliance on unskilled h1b scabs ya'll will learn eventually

• 
  JJ Ferman (@jjferman) reported 13 minutes ago

  @awscloud the fix: if bill > 1 quadrillion: we have a problem...

• 
  Daniël (@dvtoever) reported 14 minutes ago

  @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

• 
  Nilesh (@nile3h) reported 22 minutes ago

  Reached out to @awscloud team yesterday related to billing issues wrt AWS partners, no replies Can anyone help?

• 
  Keith Townsend (@CTOAdvisor) reported 27 minutes ago

  I spent over $120 in @awscloud so far this month. Most of it has been on GPU instances and Xeon 6. This is the most I've spent since I've had a long-running VM as a web app server a few years ago.

• 
  Jim Osman (@EdgeCGroup) reported 28 minutes ago

  @awscloud Real innovation starts with people solving real problems.

• 
  ❤️‍🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reported 29 minutes ago

  Amazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp

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

• 
  * (@BunnnyRAM18) reported 35 minutes ago

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

• 
  Ryan Varghese Mathew (@RyanVarghese14) reported 35 minutes ago

  Hi @awscloud @AWS I am currently facing issues from regarding certain payments. And despite incessantly reaching out on the support team and the email, I have been charged and there has been no formal support extended. I know you guys can do better than this.

• 
  M (@mdw864) reported 36 minutes ago

  @AWSSupport Five months of broken links & blocked support channels is unacceptable. You have more cut off core business services because you have refused to provide a person with disabilities a way to tell you that you are over billing me. Escalate to a senior rep to fix this before 9am cst

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

  @awscloud Bro fix your servers

• 
  kakafa.btc (@kakafa_btc) reported 42 minutes ago

  @AWSSupport Still NO resolution after 7 days! Case ID: 17849863000462 Account hold cleared days ago, but CloudFront is STILL locked due to a backend flag sync issue. @AWSSupport keeps passing the buck. Assign a supervisor to clear this flag NOW! @awscloud #AWS #CloudFront #AWSCloud

• 
  Ashmit Dutta (@ashmit105) reported 42 minutes ago

  @awscloud keeps charging me $60 a month. I can’t login to my account due to a deprecated email. Making support tickets goes nowhere. Anyone got advice on what to do?

• 
  Mr. Honkitude (@Mr_Honkitude) reported 45 minutes ago

  @St0ner1995 @AWSSupport When you owe someone $10k, you have a serious problem. When you owe someone $110 billion, they are the one with a serious problem.

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

• 
  Gopal Goti (@gopal_goti) reported 51 minutes ago

  @AWSSupport @AWSSupport Thank you for the update, but 'high volume' cannot justify a support case sitting completely 'Unassigned' for over 4 days for a basic account verification issue. This is not a complex technical issue. it is a backend system error on the AWS verification form.

• 
  Meo Meo (@CastleEL88) reported 51 minutes ago

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

• 
  SwarmOne.ai (@swarmoneai) reported 53 minutes ago

  OpenAI just unveiled Jalapeño - their first custom inference chip with Broadcom. "Substantially better performance per watt." Interesting. But a chip doesn't fix a misconfigured serving stack. Custom silicon with default batching, naive routing, and untuned KV-cache management is still burning money. SwarmOptimizer doesn't care what chip you run. It tunes the deployment layer - batching, caching, routing, concurrency - where most of the waste actually lives. The silicon is one layer. The optimization is another. Now on @awscloud

• 
  Md Jaoyad (@JaoyadCode) reported 54 minutes ago

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

• 
  Gabe Fletcher (@gabefletcher) reported 59 minutes ago

  @marcelocantos @awscloud bro... touch some ******* grass. OF COURSE IT WAS AN ERROR. WHO REALLY THINKS THEY LOOK AT THEIR AWS BILL FOR A TRILLION DOLLARS AND SAYS "OH THATS DEFINITELY REAL" stop. go **** off to some VPS's or some ****.

• 
  Payal (@payal_codes) reported 59 minutes ago

  Day 1 : "How to Scale an App to 10 Million Users on AWS" If I have to design a system for 10 million users, I won't build everything on Day 1 because it will add unnecessary complexity and cost. I'll start simple with one application server and one database. As traffic grows, if the server starts reaching its CPU, memory, or storage limits, I'll first scale vertically by moving to a bigger instance. Once that is not enough, I'll separate the backend and database so both can scale independently. To avoid a single point of failure, I'll deploy the application across multiple Availability Zones and put a Load Balancer in front so if one server or AZ goes down, traffic is automatically routed to healthy servers. As the number of users keeps increasing, I'll make my application stateless by storing sessions in Redis. This allows me to add multiple application servers behind the Load Balancer and scale horizontally. If my database starts getting overloaded with reads, I'll use Redis to cache frequently accessed data and add read replicas to distribute read traffic. For static assets like images, CSS, and JavaScript, I'll store them in Amazon S3 and serve them through CloudFront so requests don't keep hitting my application servers. If traffic suddenly spikes during sales or events, I'll enable Auto Scaling with CloudWatch metrics so AWS automatically adds or removes servers based on demand. As the application becomes larger, I'll split the monolith into microservices. This allows each service, like authentication, payments, or notifications, to scale independently instead of scaling the entire application. If the database becomes the bottleneck, especially for write operations, I'll use sharding or federation depending on the data and business requirements. Finally, when users are spread across the world, I'll deploy the application in multiple AWS Regions to reduce latency and improve availability. My approach is always the same: find the bottleneck, solve that bottleneck, and only introduce more complexity when the current architecture can no longer handle the traffic.