Article

Amazon SES Bounce Rate Limit Explained: Thresholds and Safe Targets

By Unlimited Verifier Team ·

Diagram of the Amazon SES bounce rate scale showing a 2% planning target below the 5% AWS review point and 10% pause point.

Summary

Amazon SES's public documentation describes an account review at a 5% bounce rate and a possible sending pause at 10%. Because those figures mark where problems start, a safer planning target is to keep bounces under 2% per send. Check the current AWS wording, measure each send, and clean your list before you scale.

Amazon SES's public documentation describes an account review at a 5% bounce rate and a possible sending pause at 10%, so the safe planning target is to stay under 2% per send. A bounce rate is the number of bounced messages divided by the number of messages sent. AWS's figures are the official reference points, but they mark where trouble starts, not where you should operate.

Quick answer

What is the Amazon SES bounce rate?

The bounce rate is the number of messages that bounced divided by the number of messages sent over the period AWS measures. SES shows reputation metrics in the console for each AWS Region you send from, and it publishes the same metrics to Amazon CloudWatch, so you can alarm on them.

Bounces fall into three families:

Bottom line: The ratio is simple, but the number that matters for list hygiene is permanent bounces per send, because verification and suppression control those.

What bounce rate gets an Amazon SES account reviewed or paused?

AWS's documentation describes 5% as the review point and 10% as the pause point. Other ESPs and mailbox providers can act at lower levels, so the number you plan around should sit below AWS's line. Public sources don't give one consistent cut-off across platforms, so we recommend planning to 2%.

Bounce rate (per send) What it means for SES What to do
Under 2% Healthy. Normal list decay Monitor the alarm; verify on a schedule
2% to under 5% Warning zone. Investigate Find the segment or source; suppress and verify it before the next send
5% to under 10% Review threshold per AWS documentation Pause affected campaigns and prepare a written remediation case
10% or higher Pause threshold per AWS documentation Stop sending and contact AWS support with a remediation plan

Complaints are a separate problem. Google's sender guidelines ask bulk senders to keep the spam rate below 0.3%, and Yahoo's sender requirements set similar expectations. SES tracks complaints as their own metric with their own thresholds, which sit lower than the bounce figures, so check the current numbers in AWS's documentation. Old lists often produce both bounces and complaints, because people who don't recognise a sender are more likely to mark it as spam.

Does the limit apply to one campaign or to the whole account? AWS's review decisions concern your account's sending, not a single send. In practice, though, one large campaign to bad data can carry the account over the line, which is why we measure each send. Our guide on whether one campaign can ruin sender reputation covers how that plays out with mailbox providers.

Bottom line: Aim for under 2% per send. Treat 5% as the point where recovery work has already started.

Why does SES enforce a bounce limit at all?

Bounces tell mailbox providers that you're mailing addresses that no longer exist or never asked for mail. Providers respond by filtering the sender, and on shared infrastructure that cost reaches other customers. SES's limits protect the platform's standing with those providers.

A dedicated IP changes which address you send from, not which addresses you send to. The bounce problem follows the list, so a new IP pool doesn't fix it.

Bottom line: SES cares about list quality because mailbox providers judge the platform by the senders it hosts.

How do you see your bounce rate in SES?

Use three tools, each for a different job: the console for the headline rate, CloudWatch for alerts, and event data for the cause.

  1. The console dashboard shows the reputation metrics for each Region. SES tracks reputation per Region, so a spike in us-east-1 won't necessarily appear in eu-west-1.
  2. A CloudWatch alarm on the bounce-rate reputation metric, set at 2%, notifies you before AWS's 5% line applies.
  3. Configuration set event data tells you which campaign, template or source produced the bounces. Publish bounce events to Amazon SNS, CloudWatch, Amazon Kinesis Data Firehose or Amazon EventBridge. Without event data you know the rate but not the cause.

The dashboard is too slow for diagnosis. By the time a rate shows there, the bounces are already in your sending history.

Bottom line: Use the console for the number, CloudWatch for the alarm, and event data for the cause.

How do you diagnose a bounce spike in SES?

