Skip to content

SES Account blocked/stuck in Throttling state

-3

Hi,

We have a dev account in AWS that is currently stuck in Throttling. In November 2025, more then our daily send limit was sent out to a valid identity. Since then, we've been stuck in Throttling mode and the account dashboard shows:

Max 24 hour send limit: 200 Sent Last 24 Hours: 610 Remaining send: -410 Sending quota used: 305%

It has not gone down since then. Support has suggested to run the following CLI command: aws sesv2 --region ca-central-1 put-account-sending-attributes --sending-enabled

I did a couple of weeks ago now and nothing happens. No updates on the dashboard.

I then tried to reopen an account support case, but they keep talking about production access. This is a dev account, we do not want production access on this account. We do not have a support plan. We have tried in the past (December 2025) to request an increase for the sending limit to 1000 daily, it was refused.

What can we do ? Has anyone been in this situation? Can anyone provide a solution ?

1 Answer
1

Based on the situation you've described, your account appears to be experiencing throttling because you exceeded your daily sending quota (sent 610 messages when your limit was 200). When you exceed your account's sending limits in Amazon SES, the system produces throttling errors, and your application should be programmed to wait and retry send requests.

However, the persistent throttling state you're experiencing seems unusual. Here are a few important points to understand:

Your account appears to be in the Amazon SES sandbox, which has a limit of 200 messages per 24-hour period and a maximum sending rate of one message per second. The "Sent Last 24 Hours" counter should reset after a 24-hour period, so if it's been stuck since November showing the same numbers, this suggests a more complex issue.

The CLI command you ran (put-account-sending-attributes) is typically used to enable or disable sending capabilities, but it won't reset your quota counters or resolve throttling issues caused by exceeding limits.

Regarding your request for a sending limit increase to 1,000 daily messages: if your account is still in the sandbox and you haven't requested to be removed from it, you would first need to request sandbox removal. When you submit a request to have your account removed from the sandbox, you can also request quota increases at the same time. Simply requesting a quota increase while still in the sandbox would typically be denied.

Since you don't have a support plan and are experiencing what appears to be a technical issue with your account metrics not resetting properly, I recommend opening a case specifically describing this as a technical issue with your account's quota counter not resetting after 24 hours, rather than framing it as a production access request. Be clear that you're experiencing a stuck throttling state and that the metrics haven't updated since November despite the 24-hour period having long passed.
Sources
Errors related to the sending quotas for your Amazon SES account - Amazon Simple Email Service
Managing your Amazon SES sending quotas - Amazon Simple Email Service

answered 2 months ago
EXPERT
reviewed 2 months ago
  • "Since you don't have a support plan and are experiencing what appears to be a technical issue with your account metrics not resetting properly, I recommend opening a case specifically describing this as a technical issue with your account's quota counter not resetting after 24 hours, rather than framing it as a production access request. Be clear that you're experiencing a stuck throttling state and that the metrics haven't updated since November despite the 24-hour period having long passed."

    I did that, multiple times, and regardless of the support ticket title or the message containing the words "This is not a limit increase or production access request, ... " they keep telling me that this is not the right channel to ask for this since it ends up in the limit increase / production access request department.

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.