Skip to content

Account suspended for 120 hours after payment made

0

Hello, everyone. My AWS account (ID: 764198108419) was suspended due to a payment issue, but I already made the payment via PIX 120 hours ago (on September 18), and my account has still not been reactivated. I have opened 3 support cases about this issue, but I have not received any response so far. This delay is causing critical services to remain down, and I urgently need help to have my account reactivated. Has anyone faced a similar situation or knows how to escalate this to get faster assistance? Thank you!

asked a year ago251 views

2 Answers
0

I understand your frustration with your AWS account remaining suspended even after making a payment 120 hours ago. This situation is not uncommon, but the timeframe you're experiencing is longer than typical.

Here's what's likely happening and what you can do:

  1. When an account is suspended due to non-payment, making the payment is the first step, but it doesn't automatically reactivate the account. Account reactivation requires manual intervention from the AWS Support team.

  2. While reactivation typically takes up to 24-48 hours, in some cases it can take longer, especially if there are complications or high support volumes.

  3. Since you've already opened multiple support cases, here are some additional steps you can take:

  • Ensure you've opened your support cases under the "Account and billing" category, which is available even for suspended accounts.
  • In your support case, clearly explain that you've made the payment 120 hours ago and provide any relevant payment confirmation details or transaction IDs.
  • Check all email addresses associated with your AWS account, including spam folders, for any communications from AWS that might require additional information.
  • Make sure all your contact information in the AWS account is up-to-date.
  1. If you have an AWS Account Manager or are working with an AWS Partner, consider reaching out to them for assistance in escalating the issue internally.

  2. Update your existing support case to emphasize the business impact and critical nature of your services being down, which might help prioritize your case.

While the waiting period is frustrating, especially with critical services affected, continuing to engage with AWS Support through your open cases is still the primary channel for resolving this issue. Be persistent but patient, and don't hesitate to request updates if you haven't received a response within a reasonable timeframe.
Sources
Billing and Account blocking | AWS re:Post
AWS Account Suspension Persists Despite Payment Clearance – How to Escalate? | AWS re:Post
Account suspended | AWS re:Post
AWS Support not responding on suspended account | AWS re:Post

answered a year ago

AWS
EXPERT

reviewed a year ago

0

I understand the frustration and urgency of this issue.

I have reached out, to our internal teams, on your behalf. Please continue to monitor your Support Center for any additional guidance and updates: go.aws/support-center.

- Randi S.

AWS
EXPERT

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.