Start by grouping bounces by campaign and source. Most spikes come from one segment, not the whole list.

  1. Group bounces by configuration set, template and campaign. A spike confined to one campaign points to that campaign's list.
  2. Break permanent bounces down by subtype. A cluster of NoEmail points to stale or invented addresses. A cluster of Suppressed or OnAccountSuppressionList means SES blocked sends to addresses it already held on a suppression list. That points to your sending process, which kept trying addresses that should have been removed.
  3. Compare rates by source. Check imported lists, form signups, purchased contacts and older segments separately. Our guide on why bounce rates jump after importing a list covers the common patterns.
  4. Check the age of each list. Addresses unmailed for a long time are the most likely to be dead. Is it safe to email a list that is two years old walks through that risk.
  5. Look for signup abuse. A form without validation can produce a burst of fake addresses in a single day.

Bottom line: A bounce rate tells you something is wrong. Breaking it down by source tells you what to fix.

Does the SES suppression list stop bounces?

Yes, for repeat bounces. No, for first-time bounces. The account-level suppression list can be set to cover bounces, complaints or both. The SESv2 API lets you list, get, add and delete suppressed addresses using the ListSuppressedDestinations, GetSuppressedDestination, PutSuppressedDestination and DeleteSuppressedDestination operations.

The limit is that the list only knows about addresses that have already failed or complained. An address you've never mailed can be dead and still count as a bounce the first time you send to it. Check in your own event data and reporting how suppressed sends are counted, rather than assuming either way. Also keep your own copy of the suppression data. It's your record of which addresses to exclude if you ever move to another provider.

Bottom line: Suppression stops repeats. Verification stops first-time bounces. You need both.

Which cleaning method keeps you under the SES limit?

Each method catches a different kind of bad address. Pre-send verification is the control that reaches addresses SES has never seen fail.

Method What it catches What it misses Effect on SES bounce rate
SES suppression list only Addresses that already bounced or complained Dead addresses you haven't mailed yet Stops repeats; first-time failures still count
Removing last campaign's bounces The latest failures Dead addresses in segments you didn't mail Partial; the rest of the list is untested
Pre-send bulk verification Invalid syntax, dead domains, missing MX records, nonexistent mailboxes, plus risky categories Consent, which verification can't confirm Strongest control over first-time bounces
Sunset by inactivity Long-dormant contacts Recently added bad addresses Good as policy; weaker as the sole control
Real-time validation at signup Bad or mistyped addresses at entry Addresses that go bad later Keeps new bad data out

The strongest setup combines pre-send verification, a suppression list you maintain, and checks at signup. See real-time email validation for the entry point, and email list maintenance best practices for scheduling.

Bottom line: Use the suppression list to stop repeats and verification to stop first-time bounces.

How do you stay under 2% long term?

Set a bounce budget for every send and a ramp schedule for anything new or revived. The arithmetic is simple, and it turns a vague goal into a check you can run before each campaign.

Before sending, project the bounce count from your verified segment. If the projection goes above 2%, stop and verify the segment again before sending. For cadence, verify before every import and re-verify active lists monthly. Dormant lists should be verified before any re-engagement send. These intervals are our recommendation, not a platform rule.

Ramp new or revived lists over one to three weeks, starting with the most engaged contacts. How to warm up an old email list after cleaning sets out a schedule.

Bottom line: A per-send bounce budget and a ramp schedule prevent most reviews before they start.

How do you remove bounces before your next SES send?

Export your SES bounce data, merge it with your sending list, verify the full list, suppress Invalid addresses and send to Valid addresses first. Expect a single working session for a list in the tens of thousands, and more if the file has to be split.

  1. Pull the bounce data. Collect permanent bounces from your configuration set's event data, or from the suppressed-destinations operations in the SESv2 API. Save them in a CSV with the date and subtype for each address.
  2. Merge with your sending list. Combine the bounce file with the full list you plan to mail. Remove duplicates and keep a separate copy of the suppression data.
  3. Split for upload if needed. On Pro, each list can hold up to 25,000 emails, and you can have unlimited lists. On Free, each list holds up to 150 emails, with 25 lists a month. Split larger files before upload.
  4. Upload and verify. Go to upload and verify a list and submit your CSV or Excel file, up to 10MB. The email column is detected automatically. Each address is checked for syntax, domain, MX records and the SMTP mailbox, and catch-all, disposable and role-based addresses are flagged.
  5. Read the three buckets. Valid addresses are safe for your next send. Invalid addresses should be suppressed permanently. Risky addresses include catch-all domains, where the mailbox can't be confirmed, as well as disposable addresses and role accounts such as info@. Hold Risky addresses back from your first sends. The catch-all email verification page explains how those results are handled.
  6. Export the results as CSV, Excel or JSON, and keep the counts for your records. Results are kept for 24 hours on Free and 30 days on Pro, so save your files the same day you verify.
  7. Suppress Invalid and send to Valid first. Add the Invalid addresses to your SES suppression list, then send to Valid contacts. There is no native SES integration, so this step is an export, verify and re-import workflow. To automate it, use the email verification API, available on Pro, which accepts single checks or batches of up to 10,000 emails per request. For a quick check on one address, use the free email checker. For how teams build this into recurring jobs, see email verification API and automation.

