Amazon Web Services 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:

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

• 
  Anjishnu Ganguly (@Anjishnu46) reported 11 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.

• 
  Kailash Tulsi Gajra (@kailashgajara) reported 12 minutes ago

  Is @awscloud down right now? #AWSDownAgain #AwsDown

• 
  🦋Kieran🦋 💻 (@sir_divs_alot) reported 12 minutes ago

  🚨 @AWSSupport I've been unable to create a Kiro subscription for 2+ weeks, getting error"account is not authorized to make this call." I have an active account, valid billing, and correct IAM Identity Center Organization instance setup. Case #178567212700620 escalate urgently.

• 
  Aramis Official (@AramisToken) reported 16 minutes ago

  @NoaSanderskyo7 @F1 @awscloud He was slow af, actually

• 
  SwarmOne.ai (@swarmoneai) reported 17 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

• 
  WPBeginner (@wpbeginner) reported 22 minutes ago

  You built your WordPress site over months (or years). One bad plugin/theme update can wipe it all out overnight. 😱 Plugin conflicts. Malware. A botched migration. A hacked server. The disasters that take down WordPress sites usually happen without warning. And here's the mistake most site owners make: they think their hosting provider's backup is enough. It's NOT. If the server fails, you lose both your site and the backup. We share the complete step-by-step guide for backing up your WordPress site the right way. Here is what you will learn: ✅ Use a Backup Plugin (Best for Most People): @DuplicatorWP is what we use across our sites. Full-site backups, disaster recovery links, and restore without having the plugin pre-installed. Free version available, Pro has scheduled backups. ✅ Use Your Hosting Provider's Backup: SiteGround (where WPBeginner is hosted) includes manual and automated daily backups on all plans. Bluehost partners with CodeGuard and Jetpack for their built-in options. ✅ Manual Backup With cPanel or FTP: Use cPanel's Backup Wizard for a full backup, or connect via FileZilla FTP to download your wp-content, themes, plugins, and wp-config.php files directly. ✅ Send Backups to Cloud Storage: Duplicator and UpdraftPlus both connect natively to Google Drive, Dropbox, OneDrive, and Amazon S3. Never store backups on the same server as your website. If your host fails, both are gone. ✅ Set Up Automatic Scheduled Backups: Configure hourly, daily, weekly, or monthly backups in Duplicator based on how often you publish. eCommerce stores and busy blogs need daily. Slower-moving sites can get away with weekly. Ready to protect years of hard work with a proper WordPress backup system? Read the full ultimate step-by-step guide 👇 (Link is in the thread below)

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

• 
  Prateek Gupta (@p_valuee) reported 25 minutes ago

  AWS suspended my account for billing. I have zero due invoices and zero past-due invoices. Their own Amazon Q agent confirmed it in writing. P1 case 178635853400575, day 3, production still down. @AWSSupport what is the actual reason?

• 
  Guilherme Lage (@ItsEasypop) reported 27 minutes ago

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

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 28 minutes ago

  @jeffdafo @ivanburazin @awscloud Even aspnetcore can run on Linux now - there is no excuse to have (and pay through the nose) for Windows server licenses)

• 
  Aqib Ansari (@Aqib_Ansari_) reported 28 minutes ago

  @AWSSupport Hey @AWSSupport any update on this? 8 Aug 2026: Issue opened 13 Aug 2026: Issue escalated to specialized team 18 Aug 2026: Still being investigated. Its 21 Aug 2026 now still no resolution or substantive update. Nearly 2 weeks for a service-access issue is frustrating experience

• 
  Mr Sage (@GreatSage_0x) reported 29 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

• 
  Siya (@reze_xqc) reported 31 minutes ago

  @AWSSupport @AWSSupport @awscloud Case 178653274100402, 4 days old. Got a copy-paste "noted for awareness" reply, no actual fix. Still locked out of AWS Builder ID, still can't access AWS Academy courses. This is blocking coursework. Fix it.