Our account has been suspended and is pending deletion because we missed several invoices. The email domain used for account notifications and MFA is hosted in Route 53, so our mailboxes stopped working when the account became inaccessible. We also have a phone number associated with MFA, but we haven't been able to receive a verification call or obtain a guest checkout link through an alternate email address. As a result, we can't complete MFA or pay the outstanding balance. What's the best way to reach a human in billing or account support and recover access?
3 Answers
Hosting the DNS for your account’s email domain in the same account creates a nasty recovery loop. Once access is restored, move the domain’s authoritative DNS and account-recovery mail to an independent provider, keep an alternate administrator address outside the account, and make sure billing alerts go to multiple people. For the immediate issue, clearly identify the suspension as a missed-payment case and request manual identity and billing verification.
A higher support tier is useful for technical incidents, but it probably won’t bypass a suspended account or missing payment. The fastest route is likely billing/account recovery, with proof that you control the account and payment method. Also check whether the domain’s DNS records can be restored or delegated elsewhere; if the domain itself is still registered and you can update its nameservers, that may bring mail back independently of the affected account.
If the account is suspended for nonpayment, the issue needs to go through account or billing support rather than normal technical support. Use the provider’s public support or account-recovery form, choose the billing/access problem, and provide the account ID, billing details, phone number, and an alternate email address. Explain that the account’s DNS and email are hosted there, so the usual verification path is unavailable. A paid support plan may help in normal cases, but account suspension usually has to be handled by the billing team.
That’s the problem we’re running into: the normal verification email goes to the unavailable domain, and we haven’t been able to trigger phone verification or get a guest payment link. We’ll keep pursuing the public billing-recovery route with the account details and alternate contact information.