Article

How to Fix an Amazon SES Bounce-Rate Review: Step-by-Step Recovery

By Unlimited Verifier Team ·

Flow diagram showing the steps to fix an Amazon SES bounce-rate review: find the spike, suppress bad addresses, verify the list, and ramp sending under 2% bounc

Summary

To fix an Amazon SES bounce-rate review, find the sending stream that caused the spike, suppress every bounced and unverified address, and verify the rest. Then send AWS a plan showing bounces stay under 2%, well below the 5% review line in AWS's documentation.

To fix an Amazon SES bounce-rate review, find the stream that caused the spike, remove every bounced and unverified address, verify the rest, and send AWS a plan showing bounces will stay under 2%, well below the 5% review threshold in AWS's documentation.

SES is sending infrastructure, not a list manager. It reports what happened after each message and doesn't check addresses before you send, so the list problem usually sits upstream in an import, a sync or an old database table. A reviewer will want to see the list fixed, not only the sending pattern changed. This guide covers the full recovery path, with the numbers you need at each stage. For the broader picture of why suspensions happen, read our pillar guide on high bounce rate account suspension.

Quick answer

What does an Amazon SES bounce-rate review mean?

An SES bounce-rate review is AWS checking that your bounce and complaint rates sit inside its thresholds before you keep sending at full volume. The notice you receive names the metric that tripped, and the outcome can be a warning, a review or a sending pause.

SES judges the account, not a campaign. A bad import feeding one marketing configuration set can push the account-wide rate that also covers order confirmations and password resets. You can't fix that by quarantining the one campaign you remember. You have to find every stream that drew on the same data.

If you send through another platform, the logic is similar. Our guides cover Mailchimp suspensions, SendGrid's under-review notices, Brevo suspensions and Mailgun warnings.

Bottom line: The review judges the whole account, so the fix has to cover every stream that touches the affected addresses.

Which bounce rate triggers an Amazon SES review?

AWS's SES documentation sets 5% as the bounce rate that puts an account at risk, and 10% as the level at which sending can be paused. Check the current page before you plan, because AWS can change these figures.

Metric Figure What it means Source
SES bounce rate, at risk 5% or higher Account flagged for review AWS SES documentation
SES bounce rate, pause 10% or higher Sending may be paused AWS SES documentation
Mailbox-provider spam rate Below 0.1%; 0.3% or higher is a problem Gmail-side signal, separate from SES Google sender guidelines
Working bounce ceiling 2% Margin below AWS's review line Our recommendation
Re-entry wave ceiling 1% per wave Stops each ramp step early Our recommendation

Where sources disagree: AWS's 5% is a review line, not a safe level. Mailbox-provider filtering can react to problems well before that point, so we recommend a 2% working ceiling. The reason is margin: 2% leaves room below AWS's line and for list drift.

The 1% per-wave ceiling is about speed of detection. A wave that reaches 2% on 10,000 addresses produces 200 bounces, and you only see that once the wave finishes. A 1% ceiling caps the damage at 100 and gives you a clear point to stop.

Bottom line: 5% is when AWS starts asking questions. Aim for 2% overall and 1% during re-entry.

Why does SES flag an account when the spike came from one list?

There are three reasons, and each one changes how you should respond.

For SaaS teams the exposure is wider, because one account often serves product, onboarding and marketing mail. The email verification for ecommerce and SaaS approach treats every stream that reads from the same contact data as in scope for cleaning.

Bottom line: Treat the bounce count as a floor. The real problem is usually larger, and verification is how you find the rest.

How do you find which stream caused the bounces?

Use configuration sets and event publishing. A configuration set tags each message with its stream, such as marketing, onboarding or password resets. An event destination such as CloudWatch, Kinesis Data Firehose or SNS receives a notification for each bounce, with a type and subtype. Group the data by configuration set and by time, and the source of the spike usually stands out.

