SES Virtual Deliverability Manager billing continues increasing after Global Deliverability was disabled

I've got very similar experience with VDM - I disabled it and still being charged for the past 7 days after the disabling... support case is still not assigned, and Support AI Agent is replying that charges had to stop1-2 days after disabling due to some kind of lag in billing... This is insane... I am not sure how we can escalate it, or report to BBB or whatever, but this level of support is unacceptable... basically charging for the service that we do not use.

Hello Pavish,

I'm sorry for the concern these charges have caused.

I can confirm that we've received your case and our Support team will be in touch to assist.

Keep an eye open for correspondence on your case.

- Craig M.

Thank you for the response.

However, I would like to clarify one important discrepancy.

The answer states that charges should continue until the September 1, 2026 subscription expiry date. However, this conflicts with the response I received directly from AWS Support on August 17, 2026.

AWS Support specifically stated:

“Your billing data shows no charges after August 17, 2026”

and:

“No additional subscription charges will be incurred going forward.”

Despite that confirmation, the billing amount subsequently increased:

• August 17: USD 162.97
• August 18: USD 206.65
• August 19: USD 258.74
• The amount continues to increase.

The SES console shows:

• Global Deliverability: Disabled
• Account status: Pending expiration
• Subscription expiry date: September 1, 2026

Therefore, my main question is not simply whether a disabled subscription can remain active until its expiry date. I need AWS to reconcile the specific billing timeline for my account with the previous AWS Support statement that no charges would occur after August 17.

My existing AWS Support case is:

The case is still showing Unassigned.

Could an AWS Support/re:Post expert please review this discrepancy and advise whether:

1. The charges after August 17 are legitimate subscription charges through September 1;
2. They are delayed billing records for usage before August 17; or
3. There is a billing/subscription state discrepancy that needs to be corrected.

I would also appreciate confirmation of the exact cancellation/disablement timestamp and the date on which billing for AP3S-Subscription-VirtDelivMgr will actually stop.

I am not accepting the AI-generated recommendation as confirmation of the billing behavior because it has not been reviewed by an AWS expert.

Thank you.

Edit: Removed case ID — Sage A.

Based on the subscription model for Global Deliverability, when you disable the feature, your subscription continues until the end of the current billing period shown as your 'Subscription expiry date.' In your case, that date is September 1, 2026, which means charges will continue to accrue until that date even though the feature shows as 'Disabled' with a status of 'Pending expiration.' This is the expected behavior for subscription-based services.

Regarding the increasing daily charges you're observing, Global Deliverability is sold as a single subscription package that includes monitored domains, dedicated IP monitoring, and inbox placement tests. The charges may be accumulating based on usage or the number of monitored resources during the remaining subscription period.

Since you already have an open support case regarding this billing matter, the best path forward is to continue working through the AWS Support Center. You can add correspondence to your existing case at https://console.aws.amazon.com/support/ with the specific details you've outlined, including the daily charge progression and the discrepancy between the August 17 date previously communicated and your September 1 subscription expiry date. The support team can investigate the exact billing timeline, confirm when charges should cease, review whether any charges are erroneous, and determine if a billing adjustment is warranted.

If you need faster response times or more comprehensive support for billing matters, you may also want to review your AWS Support plan options to ensure you have the level of support that meets your needs for time-sensitive billing issues.
Sources
Global deliverability - Amazon Simple Email Service
Virtual Deliverability Manager settings - Amazon Simple Email Service

I am experiencing the same issue. I also disabled Global Deliverability, but the AP3S-Subscription-VirtDelivMgr charge continues increasing. My AWS Support case has also remained unassigned. In my case, AWS Support initially stated that there would be no charges after August 17, but the charge subsequently increased from $162.97 to $460.35. I have an open billing case and am trying to get a human AWS Billing/SES specialist to investigate. It appears there may be a broader issue affecting VDM subscription cancellation/billing.