Bottom line: Pull the bounces, verify the full list, suppress Invalid and send Valid first.

What do SES bounce calculations look like in practice?

The numbers below are hypothetical. The plan limits and prices are real.

Example 1: One segment pushes the account over 5%

A team sends to 300,000 contacts and gets 18,000 permanent bounces.

18,000 ÷ 300,000 = 6.0%, above the 5% review line

Breaking the bounces down by source shows where the problem sits. 12,500 bounces came from one imported segment of 40,000 contacts:

12,500 ÷ 40,000 = 31.3% on that segment

The other 260,000 contacts produced the remaining 5,500 bounces:

5,500 ÷ 260,000 = 2.1%, slightly above the 2% target

The team suppresses all 18,000 known bounces, which leaves 282,000 contacts (300,000 − 18,000). The imported segment is removed at its source. The rest of the list is verified to catch addresses that haven't failed yet. The next send's bounce rate depends on how many of those are dead, so measure it rather than assume it.

Example 2: Small batches swing the percentage

A new sender tests a 400-address send and gets 40 bounces:

40 ÷ 400 = 10%

That is pause-level from a single small batch. Early sends should start with verified addresses, because a few bad ones can dominate the rate.

Example 3: Budgeting verification for 180,000 contacts

A SaaS company has 180,000 contacts to clear before a re-engagement send. On Pro, each list holds up to 25,000 emails:

180,000 ÷ 25,000 = 7.2, so 8 lists (seven of 25,000 and one of 5,000)

Standard verification is unlimited on every plan, so all 180,000 can be checked. Deep verification is capped at 25,000 a month on Pro, so spend that allowance on the riskiest 25,000: contacts unengaged for over a year and any segment that bounced last time. The effective cost of the included deep-verification allowance is:

$29 ÷ 25 (thousands of deep verifications) = $1.16 per 1,000 $25 ÷ 25 (annual billing, per month) = $1.00 per 1,000

These are plan prices divided by included allowance, not per-email fees. Compare them with the time, lost sends and recovery work an SES review can cost.

Bottom line: The arithmetic shows where bounces originate and how much verification the list needs.

What are the common mistakes with SES bounce limits?

Bottom line: Most SES problems come from measuring too late, sending too early and relying on a single control.

What should you do if SES has already paused your account?

Stop sending and keep your evidence. Then contact AWS support with a written remediation case. Include the bounce rate and the campaign it came from, the cause, the number of addresses suppressed and verified, and a re-entry plan with a ceiling of 2%. The structure mirrors a reinstatement appeal for other ESPs.

Each platform sets its own thresholds, so don't apply one provider's figure to another. For comparison, see our guides to Mailchimp suspensions, SendGrid's under-review status, Brevo suspensions and Mailgun's bounce warnings. For what triggers a pause on any platform, see what bounce rate gets your ESP account suspended. If you're still preparing an import, how to avoid ESP suspension when importing old lists covers the pre-send checks.

Bottom line: A written, numbers-based case is the fastest route back, whether the platform is SES or another ESP.

Which email verifier fits an SES workflow?

Choose a verifier that separates Valid, Risky and Invalid addresses, handles your file sizes, offers an API if you automate, and exports results in a format your team can use. Our guides to the best email verification tools and how to choose an email verifier go into the checks in more depth. For a broader comparison of options, see the roundup of the best email verification tools.

Unlimited Verifier covers the workflow in this article. Its differentiators are:

The trade-offs are specific. There are no native SES, ESP, CRM or Zapier integrations, so you export, verify and re-import, or call the API from your own script. Free keeps results for 24 hours, and deep verification is capped at 25,000 a month on Pro. The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark.

Need Free Pro
Price $0 $29/month, or $25/month billed annually
Lists per month 25 Unlimited
Emails per list Up to 150 Up to 25,000
Deep verifications per month 750 25,000
API access No Yes, 100,000 emails a month
Results kept 24 hours 30 days
Standard verification Unlimited Unlimited

