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 (80%)
• Errors (20%)

Live Outage Map

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

City	Problem Type	Report Time
Iztacalco	Website Down	1 day ago
Boca da Mata	Errors	13 days ago
Township of Evan	Website Down	27 days ago
New York City	Website Down	1 month ago
Ciudad Jardín	Website Down	2 months ago
Kyiv	Sign in	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:

• 
  Adam 🤗 (@AdamMolnarHF) reported 14 minutes ago

  @cgeorgiaw @AnthropicAI @awscloud ooh, I've actually been working on an autoresearch space for a different problem (math) using Kimi k3 + inference providers, I could try forking and seeing if I can reshape the structure around this with this data + build it fully in the open!

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

  @AWSSupport There is no way to get a call back I have tried many different ways. And it always show's this issue

• 
  Prateek Gupta (@p_valuee) reported 18 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?

• 
  @Randomfrequency@mastodon.social (@randomfrequency) reported 19 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

• 
  Jaimin Vaghani (@jaiminvaghani) reported 21 minutes ago

  @AWSSupport @AWSSupport Day 6. Production down. Same templated reply on Twitter, in the case, everywhere. If a multi-day production outage doesn't qualify for real escalation, what does? Asking someone with authority to review Case 178738643800497 and respond with an actual ETA.

• 
  Mon (@mon73x) reported 21 minutes ago

  @asimrazax @AWSSupport I have the same problem. Did you fix it?

• 
  Swaroop Hegde (@SwaroopH) reported 23 minutes ago

  TIL: @awscloud has been racking up ipv4 charges on an old test instance of mine even though it uses dynamic IP. Just checked that their launch wizard deployed new instances with the same issue without warning 🤷

• 
  BOB-DO-THEM (@osangesua) reported 24 minutes ago

  This is a blatant lie intended to mislead the electorate. The glitch synchronisation in the BVAS is the reason he won't effect the upgrade because if an upgrade is carried on the BVAS, the entire calibration of glitches will disappear and the fear that @awscloud may have disabled or blocked the application that allows them to manipulate the BVAS is the reason for this unprovoked lies

• 
  Weird Things (@weird747) reported 26 minutes ago

  @AWSSupport I submitted all the required verification documents for my suspended AWS account as requested. I was told I would receive a response within 24 hours, but it has now been more than 48 hours with no update or resolution. Please review my case and help restore access to my account as soon as possible. I can provide any additional information if required. My website server down from last 3 days no response by aws support tried contacting everywhere .

• 
  Brian Porter (@kbporter) reported 27 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!

• 
  Siddartha DevOps (@SiddarthaDevops) reported 32 minutes ago

  @AWSSupport link is not working

• 
  Matthew (@OneShotCaller) reported 33 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?)

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

• 
  Hagop Chemedikian (@hagop17) reported 35 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?

• 
  banhchung (@banhchugxanh) reported 35 minutes ago

  @POTATOCHEAPGAM1 @trythreews @awscloud i'm so down for cloud gaming, but 5gb internet feels like a stretch

• 
  Kenton Parton (@kenton_parton) reported 36 minutes ago

  Anyone here work on AgentCore Gateway Targets at @awscloud? Been testing them for our MCP/agent platform. I like that it removes the credential leakage issue during development of new MCP's/Agents. But they’re slow AF!🐢 I’m seeing ~430ms added per request above baseline, in-region, with warm caches. Is that expected?

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

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

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

• 
  Gopal Goti (@gopal_goti) reported 41 minutes ago

  @AWSSupport @AWSSupport Thank you for the update, but 'high volume' cannot justify a support case sitting completely 'Unassigned' for over 4 days for a basic account verification issue. This is not a complex technical issue. it is a backend system error on the AWS verification form.

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

  @QuinnyPig @awscloud Are they gonna fix that IAM identity center stored passkeys on a domain that is shared between aws orgs and accounts so I keep locking myself out of orgs when updating one?

• 
  Corey Quinn (@QuinnyPig) reported 43 minutes ago

  I’m going to get a job at @awscloud, immediately fix one bug, then resign. Which bug should it be?

• 
  MrWho (@Mrwho23) reported 47 minutes ago

  @AWSSupport I create a case for your support and till now waiting for the reply My whole system and company is waiting for your support, but you are so slow

• 
  Ümit Kaan Usta (@umitkaanusta) reported 50 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

• 
  Chris (@Mcatbeast) reported 51 minutes ago

  @awscloud has to have the worst sign-in page EVER. Every time I try to login as an IAM user it’s a complete headache and takes 30 minutes to figure out

• 
  Vera ¤⩊¤ (@VeraSimila) reported 53 minutes ago

  @awscloud L+ Ratio Fix Twitch please, nobody wants AI hype beast corpo speak

• 
  Chaz Wargnier ♨️ (@DataChaz) reported 53 minutes ago

  Let's take @Snowflake as an example. Working there gave me a clear view of the data problems hiding behind most ambitious AI roadmaps. Because Snowflake is natively deployed on AWS and available through the AWS Marketplace, it fits right into a modern stack. If you are building an AI feature, a sensible pattern looks like this: > Isolated customer events land securely in Amazon S3 from day one > Snowflake transforms raw data into a governed, usable layer > Flexible Amazon ECS compute routes only approved context to Amazon Bedrock Getting this pipeline right early means less time fixing data leaks and more time shipping AI features ↓

• 
  Synapse Brief (@Synapse_Brief) reported 58 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.

• 
  ❤️‍🔥ViBe GuY_PrinCe😉 (@777PrinceFreaky) reported 58 minutes ago

  Amazon has very poor service in Warranty and Claim Procedure To Customer fix this for me soon @amazonIN @awscloud @AmazonHelp

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

• 
  Rami (@KingRomstar) reported 1 hour 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.