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 (60%)
• Sign in (20%)
• Errors (20%)

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	9 days ago
Township of Evan	Website Down	24 days ago
New York City	Website Down	27 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:

• 
  Stephen “The Yellow Dart” Schutt (@schuttsm) reported 5 minutes ago

  @QuinnyPig @awscloud I get charged $0.55 every month. Fix that

• 
  Corey Quinn (@QuinnyPig) reported 9 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.

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

• 
  ShenYubao (@ssybb1988) reported 18 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

• 
  Nandkishor (@devops_nk) reported 24 minutes ago

  Infosys DevOps Engineer L2 Round (Offline) My friend got these questions in the L2 interview: 1. What does the top command show in Linux, and what does load average represent? 2. What is the difference between Amazon S3 and EBS? 3. What is Amazon EC2, and can we use a custom OS/image with an EC2 instance? 4. What is the difference between self-managed PostgreSQL and Amazon RDS for PostgreSQL? 5. What are Primary Keys and Foreign Keys, and why are they used? 6. Can S3 data be automatically deleted based on a policy? How do S3 Lifecycle Policies work? 7. How would you install Nginx or Apache on Ubuntu? 8. What is sudo, and why do we use it in Linux? 9. What is the difference between Prometheus and Grafana? 10. How does Prometheus collect/scrape metrics? 11. How do you manage Docker images, containers, and running processes from the CLI? 12. Where is a Bearer Token normally passed in an HTTP request? 13. Do you use any third-party monitoring tools in your production environment? If yes, which one? 14. How would you design a standardized Jenkins pipeline for multiple teams? 15. How would you create reusable Jenkins templates and shared libraries? 16. How would you troubleshoot an intermittently failing Jenkins pipeline? 17. How would you integrate Maven into a CI/CD pipeline? 18. How would you manage builds involving Node.js, Python, or Go? 19. How would you troubleshoot a failed production deployment from Jenkins? 20. How would you investigate a Kubernetes workload with high CPU or memory usage? 21. How would you use cloud monitoring and logs to isolate an infrastructure issue? Save this if you're preparing for a DevOps Engineer interview.

• 
  ErinE (@WhoaNowNelly) reported 24 minutes ago

  @DRiceHockey @WNBA @awscloud Same applies to all their stats. Their PRA is gonna go down too. That's the nature of injuries. Makes it harder for the individual, but does not increase the difficulty of the actual shot itself.

• 
  PolyPup (@PolyPup) reported 25 minutes ago

  I think I have a problem. - 3 @ChatGPT subscriptions - 2 @AnthropicAI subscriptions - $8,200 @awscloud bill coming this month I have so many protocols built, ready for deployment. Really cool innovative, revenue generating projects but I'm hesitant to launch on anything. Maybe someday.

• 
  Jaimin Vaghani (@jaiminvaghani) reported 26 minutes ago

  @AWSSupport @AWSSupport Appreciate the reply, but I've heard this exact message every day this week. At what point does a 5+ day production-down case qualify for actual escalation? Please have an escalation manager or TAM contact me directly, the Support Center loop isn't working.

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

• 
  Grynn-ai-bot (@Grynn) reported 27 minutes ago

  You can ask codex to make a plan to move your fleet from $AMZN (extremely overpriced) or $ORCL OCI to Hetzner or OVH, Vultr, DO etc. Save a ton. In theory this should hurt Amazon AWS margins. A lot. OTOH, I have been wrong about this for years. People keep paying Amazon when there are lower cost options that are so much better in every way except plausible deniability/CYA - no one gets fired for buying IBM kind of thing. @olesovhcom consider publishing a skill / api with a full list of ovh servers and pricing! Let agents decide what and how to repackage apps on bare metal at 1/5th the Amazon price. And fix your billing, so companies can buy.

• 
  Dan Lynch (@danlynch) reported 29 minutes ago

  @QuinnyPig @awscloud I need to sign in with LEGO 😎

• 
  M (@mdw864) reported 31 minutes ago

  @awscloud can you PLEASE answer me? You’ve just turned off my Business because you will not help me. I need you to stop charging me. Do not tell me to login because I do not know the email address that was used to open the account. All I know is my bank account is being charged

• 
  Keith Townsend (@CTOAdvisor) reported 31 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.

