NOW LET US – AI RAG SaaS Studio TP.HCM
NOW LET US
Digital Product Studio
Back to news
DEV-TOOLS...1 min read

Ask HN: AWS account restricted 18h despite remediation (Case 177385077300217)

Share
NOW LET US Article – Ask HN: AWS account restricted 18h despite remediation (Case 177385077300217)

Startup Qcart is facing a total production outage after AWS restricted their account due to an exposed CircleCI key. Despite immediate remediation and credential rotation, the team has received no human response from AWS Trust & Safety for over 18 hours.

Our startup (Qcart) is currently facing a 100% production outage across multiple countries. AWS Trust & Safety restricted our account 18 hours ago due to an exposed circleci access key.

Timeline:

18+ hours ago: Received notification of exposed keys (linked to a circleci-eb user).

We deleted the IAM user and all associated keys. Confirmed remediation in the support case.

Current status: Total silence. Support agents keep saying "the specialized team is looking into it," but we have had zero updates while our business is dying.

We have already rotated all credentials and verified that no other unauthorized access exists. We are a small team and this 18-hour delay with no human response from the security team is devastating.

Does anyone at AWS have advice on how to get a human to actually review a resolved security flag?

Case ID: 177385077300217

Any help or visibility is greatly appreciated.

© 2026 Now Let Us. All rights reserved.

Source: Hacker News

Advertisement
Ad slot ready: 5887729102

More in this category

EXPLORE TOPICS

Discover All Categories

Deep dive into the specific technology sectors that matter most to you.