If you're deciding between plans, the question is whether your list fits 150-email lists and whether you need the API. Teams with email verification for ecommerce and SaaS needs, such as frequent imports, usually outgrow Free quickly. Check current plan details and email verification pricing before you commit. You can create a free account and test a file before deciding.

Bottom line: Pick a verifier that matches your list size, your automation needs and your reporting, then verify before every send.

How we compared (and limitations)

This article draws on public documentation: the Amazon SES documentation on reputation metrics, bounce handling and sending limits; the SMTP enhanced status codes in RFC 3463; and the published sender guidelines from Google and Yahoo. We haven't run controlled tests against AWS's review process, and we can't see SES's internal counting rules.

AWS updates its thresholds and documentation without notice, so check the current SES pages before you plan around any figure here. The 2% target is our planning recommendation, not an AWS threshold. Unlimited Verifier figures come from the company's published plan details, and the 99.5% accuracy figure is the company's own claim. The worked examples are hypothetical. The plan limits and prices are real.

Bottom line: Use AWS's current documentation for thresholds, and use the 2% target for planning and verification.

Worked example: calculating your bounce rate per send

Campaign Sent Permanent bounces Bounce rate Status vs. plan
Newsletter A 10,000 150 1.5% Under 2% target
Promo B (old segment) 10,000 420 4.2% Warning zone, investigate
Re-engagement C (verified) 5,000 40 0.8% Healthy

Steps: 1) Divide bounces by messages sent. 2) Compare to 2% target and AWS's 5% review line. 3) For any send above 2%, find the segment, suppress and verify it, then resend only to clean contacts.

Frequently asked questions

What is the Amazon SES bounce rate limit?

AWS's public documentation describes an account review at a 5% bounce rate and a possible sending pause at 10%. These are the official reference points, but they mark where trouble starts. A safer planning target is to keep bounces under 2% per send, which gives headroom before AWS's lines are reached.

How is the SES bounce rate calculated?

The bounce rate is the number of bounced messages divided by the number of messages sent over the period AWS measures. For example, 150 bounces out of 10,000 sends is a 1.5% bounce rate. Check the reputation metrics in the SES console for each Region you send from.

Will Amazon SES pause my account at 10% bounces?

AWS documentation describes a possible sending pause at a 10% bounce rate. Whether it is applied depends on your account's history and the current policy, so confirm the wording on the SES documentation pages. If you reach that level, stop sending and contact AWS support with a remediation plan.

What is a good bounce rate for Amazon SES?

A good bounce rate for Amazon SES is under 2% per send, which is a planning target rather than an AWS threshold. Rates at or above 5% trigger AWS's documented review point. Keeping a low rate depends mostly on verifying addresses and suppressing known bounces before each campaign.

Where can I see my SES bounce rate?

You can see your bounce rate in the reputation dashboard of the Amazon SES console, separately for each AWS Region you send from. SES also publishes the same reputation metrics to Amazon CloudWatch, so you can set alarms that notify you when the rate rises.

What is the difference between permanent and transient bounces?

Permanent bounces mean the address cannot receive mail, such as a nonexistent mailbox, and carry 5.x.x SMTP status codes. Transient bounces are temporary problems, such as a full mailbox, and often succeed on retry. Undetermined bounces are cases where the receiving server gives no clear answer.

Are spam complaints included in the SES bounce rate?

No. Complaints are tracked as a separate metric with their own thresholds, and they are not part of the bounce rate calculation. Old or purchased lists often produce both bounces and complaints, so cleaning the list helps both numbers.

How do I lower my Amazon SES bounce rate?

Remove known bounced and complained addresses, verify the rest of the list, and send your first campaigns to recently engaged contacts. Use the SES account-level suppression list so previously bounced addresses are not mailed again. Then measure every send before scheduling the next one.

Can I appeal an Amazon SES account review?

AWS support is the route for responding to an SES account review or pause. Prepare a written remediation case that explains the cause, lists the steps you have taken such as suppression and verification, and shows the bounce rate trend. Respond promptly and pause affected sends while you wait.

Does the SES suppression list stop bounces?

The SES suppression list stops SES from sending to addresses that previously bounced or complained, which prevents repeat bounces to the same address. It does not fix an unclean list by itself, so you still need to verify new addresses and remove stale ones before sending.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.