Bounce type and subtype What it usually indicates Action
Permanent / General Mailbox doesn't exist or the server rejected the address (often RFC 3463 code 5.1.1) Suppress, then verify the rest of the list
Permanent / NoEmail Recipient domain doesn't accept mail Suppress, and check where that domain came from
Permanent / Suppressed or OnAccountSuppressionList SES blocked a send to an address already on a suppression list Your sending code isn't respecting suppression. Fix it before resuming
Transient / MailboxFull Temporary full inbox Retry later, and suppress after repeated failures
Transient / MessageTooLarge, ContentRejected, AttachmentRejected The message, not the address Fix the content. This isn't a list problem
Undetermined Bounce couldn't be classified Inspect the raw notification

Confirm exact wording against AWS's bounce-type definitions. The RFC 3463 enhanced status codes explain what the underlying SMTP responses mean.

Read the table as a diagnosis. If most of a spike is Permanent / General from one configuration set created during an import week, the list is the likely cause. If the spike is mostly Suppressed or OnAccountSuppressionList, the problem is in your application. If the spike just started and you haven't yet opened a review, what to do when a bounce rate suddenly spikes covers the triage.

Bottom line: Subtypes tell you whether the problem is the list, your code or your content. Each needs a different fix.

How do you fix an SES bounce-rate review, step by step?

Work through these steps in order. Each one produces evidence for your case. The platform-neutral version of this playbook is in how to get an ESP account reinstated after bounces.

  1. Read the notice and confirm the metric. Note whether the trigger was bounces, complaints or both, and the period it covers. Why: an appeal that answers a different problem gets sent back.
  2. Pause every stream that draws on the affected data. Stopping the marketing list isn't enough if transactional sends read the same table. Why: each new bounce during the review is read as the problem still being live.
  3. Write the root cause in one sentence. For example: "An import of 18,000 trade-show leads, never mailed before, was added to the marketing configuration set on 3 March." Why: a specific cause tells the reviewer the problem is understood.
  4. Build the failed set and keep the counts. Include all permanent bounces, all complaints, and transient addresses that failed repeatedly. Save the numbers by subtype. Why: this is the first thing a reviewer checks, and exact counts are more persuasive than "we removed the bad addresses."
  5. Verify everything that remains. An address that didn't fail in this send can still be dead. Why: verification produces per-category numbers, which is what turns "cleaned" into evidence.
  6. Segment the Valid addresses by engagement. Send first to recent openers and clickers. Why: engaged recipients carry the least risk, so your early waves are the cleanest.
  7. Reply and ramp. Answer through the AWS Support case or channel named in your notice, then increase volume in waves, checking each one before the next. Why: a documented ramp shows you will run the plan, not just promise it.

Bottom line: Steps 4 and 5 produce the evidence. Steps 6 and 7 turn it into a case AWS can approve.

Which cleaning method gives the strongest evidence in an appeal?

Verification gives the most complete, quotable picture of the list. Deleting bounced addresses covers only the ones that already failed. Each method has a different strength as evidence.

Method What it catches What it misses Strength in an appeal
Remove only addresses that bounced Addresses from the failed send Every dead address you haven't mailed yet Weak: the rest of the list is untested
Rely on the SES account-level suppression list Permanent bounces and complaints SES has recorded Unmailed bad addresses; catch-all failures that arrive later Moderate: shows automation, not list quality
Bulk verification of the full list Syntax, domain and MX problems, nonexistent mailboxes, disposable and role addresses, catch-all domains Consent and engagement Strong: gives per-category counts you can quote
Re-engagement send to the unverified list Engaged contacts Generates new bounces while AWS is reviewing you Poor during a review
Real-time checks at signup or import Stops new bad addresses entering Doesn't clean the existing list Good as prevention evidence

The strongest appeals combine verification, which asks whether an address is real, with engagement, which asks whether the person wants the mail. Those are different questions, and a reviewer may ask both.

Bottom line: Verify the full list, then segment the Valid addresses by engagement. Don't send to an unverified list while the review is open.

How do you verify the list with Unlimited Verifier?

