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.

• Errors (36%)
• Website Down (36%)
• Sign in (28%)

Live Outage Map

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

City	Problem Type	Report Time
Rostock	Website Down	1 day ago
Glendale	Website Down	13 days ago
Oakland	Sign in	14 days ago
Greater Noida	Errors	15 days ago
Alamogordo	Website Down	19 days ago
San Francisco	Website Down	21 days 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:

• 
  Ankur Agrahari (@agrahariankur21) reported 21 seconds ago

  @AWSSupport Yes it's really really frustrating as my 15+ clients website applications and all the mobile apps are not working since 12 hours and 500+ employees salaries were not disbursed due to this issue, but no instant help from your service team. Case Id sent privately.

• 
  Trevor Skinner (@PrometheusAIsec) reported 53 seconds ago

  I’m getting real tired of watching this industry pretend dependency is innovation. The entire tech world got sold on the idea that hardware was the problem and cloud was the solution. And to be fair, Amazon AWS played it perfectly. From a business standpoint, it was brilliant. Make infrastructure easy. Make it scalable. Make it fast. Make it cheaper to start. Then make it harder and harder to leave. That’s the part nobody wants to talk about. At first, cloud feels like freedom. No racks. No servers. No switches. No up-front hardware cost. No late nights swapping drives, troubleshooting power, rebuilding arrays, or fighting broken infrastructure. But over time, that freedom can turn into a leash. I’ve seen enough real-world systems to know the difference between convenience and control. Access control, networking, servers, security hardware, firewalls, cameras, panels, credentials, cloud dashboards, hosted platforms, vendor portals — it all looks great until the business depends on something it does not actually own. That is where the trap starts. One vendor controls the platform. One vendor controls the pricing. One vendor controls the updates. One vendor controls the outage window. One vendor controls the rules. One vendor controls the ecosystem. Then businesses slowly build everything around it. Compute, storage, databases, backups, monitoring, identity, deployment, physical security, access control, video, alerts, compliance, logging, and billing. By the time they realize how deep they are, leaving is no longer a simple decision. It becomes a migration project. A budget problem. A staffing problem. A security concern. A downtime risk. A business risk. That is not just convenience. That is a dependency loop. And what frustrates me the most is that the same industry that used to understand real infrastructure now acts like ownership is outdated. Owning hardware is not outdated. Understanding networks is not outdated. Knowing servers is not outdated. Knowing how systems work underneath the dashboard is not outdated. Building hybrid infrastructure is not outdated. It is control. Cloud has its place. Hosted systems have their place. Managed platforms have their place. I am not against any of that. I am against companies blindly giving up ownership, knowledge, and leverage, then calling it progress. Because when your entire business depends on someone else’s platform, someone else’s pricing, someone else’s rules, someone else’s uptime, and someone else’s permission, you do not own your technology. You rent permission to operate. Prometheus V2 is built different by RocketCore.

• 
  Sociaall Inc. (@dez_blanchfield) reported 3 minutes ago

  over three hours, and @AWSSupport are still asleep at the wheel while their platform is down - mind bloggling..

• 
  Steve (@somatg3) reported 5 minutes ago

  @danorlovsky7 @awscloud @NextGenStats Easy. Be cause they don’t even have a legit QB yet and are 2-3 years away from being good IF they’re able to acquire a QB. They need EVERYTHING. Spending #3 for a RB on a bad team isn’t a winning draft strategy. Trade down or take the best edge rusher remaining.

• 
  Mf91 (@Mf9166921324) reported 6 minutes ago

  @awscloud @thomsonreuters Is there any outage on kinesis services around 15.10 UTC in eu central 1?

• 
  POWER magazine (@POWERmagazine) reported 12 minutes ago

  4/5 The good news: the same AI finding vulnerabilities can also help fix them. @awscloud reports a 50x improvement in security log analysis. AI models are now generating viable patches. And Project Glasswing will publish practical security recommendations within 90 days.

• 
  Dr. Srikanth Sundararajan (Doc) (@SundarSrik) reported 17 minutes ago

  @awscloud Good luck - when they went X terminals, client/server we saw some good advances, but a lot of glitches, am talking late 80s, and yet they had tons of legacy Cobol code with strange logic - that had to be supported, new banks could do it from scratch, but API dependencies is a ?

• 
  Siddhant Tripathi (@siddhantio) reported 20 minutes ago

  @awscloud opened a case over 10 days ago and it’s still unassigned to any agent. Please help in resolving the billing issue.

• 
  Ronny A. (@DjTimbao) reported 20 minutes ago

  @AWSSupport The issue is that the team is NOT responding via the case. It’s been 3 days for this one and 8 days for the previous one. I am totally blocked. Can you at least escalate Case ID 177654556500245 to the Billing and account team? 'Working via the case' is currently impossible Thanks

• 
  Vijay Swami (@vjswami) reported 22 minutes ago

  In an Agentic AI sales cycle, you need to intimately understand current customer workflows before you can even think about agents. This concept of deeply understanding the problem before "solution'ing" was something drilled into our heads at @awscloud in the early days. Prior to the current tools, this involved lots of back/forth with a customer, then having to put together a working document in the shape of the workflow for that particular customer and/or department. Time consuming and error prone. Today? Another day, another @AnthropicAI @claudeai Claude Code skill developed to speed this along: /workflowdiscovery It can take in multiple types of unstructured data (emails, docs, images, etc) and then turn them into a nice living document that maps the workflows, stakeholders, inputs/outputs, artifacts and more... in minutes. This is then automatically hosted on an internal website and the sales team gets a link they can use to go back to the customer and live edit the doc Q&A, validate assumptions, etc to lock this down. And then this can feed right into the solutions/engineering team with a simple JSON export into their workflows for agent mapping. Below is the skill information on the left, and sample output on the right. These are the types of tools and workflows which are mandatory for sales teams in 2026+.

