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 (82%)
• Sign in (9%)
• Errors (9%)

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	5 days ago
New York City	Website Down	8 days ago
Ciudad Jardín	Website Down	1 month ago
Kyiv	Sign in	2 months ago
Chennai	Website Down	2 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:

• 
  Silksteele (@silksteele) reported 5 minutes ago

  @adamKDean @awscloud Pshhhh! That's a rounding error against your consulting fees and contract work. I'm surprised you even noticed.

• 
  Jan Jezek (@jbodl) reported 6 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?

• 
  Guilherme Lage (@ItsEasypop) reported 6 minutes ago

  Another OG goes down. I remember people calling Storj the next Amazon S3 back in 2018

• 
  Erin (@erinEncoded) reported 13 minutes ago

  @awscloud This is tone deaf. It wasn’t funny. It was upsetting. It reduced my trust in your systems, testing, and ability to roll back critical errors. I didn’t laugh. Why are you?

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

• 
  Ben Newton ベン (@BenENewton) reported 15 minutes ago

  @awscloud Somewhere there's an IT guy lying on the ground next to his desk after opening the page with this error on it.

• 
  J Bret Edwards (@jbecompslns) reported 16 minutes ago

  did @AWSSupport lay off all the accounts and billing people or are they all just swamped from all those insane billing estimate cases from last week? I don't remember the wait times being this bad when I was still working at AWS a few years ago. It's kind of surreal being on the other side of the fence, knowing exactly what needs to be done to resolve the issue, but then having to wait to get someone to actually look at the case. I think they laid off too many people. This is going to come back to bite them in the medium to long term.

• 
  Joy | 🔥 (@JoyKingdomx) reported 21 minutes ago

  As we all know, cloud outages are not a new topic here. But what is changed is how many products now depend on the same infrastructure. A few years ago, an AWS outage mostly affected AWS customers. Where today one infrastructure issue can ripple across AI apps, APIs, developer tools, streaming platforms and payment services. That is the downside of concentration. We have seen @awscloud outages impact millions. We have also seen @OpenAI outages pause production apps because entire inference pipelines depended on a single provider. It is not the outage that matters - it is the dependency behind it. That is the reason why decentralized compute makes sense. Instead of relying on a single cloud or region, @ionet distributes compute across a global network of GPUs in 138+ countries. No infrastructure is immune to failure, the goal is to ensure one failure does not become everyone's failure.

• 
  M (@mdw864) reported 21 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.

• 
  mail box (@mailbox28564784) reported 22 minutes ago

  @amazonIN @amazon @awscloud I am extremely disappointed with Amazon's customer service. Despite returning the product, I have neither received my ₹1,400 refund nor a replacement. Repeated follow-ups and social media complaints have not resolved my issue.l

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

• 
  Priyanshu (@iproductAI) reported 24 minutes ago

  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.

• 
  GettingMyGlitchOff (@GettingMyGlitch) reported 25 minutes 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 happening more frequently. Emails from mturk-noreply havent worked in a long time so any updates on this situation?

• 
  Onkar Deshpande (@i_am_onkar) reported 26 minutes ago

  @bilal_akh @awscloud what were potential issues? account compromised? keys exposed? last time this happened for me was when some keys got leaked and someone emptied my startup credits -this was 8years ago tho

• 
  Sudeep (@sudee1285) reported 26 minutes ago

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

• 
  Ajith (@iamarulajith) reported 32 minutes ago

  @F1 @awscloud Actually surprised to see the good start by Max. I thought he would bog down again but not this time.

• 
  Jack Stone (@c0XhHxvylL) reported 35 minutes ago

  @stoprocent @AWSSupport when you owe aws 10k that's your problem when its 1 trillion it's their problem

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

• 
  Santhosh (@santhoshv) reported 39 minutes ago

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

• 
  Payal (@payal_codes) reported 45 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.

• 
  metis (@metis00001) reported 47 minutes ago

  I can't understand why AWS has not been able to resolve my issue of payment method. Whatever credit card I put, they are not able to verify it and they keep asking me to call the card issuer. It's not card issuer issue! @awscloud

• 
  Mario Giampieri (@mario_giampieri) reported 47 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.

• 
  RickDavis404 (@RickDavis404) reported 47 minutes ago

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

• 
  IDrabs (@drabs_i) reported 50 minutes ago

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

• 
  Tseng (@TsengSR) reported 55 minutes ago

  @marcelocantos @awscloud I'm 100% certain you'd also crying a river when hard caps are added and the same happens again, because then your services will be shut down immediately until they resolve it and you'll cry too, how they'd dare to take your services offline when reaching the cap due to an error.

• 
  Ironluca (@Ironlucaaa) reported 57 minutes ago

  Heyo again @AWSSupport, thanks for fixing the issue! My bill is only $503 now. That's much better, it's okay now!

• 
  deibeat (@deibeat_13) reported 59 minutes ago

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

• 
  M (@mdw864) reported 59 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.

• 
  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

• 
  Ignacio Cassinelli (@igncass) reported 1 hour ago

  @awscloud What a terrible response