This is the verification step, using Unlimited Verifier. Plan your file splits before you start, because the per-list cap and monthly deep allowance shape the work. Your email verification pricing depends on how many lists and deep checks you need.

  1. Export the source list and the failed set separately. Include engagement fields such as last open or signup date in the main export. Save bounces and complaints as their own file, so the audit trail stays intact.
  2. Subtract the failed set. Remove every bounce and complaint from the working list, then confirm the remaining count matches your arithmetic.
  3. Sign up and check your plan limits. You can sign up for free. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications, with no API access. Pro is $29 a month, or $25 a month billed annually. It allows lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access for 100,000 emails a month. Standard verification is unlimited on every plan, with no per-email fees.
  4. Split any file over the list cap. On Pro, split anything above 25,000 rows. Files must be CSV or Excel up to 10MB. The email column is detected automatically.
  5. Upload and run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
  6. Read the three buckets. Valid addresses go to your first sends. Invalid addresses are removed and suppressed. Risky addresses, including catch-all domains, disposable addresses and role accounts such as info@, are held back until the main list shows stable results. For how catch-all results are handled, see catch-all email verification.
  7. Export and save the counts now. Export as CSV, Excel or JSON. Free-plan results are kept for 24 hours and Pro results for 30 days, so download the files and store the summary for your appeal.
  8. Re-import the Valid contacts. Unlimited Verifier has no native SES integration, so the step is an export and re-import, or a script that calls the API. Add the Invalid addresses to your own suppression table so your application never tries them again.

To spot-check a single address, such as a key account that came back Risky, use the free email checker.

Bottom line: Subtract the failed set, verify the rest in files under 25,000 rows, keep Valid, suppress Invalid, and save the counts before the results expire.

What does a 60,000-contact SES import look like after cleaning?

This example is illustrative. The verification percentages are hypothetical, but the arithmetic and plan limits are real.

The situation: A SaaS company imported 60,000 contacts from an old trade-show file into its marketing configuration set and sent one campaign to all of them. The results were:

SES flagged the account for review.

Cleaning:

  1. Remove the failed set. For the appeal, remove all 4,200 bounces and all 72 complaints. Nothing overlaps, so 60,000 − 4,272 = 55,728 survivors. Removing the 300 MailboxFull addresses is stricter than a retry-then-suppress policy, and it makes the appeal's base cleaner.

  2. Split for Pro's 25,000 cap: 25,000 + 25,000 + 5,728 = 55,728.

  3. Allocate deep verification. Use the 25,000 monthly deep checks on the oldest-import segment, and run standard verification on the remaining 30,728.

  4. Hypothetical results:

    • Valid: 46,028 (82.6%)
    • Risky: 7,400 (13.3%)
    • Invalid: 2,300 (4.1%)

    Check: 46,028 + 7,400 + 2,300 = 55,728.

  5. Cost: $29 ÷ 55,728 ≈ $0.52 per 1,000 addresses on one monthly Pro plan. On annual billing at $25, it's about $0.45 per 1,000.

Why the Risky count matters: In this illustrative case, the 7,400 Risky addresses are the ones the bounce feed hasn't shown yet. Some of them may accept mail now and fail later, which is why they stay out of the first waves.

Plan comparison:

Re-entry ramp (Valid only):

Wave Audience Wave size Cumulative Bounce ceiling
Day 1 Opened in last 30 days 5,000 5,000 1% (≤ 50 bounces)
Day 3 Opened in last 90 days 10,000 15,000 1% (≤ 100)
Day 7 Remaining engaged Valid 15,000 30,000 1% (≤ 150)
Day 14 Remaining Valid 16,028 46,028 1% (≤ 160)

Hold the 7,400 Risky addresses back. If any wave goes over 1%, pause and investigate before the next one. The best catch-all addresses can go to a small test batch at the end of the ramp.

Bottom line: A single Pro month and a few hours of work turn a vague "we cleaned it" into an audit trail with exact counts.

What should the AWS Support case contain?

A strong case is short, factual and numerical. Include these five items:

Reply through the case or channel named in your notice, and answer exactly what AWS asks. Leave out complaints about your data vendor or unrelated issues. Reviewers respond to ownership and a concrete fix.

Bottom line: Lead with the cause, quote the counts, and commit to a ceiling you can measure.

How long does reinstatement take, and how do you ramp back?

