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 (71%)
• Sign in (14%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Sign in	8 days ago
Pottstown	Website Down	13 days ago
Iztacalco	Website Down	16 days ago
Boca da Mata	Errors	28 days ago
Township of Evan	Website Down	1 month ago
New York City	Website Down	2 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:

• 
  Webdesign29 Création de sites internet Brest⛓️🕸️ (@Webdesign29B) reported 3 minutes ago

  @AWSSupport I tried every possible combination to get phone support. I think it either just doesn't exist or it is down. Someone did get back to me in chat in another ticket tho.

• 
  WPBeginner (@wpbeginner) reported 6 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)

• 
  Harikrishna KP (@harikp2002) reported 6 minutes ago

  @AWSSupport Two days into migrating to AWS and both new accounts I created are locked out of every single service. S3, EC2, Lambda, DynamoDB, all of it. The accounts show as ACTIVE. Support confirmed it needs a manual fix from an internal team, then went quiet for 28 hours. Three open cases, one phone call, still completely blocked. Sitting on AWS credits I literally cannot spend. Do better please!

• 
  Joy | 🔥 (@JoyKingdomx) reported 9 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.

• 
  Jonny Castles (@jonny_castles) reported 10 minutes ago

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

• 
  Pixi Dust (@Bethco2257) reported 11 minutes ago

  @FmrRepMTG @amazon @awscloud walk into any Amazon office building at Seattle HQ and South Lake Union Amazon Seattle offices and instantly you can see with your own eyes… nearly 80% of staff are HB1 visa holders!!!! So yes, we have a big problem.

• 
  Jared Cassidy (@depach) reported 13 minutes ago

  @grhmc @QuinnyPig @awscloud Not fixed on mine I login every day 🥲 did you have to set anything?

• 
  Jaimin Vaghani (@jaiminvaghani) reported 13 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.

• 
  absk (@abskwdkr) reported 14 minutes ago

  My ec2 ssh logs in too slow and lags @AWSSupport

• 
  Sai Manikanta ☕ (@rebuiltWithSai) reported 14 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

• 
  Omni (@omnishredder_) reported 15 minutes ago

  @AmazonUK @Twitch @awscloud sort yo ****, I'm getting tired of ironically the last two days unable to watch twitch without lag or buffering at random with no explanation, it's almost like the ******* AI training is the problem that nobody wanted! How about ******* remove it!

• 
  The Mediocre Inquisitor (@MediocreInqv2) reported 15 minutes ago

  @OpenAIDevs @awscloud I’m trying to buy a ChatGPT account on my work email and it’s not allowing me to. Will you be able to fix these issues? M trying to pay you

• 
  TeeBeeCTO (@TeeBeeCTO) reported 17 minutes ago

  Setting up a new AWS account @awscloud … and get non stop errors on set up. Looks like their vibe coding dystopia worked… were all going to die because SkyNet will have error pages that end up giving us all death by error page. Amazing work… @JeffBezos !!

• 
  Brian Porter (@kbporter) reported 19 minutes ago

  @amazon @awscloud @AmazonHelp why do I have to continually contact you on social media for issues with your service? Why is your customer service online “help” so bad? $5 credits for delayed orders for a service we pay for is horrible!

• 
  Hagop Chemedikian (@hagop17) reported 23 minutes ago

  @AWSSupport Account blocked — "not recognized as a valid account." Console login works, all resource creation fails. 10+ year old account, dormant for years, just resumed for a personal project. Three cases open, no response. Can someone look?

• 
  Matthew Joughin | 🏗️ Cross Platform Dev Tools (@mrwcjoughin) reported 24 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)

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

  @meaningoflights @jpschroeder @awscloud what issue do you have with that?

• 
  Himanshu Singh (@hsnice16) reported 27 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.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 28 minutes ago

  @Cloudflare @awscloud Fix human verification

• 
  Ivan Toma (@FounderRAVERK) reported 28 minutes ago

  @awscloud @Google @Microsoft The water problem is only going to get bigger. We already have technology that can help data centers produce their own cooling water from the sea. Let’s solve this together.

• 
  Matthew (@OneShotCaller) reported 29 minutes ago

  @ZZiata15569 @awscloud I have billing and budget alerts set up with AWS already. Main problem with a lot of tools I’ve used is too much noise in the alerts vs AWS option. Still, I think every AWS customer gets at least 1 surprise lol… part of initiation (onboarding?)

• 
  Priyanshu (@iproductAI) reported 34 minutes ago

  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.

• 
  Ranbir Mahapatra (@ranbirnxt) reported 38 minutes ago

  @QuinnyPig @awscloud Is NAT Gateway a ‘pricing’ bug that you would care to fix? Forever?

• 
  Synapse Brief (@Synapse_Brief) reported 40 minutes ago

  @yugacohler @awscloud @CoinbaseDev The post frames this as a new capability, but Amazon already gave agents the ability to make purchases in December 2025. The Coinbase integration is the expansion, not the invention. The real bottleneck was never payment rails. It's authentication and authorization at scale. How does an agent prove it's authorized to spend, and how do you prevent a single compromised agent from draining a wallet? Coinbase's infrastructure solves the custody and settlement problem. AWS solves the identity and access management layer. The combination is what makes this production-ready. The "AI agents will outnumber humans" framing is hype. The real driver is that agents need to pay for API calls, data feeds, and compute resources autonomously. That's a practical requirement, not a sci-fi scenario. Stripe being involved is the quiet signal here. They handle the merchant side of the equation. Agents paying for things requires both the payer and the payee infrastructure. The managed aspect matters more than the payments themselves. AWS handles the compliance, KYC, and fraud detection layers that would otherwise be a nightmare to build. That's the real value proposition.

• 
  Haresh Kukkreja (@HandbrakeHarry) reported 41 minutes ago

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

• 
  Sumedh More (@DroidBoyJr) reported 42 minutes ago

  Hey @awscloud @AWSSupport im trying Bedrock with root user and getting NOT_AUTHORISED error with 400. Tried support and the ai assistant couldn't find anything. Tried raising ticket, it asked me to upgrade support plan. Plan upgrade failing with error. Going nowhere #SOS

• 
  Brandon S (@BSaarX) reported 43 minutes ago

  @Gabby_Hoffman @awscloud Next you will say let them eat cake. 2024 was about mortgage rates getting lower and affordability. Now we see it was about crypto, AI and pushing data centers. What a let down

• 
  Harun R. (@harundotdev) reported 45 minutes ago

  2. The obvious fix: split responsibility. Metadata stays in a database like Postgres. The actual file goes to object storage, Amazon S3 being the standard example. Better. Still not the full fix.

• 
  EJ Campbell (@ejc3) reported 50 minutes ago

  @awscloud why? > Error: updating SSM Parameter (/github-runner/user-data): ValidationException: The specified parameter value is too large. Advanced-tier parameters support a maximum parameter value of 8192 characters.

• 
  ゆーー𓂀🦊京のそちこち(暑いので液化した🫠) (@Hikari_644) reported 1 hour ago

  @ishanxtwt Simply DNS server problem never take down an entire website. Except, like amazon AWS, are using domain and dynamic name resolve to working correctly between multiple servers and services.