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 (63%)
• Sign in (19%)
• Errors (19%)

Live Outage Map

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

City	Problem Type	Report Time
Ciudad Jardín	Website Down	2 days ago
Kyiv	Sign in	1 month ago
Chennai	Website Down	1 month ago
Point Pleasant Beach	Website Down	2 months ago
Little Rock	Errors	2 months ago
Atlanta	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:

• 
  ThriveCart (@ThriveCart) reported 4 minutes ago

  @EssixGalaxy Hello, Amazon AWS has triggered an unscheduled update, likely mitigating a wider issue on their end. This is impacting some carts. We expect AWS to resolve very shortly. We will provide an update when it does.

• 
  chaturfier (@chaturfier) reported 8 minutes ago

  @AWSSupport Production AWS SES account paused over a resolved credential scrape. Keys rotated, issues fixed. Case 178014826500654 unread for over 48 hours while business halts. Help?

• 
  Ann O'Leary 🙄🤬 (@Panda6) reported 13 minutes ago

  @goodreads Hi - honest question - why is your site so very slow to load?? Can’t you get some @awscloud juice behind it??

• 
  🇺🇸 End H1B F1 OPT TN E3 O1 L1 I1 H4 all NIV 🇺🇸 (@slmimorgan) reported 14 minutes ago

  @IAGovernor @awscloud @Cognizant You need to stop down you treasonous monster. You are elected to serve we the American people. Not Cognizant or Indians. Shame on you.

• 
  ProAmPete (@ProAmPete1) reported 19 minutes ago

  @AWSSupport @DiegooUA_ I am having the exact same issue, except support has inexplicably left my tickets in unassigned status for 3 months. I verified my identity and they in turn suspended and threatened to delete my account, and never even gave me the call I requested MULTIPLE times.

• 
  Rudra Narayan Mohapatra (@rnmohapatra46) reported 19 minutes ago

  @awscloud Hi, I took the AWS Certified Solutions Architect – Associate exam about 3–4 weeks ago, but my digital badge is still not showing up on Credly. Could you please help me resolve this issue? Thanks in advance.

• 
  Rohan Jeruel (@JeruelSingh) reported 21 minutes ago

  @AWSSupport @AWS Our AWS account has been suspended for 48+ hours. Production SaaS platform serving enterprise clients is down. Support case open but UNASSIGNED. We need a human at AWS Trust & Safety or Account Reinstatement to look at this TODAY. #AWS #AWSSupport

• 
  Miguel A. Vega Segovia (@mavegasegovia) reported 21 minutes ago

  @AWSSupport @AWS URGENT: my AWS account 268140507056 has been WRONGFULLY SUSPENDED for ~48h — AFTER paying my invoice IN FULL (balance $0.00). My 100% digital business is completely DOWN, losing customers by the hour. 🧵

• 
  Catdingo (@CattManii) reported 24 minutes ago

  @awscloud Is that after or way after losing millions of dollars due to uptime issues?

• 
  Prince Raj (@theprinceraj) reported 29 minutes ago

  @vansh22b @awscloud @AWSCloudIndia Contact them through support email. Explain to them your problem and that you cannot afford to pay this bill. They often waive off the bill when you leave a VPS or paid service running mistakenly

• 
  Arindam Sarkar (@asoptionsell) reported 29 minutes ago

  @awscloud AWS not giving me 1 year free server to run models.

• 
  esyx (@esyx0) reported 31 minutes ago

  Today i got email from AWS that they can't approve my request for **** SES no explanation at all, only generic "During our evaluation, we identified some concerns that prevent us from approving your request. Due to security reasons, we are unable to provide specific details about our assessment criteria." has anyone had to deal with this? All i wanna use the SES for is transactional mails like verification, reset, notifications about your account etc @awscloud @AWSSupport Can you please help? At least tell me what's wrong so i can fix it, i genuinely have no idea

• 
  praveen A (@praveen_hacker) reported 34 minutes ago

  @AWSSupport @AWSSupport Hello AWSSupport, The issue has not yet been resolved. Could you please assist in resolving it as soon as possible?

• 
  Vijay Tupakula (@vijaytupakula) reported 34 minutes ago

  @Ed_13057 @awscloud it wasn't a problem for me, they accepted with in a few hours.

• 
  Tiffa (@TiffaJessi) reported 34 minutes ago

  Yo @awscloud u guys should totally idk maybe fix servers with @PlayApex because they’re TERRIBLE!!!!!!

• 
  Toby Cummings (@Omek) reported 37 minutes ago

  @CompeteTFT @awscloud Uhhh we still can't save picks. It gives me an error every time.

• 
  Tanner Scadden (@TannerSDev) reported 37 minutes ago

  @awscloud please help us asap your team suspended our account at the same time we got an email saying we have two weeks to address a problem with our root account. Cloudflare is down for us, and EC2 won't provision new instances. Our app is down. We serve hospitals. Please

