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 (39%)
• Website Down (32%)
• Sign in (29%)

Live Outage Map

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

City	Problem Type	Report Time
Oakland	Sign in	21 hours ago
Greater Noida	Errors	1 day ago
Alamogordo	Website Down	6 days ago
San Francisco	Website Down	8 days ago
Mercersburg	Sign in	10 days ago
Palm Coast	Errors	13 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:

• 
  Mohammad Imran (@mohdemraan) reported 1 second ago

  @AWSSupport This is not about account suspension. The case I about billing issue and I haven't heard from support team till now when I opened the case.

• 
  неможливо розбачити (@stimcrol) reported 6 minutes ago

  @awscloud You had 13-hour outage because of AI push. You'd better resign sooner

• 
  N (@namzylll) reported 11 minutes ago

  Ignoring the Middle East when it comes to servers is a huge oversight. ALOT of players are stuck with 130+ ping. FIX THEM!!!! @FortniteStatus @awscloud @FortniteME #fortniteriyadh

• 
  tsonubin (@tsonubin) reported 11 minutes ago

  Anybody experiencing login issue with AWS CLI? @awscloud @awssupport

• 
  nightshift (@nightshift54619) reported 13 minutes ago

  @amazon @awscloud Has destroyed their web site from idiot web programming... It's so slow and laggy it's unusable. Whatever they did in the last couple weeks, destroyed its usability. Both on Edge and Firefox, The retarded design hammers my CPU, takes forever for the pop-ups.

• 
  Testing Account (@Haleyafabian) reported 15 minutes ago

  @AWSSupport my package was broken when delivered. I need it replaced asap.

• 
  Aikido Security (@AikidoSecurity) reported 16 minutes ago

  @kirodotdev is rewriting how software gets built. We're making sure it's secure. Aikido is the first security partner globally that @awscloud going to market with for Kiro. 🚀 AI agents now generate most of your code. Catching security issues in review doesn't scale. So we put Aikido where the agents are. Every change gets scanned automatically.

• 
  Mike Dupont (@introsp3ctor) reported 16 minutes ago

  @AWSSupport oh, now it magicallly worked again! i just logged in. thanks for your help. this is the second multi day outage, once a month it seems

• 
  Abomination (@Abomination81) reported 17 minutes ago

  @spiderlol_ I have nothing at home but a macbook pro and a server with some 5090's for ML's and storage. I use amazon aws ec2

• 
  WilliamNextLvl (@WilliamNextLev1) reported 18 minutes ago

  @WatcherGuru Only problem is...$NET is not in the business of cyber security. LOL Cloudfare competes with Amazon AWS for serverless computing. (I would buy $NET here...)

• 
  TopCeo (@TeetheBuilder) reported 20 minutes ago

  @KylePause @AWSSupport Are you still having issues with this? I may be of help

• 
  CodieEditor (@CodieEditor) reported 20 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.

• 
  Neal🅾️ (@BuddyPotts) reported 22 minutes ago

  @danorlovsky7 @awscloud @NextGenStats The defense was horrendous last year and all they added was Edmunds but lost Okereke and Flott. They cant stop the run at all, they should trade down and collect more picks and build the defense

• 
  जहाँ mila,वही खोदूंगा (@GamingNepr34519) reported 22 minutes ago

  @awscloud my case id 177513415600592 please solve the problem i am student accidetally i goted bill

• 
  james bowler 👹 (@jmbowler_) reported 24 minutes ago

  anyone else having trouble getting past @awscloud mfa?

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

• 
  Andrew Sam (@egy_pl_eagle) reported 28 minutes ago

  @WhoisNuel @awscloud that's scary cause banking are known to be stable and bug free ... also with AI we will still have a maintainability issue

• 
  CodieEditor (@CodieEditor) reported 32 minutes ago

  @AWSSupport Already sent, please take a look. This problem is with only the use of Claude Opus 4.7 via Bedrock; billing of other services are working totally fine.

• 
  Xyz (@Xyzfb2t) reported 32 minutes ago

  @awscloud First create a problem by having different services and the solve it by creating a new service.

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

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

• 
  Decent Cloud (@DecentCloud_org) reported 41 minutes ago

  @AWSSupport @theodorebeers GitHub feedback. No case ID. No SLA. Problem solved - for AWS.

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

• 
  NFT and CRYPTO Fan (@MC59785335) reported 44 minutes ago

  @AWSSupport Thank you for support . Actually i think with support + or even with regular plan such kind of issues like restore limits should be resolved in 1 hour range. However im still have not received any answer regarding my case..

• 
  Saad Hussain (@SaadHussain654) reported 44 minutes ago

  @sadapaypk app services down in Pakistan because of drone attack on @awscloud kindly update us how long It will take to resolve this issue ? We are suffering from 1,2 days

• 
  Mapharaphara🇷🇺🇷🇺 SR Tumel⭕ Elemch⭕s Makhudu (@ElemchosMaphara) reported 45 minutes ago

  @awscloud Is the rear seat killing issue fixed or Americans are liars?

• 
  Akintola Steve (@Akintola_steve) reported 46 minutes ago

  Where statelessness breaks at the infrastructure level, silently. File uploads written to local disk. The file lives on one instance. Others cannot see it. Fix, object storage like Amazon S3. In process caches with no sharing. One instance caches, another does not. Fix, centralized cache. Background jobs tied to instance memory. Jobs disappear on restart. Fix, external queue. WebSocket connections tied to one server. Broadcasts miss other clients. Fix, shared pub or sub.

• 
  canadianbreaches (@canadabreaches) reported 48 minutes ago

  BREACH ALERT: Duc (Duales) — Toronto fintech. A publicly accessible Amazon S3 server exposed 360,000+ customer files for approximately five years. Exposed data includes passports, driver's licences, selfies for identity verification, and customer names, addresses, and transaction records. Office of the Privacy Commissioner of Canada is investigating. Severity: CRITICAL.

• 
  The Night King (@nightkingog) reported 52 minutes ago

  I am witnessing @awscloud is doubling down

• 
  Arthurite Integrated (@Arthurite_IX) reported 52 minutes ago

  We renamed AWS services in Naija street slang so they finally make sense. 1. Amazon S3 = "The Konga Warehouse" Store anything. Retrieve it when you need it. It doesn't judge what you put inside. 2. Amazon EC2 = "The Danfo" You control the route, the speed, and how long it runs. The agbero (security group) decides who gets on. 3. AWS Lambda = "The Okada" Short trips only. No long commitments. Pay per ride. When it reaches the destination — it disappears. 4. Amazon RDS = "Iya Basement" She manages everything in the back. She's been there for years. She knows where everything is. Do not interrupt her. 5. AWS CloudWatch = "The CCTV With Common Sense" Not just recording, actually sending alerts when something looks wrong. Unlike the one in your office building. 6. Amazon Route 53 = "The Agbero" Directs all the traffic. Decides which danfo goes where. Keeps everything moving. 7. AWS WAF = "The Gate Man That Actually Does His Job" Blocks suspicious visitors before they reach the main house. No bribe accepted. 8. Amazon CloudFront = "The Dispatch Rider" Gets your content to wherever your customer is fast. No go-slow. No bridge hold-up. Which one made you laugh? Drop it in the comments. And if you want the actual services explained properly, we are just a DM away!

• 
  Murari mishra (@MurariYuvi) reported 58 minutes ago

  @AWSSupport Our organization with account id - 625119556213 is not able to login to the root account, also getting emails reg abuses in the account. Have been trying to get help but can't raise any support even. The Account manager has no clue what's going on. Can you help ASAP?