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 (40%)
• Errors (35%)
• Sign in (25%)

Live Outage Map

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

City	Problem Type	Report Time
Clearwater	Website Down	10 hours ago
Monterrey	Website Down	6 days ago
Rostock	Website Down	9 days ago
Glendale	Website Down	20 days ago
Oakland	Sign in	22 days ago
Greater Noida	Errors	22 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:

• 
  Uttam Tarsariya (@UttamTarasariya) reported 3 minutes ago

  @AWSSupport URGENT: My account was auto-upgraded from Free Tier, then suspended minutes later. No dues, no violations. Cannot login (root or IAM). Our production AI agent serving live users is DOWN. Please help reinstate ASAP. Ready to verify anything. Can I DM details?

• 
  XALE (@InvincibleXALE) reported 5 minutes ago

  @AWSSupport Hi again, Its been over 2 days now, and over 30+ customers are affected of ours and its been critical And our account is still the same Feeling kind of hopeless on this.. I need this issue resolved ASAP, PLEASE Before the week starts or this issue can force us to lose clients

• 
  ZacD (@ZackD0x) reported 5 minutes ago

  @awscloud feels like banks finally saw the glitch and decided to hit ctrl+alt+del on themselves

• 
  CodieEditor (@CodieEditor) reported 7 minutes ago

  @AWSSupport It is not just our issue; all the customers/startups across AWS who are using credits for building something must be faced with this issue. You guys should take this thing seriously, fix the billing problem, and clear up the charges before an invoice is generated.

• 
  TechBrosTechBro (@WE2SeriousConvo) reported 9 minutes ago

  @JeffBezos We need to give everyone in the world 1VCPU for free for life from amazon aws. That will solve all world problems. People can rent them out or host their websites and or business ideas. Call me Jef..

• 
  Kunal (@kunal_twts) reported 10 minutes ago

  @ryukozyy @awscloud But those computers ease so much issues for companies

• 
  practitioner (@Chrispractical) reported 14 minutes ago

  @awscloud The real advantage isn’t budget size… it’s how fast you can safely ship AI that actually solves real problems in regulated industries

• 
  Kaspa Mode: ON (@KasConviction) reported 17 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.

• 
  mxh (@Jadore71411744) reported 25 minutes ago

  @AWSSupport Thank you — please do prioritize this. My account has been down for 24+ hours and I still haven't received the verification email. Case 177691716900502 is still unassigned. Waiting on your DM reply.

• 
  Ibraheem Tuffaha 🥛 (@IbraheemTuffaha) reported 26 minutes ago

  when you try to buy Savings Plans yourself 🫠 @awscloud gives you Savings Plans and Reserved Instances Different types, different terms, different quantities They even give you recommendations Those recommendations go stale in days Usage shifts, workloads change, and suddenly you're either underutilized or short Under-buy and you miss the savings Over-buy and you're locked into years of commitment you don't need We've watched companies spend months on this and still get it wrong @MilkStrawAI does it automatically Scans the AWS account, figures out exactly how much commitment is needed, and buys it gradually over a week If usage shifts up or down, the system adjusts on its own Zero intervention from the client They just see the bill drop at the end of the month

• 
  nick (@NicsTwitz) reported 27 minutes ago

  @amazon @AnthropicAI @awscloud 100 billion dollar compute commitment is wild. the AI arms race isnt slowing down its accelerating

• 
  SCOTT (@ScottSummers) reported 28 minutes ago

  If you’re still ignoring $ICP after today and @awscloud going down you’re retarded

• 
  Misu (@yngmisu) reported 29 minutes ago

  i’m having a really hard time getting better value from the open source models that are available on bedrock claude and codex just oneshot tasks, ending up cheaper in the long run i don’t like spending money on the model just solving compile errors in a loop @awscloud can we get some of the new models on bedrock or are yall busy with the openai deal (which i’m waiting for too)

• 
  Trevor Skinner (@PrometheusAIsec) reported 30 minutes 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.

• 
  Smarty (@RathoreSmarty) reported 31 minutes ago

  @AmazonHelp @amazonIN @awscloud It is unacceptable refund was already initiated w/o any investigation Now after investigation,its denied citing policy violations. If issue, why was the refund approved in the 1st place? Reversing it later is unfair. I request immediate refund.

• 
  Henrique Lima (@HenriqueLi88059) reported 33 minutes ago

  @AWSSupport @awscloud Update: our account has been reactivated! ✅ After 36+ hours down, our Medical Imaging platform is back online. Thank you to @AWSSupport and the verification team for resolving this. We hope no other healthcare platform has to go through this. 🙏

• 
  Ashish Pawar (@Ashish_Pawa_22) reported 38 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.

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

  @Harryhwrqx @chainlink @awscloud and price goes down

• 
  Mark Kappel (@DTLB58) reported 39 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?!?!

• 
  hunterjackson (@Tweeter_itsme) reported 41 minutes ago

  @amazon @amazonIN @awscloud provided. Instead of resolving the issue, the same delivery person keeps being assigned again and again. This is unacceptable customer service and harassment of customers.

• 
  Carbon Tax Neil (@NeilPitman10) reported 46 minutes ago

  @AWSSupport Great! another bot. OK, but no one is looking at the github issues log.

• 
  StatusGator (@statusgator) reported 50 minutes ago

  🔥AWS outage update: @awscloud is calling the ongoing US East 1 outage in N. Virginia a "thermal event". It sounds like some cooling system failed over there at AWS. Also, the backup cooling must have also failed. And then some instances got fried. Impact has expanded to other services in the Availability Zone that depend on affected instances: AWS IoT Core Amazon ElastiCache Amazon Elastic Load Balancing Amazon Redshift Amazon SageMaker

• 
  Fôrtûne (@Fortune71227524) reported 50 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.

• 
  Sakura Yuki (@sakurayukiai) reported 51 minutes ago

  @vllm_project @awscloud @RedHat_AI The wild part is that FP8 KV cache was silently nuking 128k retrieval down to 13% and everyone probably just blamed the model. Two-level accumulation in FA3 is a massive save.

• 
  Dhananjay Maurya (@dhananjaym182) reported 53 minutes ago

  @AWSSupport I have sent Aws case in private message please have look and fix the issue

• 
  Basim Khalid (@basimkhalid) reported 56 minutes ago

  @nygma504 @AWSSupport @awscloud Its down for me too. Any ETA please?

• 
  Uttam Tarsariya (@UttamTarasariya) reported 58 minutes ago

  @AWSSupport Now, the guy who was working on this problem disappread and a new supporter came and respond me to go on the login page and dashboard and upgrade the plan. Simple !!! He does not know anything about the issue and we have to explain to him I think.

• 
  HRH Prince Sven Olaf of CyberBunker - CB3ROB (@cb3_rob46858) reported 58 minutes ago

  @awscloud then you end up with a leaking radiator, oil leaks and half the lights broken because noone ever can be ****** to change them on those horrid contraptions.

• 
  Money Guru Digital (@Moneygurudigi) reported 59 minutes ago

  🚨 Coinbase just went down for hours Large parts of the platform became unusable while traders were trying to access the market. The reported issue? Problems tied to Amazon AWS infrastructure. One reminder again: A huge part of crypto still depends on centralized systems

• 
  Martin Alltimes (@Palatineirish) reported 59 minutes ago

  @awscloud What’s the difference between modernising and rebooting. Terrible, confusing text.