We couldn't confirm a fixed AWS review timeline from public documentation, so don't schedule campaigns against a date. The fastest path is a complete first response that answers the questions a reviewer would ask.

Ramp over one to three weeks. Check the bounce rate on every wave, using your event data and the reputation metrics in the SES console. Don't increase volume until the previous wave has settled.

Mailbox-provider reputation often recovers more slowly than the account review itself. Expect the inbox placement to lag. Does one high-bounce campaign hurt deliverability for weeks? explains that lag.

Bottom line: A complete first response shortens the review. A disciplined ramp protects the account after it.

What are the most common mistakes?

Bottom line: Most failed appeals come from sending too soon, or from claiming a clean list without evidence.

How do you keep SES from flagging you again?

Bottom line: Alert at 2%, verify at the point of entry, and re-verify on a schedule. That combination makes a repeat review unlikely.

How we compared (and limitations)

This guide is based on public documentation: AWS's SES documentation, Google's sender guidelines, RFC 3463 for enhanced status codes, and the FTC's CAN-SPAM guide. We haven't run controlled tests against AWS's review process. Thresholds and bounce-subtype definitions can change, so check the current AWS pages before you act on any figure here.

Unlimited Verifier's plan limits are the company's published facts. The company states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. The worked example's verification percentages are hypothetical, and the arithmetic is shown so you can rerun it on your own data.

For a broader comparison of options, read our roundup of best email verification tools or our guide on how to choose an email verifier.

Illustrative ramp plan with 1% ceiling per wave

Wave Daily volume (example) Max bounce rate allowed Action if exceeded
1 500 verified valid addresses 1% Pause, re-check list, do not advance
2 1,000 verified valid addresses 1% Pause, re-check list, do not advance
3 2,500 verified valid addresses 1% Pause, re-check list, do not advance
4 Remaining verified valid addresses 1% Pause and investigate source

Volumes are illustrative. Advance to the next wave only when the previous wave's bounce rate stays at or below 1%.

Frequently asked questions

What bounce rate triggers an Amazon SES review?

AWS's SES documentation sets 5% as the bounce rate that puts an account at risk of review, and 10% as the level at which sending may be paused. Check the current AWS documentation, since these figures can change. Aim to keep your bounce rate under 2% to leave a safety margin.

How long does an Amazon SES bounce-rate review take?

The timing varies, and AWS does not publish a fixed review period in the material this guide relies on. Your reply quality and the speed of your remediation both affect how quickly the case moves. Check the AWS Support or SES notice for any deadline stated in your account.

Which bounces should I suppress first?

Suppress all permanent bounces and all complaints first. Permanent bounces indicate addresses that will not accept mail, and continued sends to them raise your rate. Keep these addresses off every future send across all configuration sets that share the same data source.

Do complaints count toward the SES review?

Yes, complaint rate is tracked alongside bounce rate and can also trigger review. Remove complainers from your sending lists and honor unsubscribe requests immediately. Include complaint figures in your appeal so AWS sees the full picture.

Should I split bounces by configuration set before appealing?

Yes. Splitting bounces by configuration set and bounce subtype shows which stream or import caused the spike. This lets you explain root cause clearly and prove the problem source is contained, which reviewers look for in a credible appeal.

How do I verify email addresses before sending again?

Use an email verification service to classify addresses before you send, then send first only to addresses marked valid. SES does not check addresses before sending, so verification has to happen in your own pipeline or a third-party tool.

What should my appeal to AWS include?

Include the root cause, counts of addresses removed and suppressed, verification results, and a ramp plan with a 1% bounce ceiling per wave. Keep the message factual and specific. Reviewers respond better to numbers and documented fixes than to general assurances.

Can I ramp sending volume after a bounce-rate review?

Yes, ramp gradually in waves, checking bounce rate after each wave before increasing volume. Stop the ramp if any wave approaches your 1% ceiling. Sending full volume immediately after remediation risks a repeat review.

Will removing bounced addresses fix my bounce rate on its own?

Removing bounced addresses stops repeat bounces to known bad addresses, but it does not fix an upstream problem such as a bad import or stale sync. Confirm that the source feeding your list is corrected, or new bad addresses will keep arriving.

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.