• 
  aem (@aemukit) reported 25 minutes ago

  I guess @awscloud is down and that's why everything is down.

• 
  ELECTROCARDS (@ELECTROCARDS) reported 28 minutes ago

  @awscloud i am from Pakistan i need your help for Amazon account opening issue.

• 
  Marci (@Nma_ci) reported 29 minutes ago

  @AWSSupport We are currently having an issue on our Production on AWS because a required quota is not being approved. This same quota was approved in our Test Environment on AWS. Support Ticket keeps getting closed. caseID: 177753893100221

• 
  OdysseasPapadmitriou (@odyhub) reported 30 minutes ago

  @AWSSupport - Redis issues on Virginia US-East1 - why are your updates so incomplete?

• 
  The Returns Report (@ReturnsReport) reported 32 minutes ago

  $GOOGL Why everyone's losing their minds over this number: Google Cloud is the part of Google that competes with Amazon AWS and Microsoft Azure. Last quarter: grew 48% This quarter: grew 63% Cloud businesses don't usually accelerate this fast. They mature, slow down, and stabilize. Google just did the opposite. At $20B per quarter, this is the fastest-growing big cloud business in the world right now.

• 
  Adrian | The Web Scraping Guy (@adrian_horning_) reported 32 minutes ago

  @romaindewolff @awscloud Did you end up paying for it? If so, I would def switch if you have been a loyal customer and had one spike? Absolutely they should’ve taken the price down some

• 
  Manik Sharma (@manikgem37) reported 33 minutes ago

  @AWS @awscloud @amazonIN Hi, I am not able to use Marketplace models on Amazon bedrock even after having Activate Founders credit and payment methods added. Getting the 'Invalid_payment_instrument' error. Raised case too. Here is the latest one id 177678551600643. Please help!

• 
  Mark Kappel (@DTLB58) reported 37 minutes ago

  @danorlovsky7 @NextGenStats @awscloud RB Depth chart: Tyler Allgier, James Conner, Trey Benson and Bam Knight. And you want them to draft Love? ?!?! What a terrible resource of player personnel! Is Love probably better than all of them? Sure. But then why the heck did you structure your offseason like this?!?!

• 
  Kaspa Mode: ON (@KasConviction) reported 38 minutes ago

  @cryptorover Ethereum is not even fully decentralized. No PoS can be with much of the node control on Amazon AWS. ETH is slow, expensive, and not fully decentralized.

• 
  Ashish Pawar (@Ashish_Pawa_22) reported 40 minutes ago

  @AWSSupport @AWSSupport Prioritized but still no call after 74 hours. Documents already sent. Need phone verification NOW. My business is down. Call +91-8275976388 immediately.

• 
  Shatakshi (@true_amateur) reported 42 minutes ago

  If we can point out mistakes we should call out the good work too. I forgot to appreciate the help from @awscloud .Because I tweeted here & raised an issue the service charges were waived off. Sampath if you see this Thank you for the help 🙏

• 
  Pacific Card Exchange (@pactcg) reported 42 minutes ago

  @AWSSupport Yes. Have a case up online but cannot get in contact with anyone. Still dealing with my site down for the past 2 days w/o any notification from AWS.

• 
  Dave L 💜🛡️ (@BajaDavidlak) reported 43 minutes ago

  @Harryhwrqx @chainlink @awscloud and price goes down

• 
  Execute (@0xExecute) reported 43 minutes ago

  @awscloud Hotter take I’ve been getting charged $280 a month for a open intense I can’t shut down or find to shut down with ZeRO support from aws with my ticket that’s been open for three months and counting!

• 
  Fôrtûne (@Fortune71227524) reported 47 minutes ago

  @AWSSupport It is not a service quota issue. I currently have 8 for the "all G and VT on-demand instances". That should launch 2 G5s. I hardly launch one without the 'insufficient capacity in this region'. Launching two successfully is a miracle. Y'all need to add more G5s in London.

• 
  None (@BourDeniz) reported 49 minutes ago

  @AWSSupport 50+ hours, still unassigned. Production has been down since Saturday. Please escalate.

• 
  Ødoworitse | DevOps Factory (@ceO_Odox) reported 52 minutes ago

  Every DevOps engineer knows "It works on my machine" is a lie. Hit a wall today deploying to @awscloud EC2—*** was begging for a password in a headless shell. ​Error: fatal: could not read Username. Reality: The source URL drifted, and the automation had no keyboard to answer. 🧵

• 
  CodieEditor (@CodieEditor) reported 55 minutes ago

  @AWSSupport @AWSSupport Still, there is no fix for this billing. We hold to using our AWS account to avoid further unexpected costs. Please fix Opus 4.7's billing issues in Bedrock. I think all AWS users might be facing this issue at some point.

• 
  Kai Antonio (@KaiAntonio61428) reported 57 minutes ago

  @awscloud Juggling all that info definitely slows things down. Centralizing it sounds like a smart move.

• 
  Riccardo Dana | @SWOP (@riccardo_dana) reported 58 minutes ago

  Due to the @awscloud outage @SWOP_ai is currently down. We are working hard to resolve the issue asap. We expect to have it back and running in the next 2 hours. We apologize for any inconvenience this may have caused.