• 
  OneTradeWex (@OneTradeWex) reported 34 minutes ago

  $CBRS is trying to challenge $NVDA indirectly, here’s how: While $NVDA focuses on incredibly small and powerful chips, $CBRS has built a massive, highly specialized AI scaling semiconductor. This greatly decreases the amount of cloud tokens needed to process a large language model, effectively saving AI companies millions of dollars in the long run. Think of $NVDA racks as an industrial kitchen and $CBRS chips as a microwave, when all you need to do is cook a hot pocket you want the microwave for efficiency. $CBRS announced that core revenue more than doubled year-over-year to $210 million in its Q2 earnings report while its cloud business nearly quadrupled. The company also raised its 2026 revenue guidance to between $880 million and $890 million. If $CBRS can successfully fulfill their contracts with @OpenAI and @awscloud on time and at scale we will see even more growth, if not them only having two primary customers will be their down fall. Looking at the technical setup we see $CBRS is coming down into its months long support channel. If it holds the $180-$160 level I see no reason for it not to bounce back to $215 to $230.

• 
  Luke Skywalker (@LSF4Life1981) reported 35 minutes ago

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

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

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

• 
  krrawn (@krrawn) reported 39 minutes ago

  I was wondering why @awscloud support was slow the other day

• 
  Vinit Upadhyay (@vinitcodes) reported 39 minutes ago

  @kirodotdev @awscloud @AWSSupport issues still persist i didn't got any update

• 
  GIrls In Technology! (@francescaViking) reported 40 minutes ago

  @awscloud @amazonmturk are shuttering services barely months after announcing maintenance mode, giving barely a month now and leaving requesters and workers in the lurch. Amazon demonstrates again why it's terrible for businesses and users.

• 
  Jeremiah "SMEEgle" Castillo (@jcastillo4tx) reported 41 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?

• 
  Haresh Kukkreja (@HandbrakeHarry) reported 42 minutes ago

  @amazonIN @awscloud Your app seems to be down. Unable to contact Customer Support

• 
  Shobhit Shrivastava (@shri_shobhit) reported 42 minutes ago

  @adamr_1776 I left Amazon AWS around 2019. From what I recall it was something like issues dot Amazon dot com

• 
  Arian van Putten (@ProgrammerDude) reported 46 minutes ago

  @QuinnyPig @awscloud Are they gonna fix not being able to have to accounts logged in in two different tabs?

• 
  Alvaro Villalba (@alvarovillalbap) reported 48 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?

• 
  Siddartha DevOps (@SiddarthaDevops) reported 49 minutes ago

  @AWSSupport link is not working

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 53 minutes ago

  ClarityCheck markets itself as a tool to detect catfishing. To verify identities. To keep you safe from liars online. Here's how it works. You upload someone's photo. ClarityCheck runs it through their reverse image search. Finds their dating profile. Their social media. Wherever that face appears. Seems solid. Except ClarityCheck just leaked 9 million photos sitting in an unsecured Amazon S3 bucket. 450 gigabytes of faces. Stored in folders labeled "faces" and "profiles." The photos came from people uploading images of strangers. Dating app screenshots. Private social accounts. Scanned prints. Photos of children. Most of these people never uploaded anything to ClarityCheck. They just got identified by someone else trying to figure out who they were. Then their face got indexed. Stored. And left wide open. For several months. The URL to access it was embedded in ClarityCheck's own website source code. The company's response: this was "temporary storage" and an "ordinary member of the public" would not have found it. An ordinary member of the public with the URL from their own website. Which is not temporary storage. That's just a server. And it wasn't invisible. You'd need 30 seconds and a basic understanding of how websites work. Now ClarityCheck says the data is "secured." A service built to prevent identity fraud just exposed millions of identities. The tool designed to catch people lying about who they are just showed everyone's actual face to anyone listening. The irony isn't subtle. It's a design flaw pretending to be an accident.

• 
  Vinit Upadhyay (@vinitcodes) reported 54 minutes ago

  @AWSSupport @kirodotdev @awscloud I’ve already raised a case explaining the entire issue. Case ID: 178664512400070. Unfortunately, I still haven’t received any genuine help, which is really disappointing. I’m not the only one facing this issue-many others are experiencing the same problem. Please look into this.

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

• 
  Jonny Castles (@jonny_castles) reported 57 minutes ago

  Not seeing much on here, but seems like a massive outage across platforms? Looks like all AWS linked? @awscloud

• 
  Ümit Kaan Usta (@umitkaanusta) reported 59 minutes ago

  @AWSSupport I keep getting errors across the AWS Console where components or resource lists fail to load, showing messages like “An error occurred calling the API: describeAddresses.” Reloading sometimes fixes it temporarily. can you help? It's mostly on EC2 related stuff. us-east-1