We're a small startup operating through a US company, and our production infrastructure—including databases, application code, EBS volumes, snapshots, and customer data—is hosted in AWS. For nearly a year, our usage was covered by AWS credits, so this was our first direct billing issue in a long time.
AWS notified us on August 2 that a payment had failed, even though our primary payment method had sufficient funds. On August 5, we discovered that the account was restricted while trying to launch an EC2 instance. We found the overdue invoice in the Billing Console and paid it in full immediately. AWS showed the invoice as "Paid" and sent a payment confirmation email.
The restrictions were not removed after payment, so we opened a support case. Several days later, the only response said the issue had been forwarded to the appropriate support team, but nobody followed up. On August 10, we received another suspension notice saying payment was required to restore access, even though the invoice had already been paid five days earlier and still shows as paid.
This has caused a serious production outage: our systems are inaccessible, operations are halted, and customers cannot use our services. We're also worried about whether our databases, volumes, snapshots, and other data remain intact and recoverable.
Has anyone dealt with an AWS account suspension that continued after payment? What is the most reliable way to escalate a billing suspension so AWS can manually verify the payment, restore access, and confirm that the data is preserved?
3 Answers
A payment marked as paid does not always mean every balance on the account is cleared. Check the full transaction history and all invoices, including small charges that credits may not cover. Marketplace purchases and some services—such as certain third-party or model-related charges—can be billed separately from normal AWS usage. Ask support to confirm the complete account balance and whether the payment was applied to the exact invoice associated with the suspension.
If this account supports production workloads, a Business Support plan is usually the fastest escalation path. Open or update the billing case, clearly state that the invoice is paid, attach the payment confirmation, and mark the issue as an account-access and production outage rather than a general billing question. Once access is restored, you can ask AWS to review the downtime separately, but the immediate priority is getting the billing and account teams to reconcile the payment.
Keep everything in the active support case: the paid-in-full status, payment confirmation, timestamps, screenshots, and the production impact. Ask directly for manual payment reconciliation and confirmation that no deletion or data-retention action is underway. Avoid opening many duplicate cases unless support instructs you to, since that can split the history between teams. The account team ultimately has to clear the restriction, so persistence through the billing escalation channel is more useful than trying to change infrastructure elsewhere.
Agreed—production systems generally need at least Business Support so urgent operational issues can be escalated. If you purchase it now, it may not automatically apply retroactively, but it should provide a better route for the current incident.