• 
  Bryce Crawford 🐱 (@bryce_meow) reported 38 minutes ago

  Have @awscloud service problem Contact AWS support "This response was generated using generative AI. You may need to verify responses." * Hallucinates * * Obvious mathematical error * Peak comedy

• 
  Corey Quinn (@QuinnyPig) reported 42 minutes ago

  @AWSSupport @M0hkaif That’s not a great response. A. That place is a ghost town. B. Why not just suggest to the user that that’s expected behavior if they selected a multi-AZ cluster? It solves their problem right off.

• 
  Charu (@Charu_Sethi) reported 45 minutes ago

  This week the same problem showed up in two places that don't talk to each other: Coinbase wrapping AI trading agents in an SEC-registered advisory, and x402 charging AI agents per request at the AWS edge. Both are solving authorisation-within-limits. Neither is interoperable with the other. Step back and the pattern is clear. Agentic settlement is becoming table stakes. x402 now runs through AWS CloudFront and WAF, settling USDC on Base and Solana via EIP-3009 in around 200ms, with 169M-plus cumulative payments. Mastercard's Agent Pay for Machines handles multi-rail M2M settlement. Coinbase is putting agent execution inside a registered wrapper. The rails are getting solved. What is not getting solved is the layer above them: a portable, revocable spending mandate that binds an agent's authorisation to a verifiable human or corporate entity and travels across rails. ERC-8004 gives agents identity and reputation, not spending authority. The agent-authorisation drafts (ERC-8118, 8184, 8150) are all single-principal or payment-channel scoped, and none has advanced. An agent authorised inside Coinbase's advisory and an agent paying through x402 at the AWS edge are governed by completely separate, non-portable models. That's the gap. The structural question worth testing: do the platforms each standardise their own proprietary mandate model, leaving on-chain rails competing inside someone else's walled authorisation garden, or does a neutral cross-rail mandate primitive finally emerge? Whoever ships the portable mandate owns the layer everyone else has to build against. @coinbase @awscloud @Mastercard #AgenticPayments #x402

• 
  Pranjal Agrawal (@agrawalpranjal7) reported 45 minutes ago

  @AWSSupport I am still waiting for an update from AWS, as it has been 13 days since I raised the issue, and it remains unassigned.

• 
  SpiritualTRADER (@Spiritual_Trad) reported 47 minutes ago

  @uditdwivedi079 @awscloud @AWSCloudIndia Because internet can be a problem. Once on cloud you don’t have to worry about it.

• 
  Peyton Nowlin (@Peyton_Nowlin) reported 47 minutes ago

  @Tech_Over_Lord @awscloud You are the problem so blindly anti AI you do not even understand the reference

• 
  DIWhyCoder - ⌨️ 🇺🇸 (@diwhycoder) reported 48 minutes ago

  @awscloud AWS running out of server space confirmed.

• 
  Exodys (@711intern) reported 53 minutes ago

  /var/log/deoxys entry_019 / entry_020 (Weekend Edition) 1. Bug Hunting on a VDP > finished subdomain enumeration. > performed initial nuclei scan on the list, found some interesting things like CORS and subdomain takeover. > Used subzy tool to check for subdomain takeover, but all of those dangling subdomains pointed to amazon AWS elb so it was a dead end. > Also they fixed the CORS issue. > Started JS recon

• 
  chaturfier (@chaturfier) reported 54 minutes ago

  @AWSSupport Correct: it's been just over 48 hours since the start of the issue.

• 
  Crypto Pulse (@x1cryptopulse) reported 54 minutes ago

  @awscloud @OpenAI Context retention across multi-step agent workflows is where the real scaling issues show up. 🤖

• 
  Hot_Tamales (@tama96420497) reported 54 minutes ago

  @IAGovernor @awscloud @Cognizant Terrible optics. Read the room.

• 
  S_A.A | WordPress Developer | Ai (@saafolabi_me) reported 59 minutes ago

  The 3-2-1 backup rule, applied to web hosting: 3 COPIES of your data 2 DIFFERENT storage types 1 OFFSITE location What this looks like in practice: Copy 1: Daily cPanel/WHM backup → stored on server Copy 2: Weekly backup → synced to Amazon S3 or Backblaze B2 Copy 3: Monthly snapshot → downloaded locally to your own machine Storage type 1: Server disk Storage type 2: Object storage (S3/B2) Offsite: S3 and your local machine are not on the same server The part almost nobody does: → RESTORING a backup to verify it works An untested backup is not a backup. It's an assumption. Once a month: → Pick a client site → Restore yesterday's backup to a staging environment → Confirm the site loads and the database is intact → Document the restore time If you've never done this, the first time you need it is not the time to find out it doesn't work. When did you last successfully restore from a backup?

• 
  Jay (@jaycansea) reported 1 hour ago

  @awscloud It slows everything down and is a disaster so far.