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 (67%)
• Sign in (17%)
• Errors (17%)

Live Outage Map

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

City	Problem Type	Report Time
Boca da Mata	Errors	5 days ago
Township of Evan	Website Down	19 days ago
New York City	Website Down	22 days ago
Ciudad Jardín	Website Down	2 months ago
Kyiv	Sign in	3 months ago
Chennai	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:

• 
  metis (@metis00001) reported 8 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

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 10 minutes ago

  @AWSSupport Live production server is down. Case 178699777500302 (Account Reinstatement) filed with a callback requested — call failed to initiate. Earlier case 178699433100264 still unassigned. Need urgent help, can someone DM me?

• 
  absk (@abskwdkr) reported 11 minutes ago

  My ec2 ssh logs in too slow and lags @AWSSupport

• 
  Piragash Velummylum (@piragash) reported 13 minutes ago

  At @awscloud we call this undifferentiated heavy lifting. @Cometml Opik does the hard work, so you can focus on the customer problems.

• 
  Anjishnu Ganguly (@Anjishnu46) reported 14 minutes ago

  Hey @AWSSupport, Our Case 178452910500907 is still not resolved, and we've been left waiting without any meaningful update. Because of this, we're also unable to apply for AWS Activate, which is directly impacting our business operations and slowing down our workflow. This delay is becoming unacceptable. Please look into this urgently and help resolve it as soon as possible.

• 
  Dhanush N (@Dhanush_Nehru) reported 15 minutes ago

  Opened a support portal ticket on AWS. For a week, I heard nothing. contacted @AWSSupport by direct message and the issue was resolved in a matter of days. Their team still responds to thousands of queries every day. That's how genuine support appears. Thank you AWS!

• 
  kakafa.btc (@kakafa_btc) reported 16 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

• 
  @Randomfrequency@mastodon.social (@randomfrequency) reported 16 minutes ago

  @QuinnyPig @awscloud There is only an A, B, and C zone and never shall we acknowledge the existence of any other ones. // Being part of the problem since 20XX

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

• 
  Corey Quinn (@QuinnyPig) reported 20 minutes ago

  Kinda funny that nobody's even making observations like this about @awscloud, if you want to go a level deeper down the irrelevance well.

• 
  Clem ent (@clement___10) reported 20 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.

• 
  Master of Controversy (@THe0GAmer) reported 23 minutes ago

  @Pirat_Nation Amazon aws outage knocked psn offline for 8 hours while sony pushes an all digital future fans could not launch their purchased games

• 
  Himanshu Singh (@hsnice16) reported 24 minutes ago

  Been using LLMs a lot to write code recently. Sometimes I learn a few new things, and sometimes it just confuses itself and me, maybe because there is no one right way to do things. Recently, while working on a pricing page for a new product we've been developing, a senior team member suggested that it would be better to extract it into a separate codebase and deploy the frontend separately. He would then route it through CloudFront under the same origin to avoid cross-origin issues when transferring credentials. I learned that using `*` for `Access-Control-Allow-Origin` doesn't work for credentialed CORS requests. But before all of this worked, I had extracted the pricing frontend into the same codebase, just in a new folder with the required files, and was trying to deploy it on the same infrastructure the rest of the application was using on @awscloud. It wasn't working because there were some issues between the build output and the CDK synthesis/deployment stages. Eventually, I extracted the code into a completely new repository and deployed it on @vercel.

• 
  Ayush Awasthi (@Ayush_awa) reported 24 minutes ago

  @AWSSupport Its the third day today. The only mail I received from aws was all about “We are getting someone to investigate this” Since then I havent received any update. My only issue is that these things are time sensitive and you cant just take days after days with no real status updates

• 
  Maciej Wilczyński (@wilczynski24) reported 26 minutes ago

  @opsolutehq @awscloud Otherwise, I believe it's not fully viable for full-range products. Example of Lovable: they have hundreds of potential use cases. That's where they are on credit-based systems rather than outcome-based systems, because you can't narrow down the overall cafeteria of use cases.

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 33 minutes ago

  Day 19 of #JobSwitchUntilPlaced 🚀 Today's progress: ✅ Started a new Microservices project by building the User Service ✅ Solved 2 DSA problems ✅ Learned about Blob Storage (Amazon S3) One step closer to building production-ready, scalable backend systems.💪 #BuildInPublic

• 
  Siya (@reze_xqc) reported 36 minutes ago

  @AWSSupport Case 178653274100402 opened 3 days ago, no response. Can't sign in to AWS Builder ID, email locked to unknown sign-in method, blocking access to AWS Academy courses. Need help.

• 
  Adam Peterson (@_adam_here_) reported 36 minutes ago

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

• 
  ShenYubao (@ssybb1988) reported 37 minutes ago

  @AWSSupport @awscloud AWS account suspended for additional verification; Production services down for ~24h. All verification docs submitted. Unable to purchase Business Support+ due to suspension. Please expedite review & help restore production. Case ID: 178678971500932

• 
  Alvaro Villalba (@alvarovillalbap) reported 37 minutes ago

  @philipkung @awscloud @amazon Technical support has being helpful historically for me (with smaller problems than yours) But it did cost us a lot of $$$ for something I feel should be included Did they charge for your technical support?

• 
  Rami (@KingRomstar) reported 41 minutes ago

  @awscloud your multisession login doesn't even work right. I have to logout of one account and into another everytime I want to swap environments.

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

• 
  Adam Peterson (@_adam_here_) reported 44 minutes ago

  is @AWSSupport down?

• 
  Prateek Gupta (@p_valuee) reported 52 minutes ago

  @AWSSupport My entire production is down since 3 days, I believe this is a P1 and should be treated like one @AWSSupport. Please help me with an ETA

• 
  Mohammed Nafees (@mnafees) reported 55 minutes ago

  yo @awscloud seems like a broken cert chain from your side

• 
  Mahadev Vyavahare (@mahadevkv) reported 55 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

• 
  jd42 (@jdonovan42) reported 55 minutes ago

  @DarioCpx Pls recalculate considering the massive clouds the AI revs sit on. Each $1 in AI attaches $1.5-2.5X attached cloud biz and your down to 30-45% of revs. Then as open wgt models gain apply the 100% revenue retention vs. 60% on frontier and look at EBITDA % from frontier is 10-15% max. But nice try ;) No doubt Anthropic and OpenAI both stimulate demand for Amazon AWS. It creates 2x the cloud biz than it does the direct AI biz. So why not count the full picture of things vs just the #'s that fit one narrative.

• 
  Mr Sage (@GreatSage_0x) reported 57 minutes ago

  Custos makes verdicts on AI agent transactions. Problem: it had no memory. Every decision started from zero. Meet Anamnesis — I gave it a memory layer using CockroachDB. Built for the @CockroachDB x @awscloud Hackathon

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

• 
  Indrani Som (@indrani_som2004) reported 1 hour ago

  @AWSSupport please look into this issue