Article
5 Steps to Take After a Bounce Rate Spike
By Unlimited Verifier Team ·

Summary
After a bounce rate spike, pause sends to the affected segment, separate hard bounces from blocks, suppress hard bounces permanently, verify the affected list, and then re-warm in small batches. Keep hard bounces under 1% per send while you recover.After a bounce rate spike, take five steps in order: pause sends to the affected segment, split hard bounces from blocks, suppress hard bounces permanently, verify the affected list before sending again, then re-warm in small batches while holding hard bounces under 1% per send. For the verification step, Unlimited Verifier fits well because its standard checks are unlimited on every plan, including Free. This guide is for marketers, list owners, agencies and SaaS teams whose ESP has reported a jump in bounces, or who want to stop one before an account review starts. If your account is already under review, read our high bounce rate account suspension guide first, then come back here.
Quick answer
- Contain first: pause the campaign or automation hitting the spiking segment before you diagnose anything.
- Split hard from soft: permanent failures point to the list. Blocks and reputation messages point to your sending, and they need a different fix.
- Suppress hard bounces permanently and make sure they never come back through a re-import.
- Verify the affected list before the next send, using a tool that sorts addresses into Valid, Risky and Invalid.
- Re-warm in batches and keep hard bounces under 1% per send.
Which step should you do first?
Do steps 1 through 3 on the same day. They cost nothing and stop further damage while you work out the cause. Step 4 fixes the list, and step 5 keeps the spike from coming back.
Quick picks
- Fastest containment: Step 1. It takes minutes and stops new bounces from that segment.
- Most useful diagnosis: Step 2. It tells you whether you have a list problem or a reputation problem, and the fixes are different.
- Best value for large imports: Step 4 on a plan with unlimited standard checks, so re-checking during clean-up doesn't add per-email cost.
- Best long-term prevention: Step 5, combined with checking addresses at signup.
Bottom line: the first three steps are free and limit the damage, so start them the same day you see the spike.
What are the 5 steps side by side?
| Step | Do it when | Main output | Cost | Owner |
|---|---|---|---|---|
| 1. Pause affected sends | Within the hour of the spike | No new bounces from that segment | $0 | Campaign owner |
| 2. Diagnose the cause | Same day | Root cause: list, source, domain or reputation | $0 | Deliverability or ops |
| 3. Suppress hard bounces | Same day | Permanent suppression list | $0 | List owner |
| 4. Verify the affected list | Within 48 hours | Valid, Risky and Invalid decisions | Free or Pro plan | List owner |
| 5. Re-warm and monitor | Next 2–4 weeks | Bounce rate under 1% per batch | $0 extra | Campaign owner |
Bottom line: the table shows who does what and when, but the order matters more than the labels.
How we compared (and limitations)
We ordered these steps by four criteria: how quickly each one stops further damage, how directly it addresses the cause of the spike, what it costs, and whether you can undo it if you get it wrong. Where we describe verification features, we rely on Unlimited Verifier's public documentation.
Limitations. We did not run a controlled test of these steps against real bounce data. The worked numbers are illustrative. ESP thresholds for account reviews differ and change over time, so check your provider's current policy. Accuracy figures are vendor claims. Verification removes addresses that will fail, but it can't tell you whether the remaining subscribers want your mail.
Bottom line: these criteria favor cheap, reversible actions first, which is why containment comes before cleaning.
What are the 5 steps to take after a bounce rate spike?
1. Pause sends to the affected segment (within the hour)
Pause the campaign, automation or import producing the spike. Don't wait for a full diagnosis, because every additional send to the same contacts adds bounces against your sending reputation.
First, measure the spike correctly. Bounce rate is usually bounces divided by emails sent for that campaign. Some ESPs use delivered as the denominator instead, so check which one your dashboard uses before you compare numbers to a threshold. As a working rule, we treat a jump of more than one percentage point over your normal baseline as a spike. That is our definition, not an industry standard.
Key features (what to check first)
- Which campaign, automation or import produced the spike
- Whether it was one send or a trend across several
- Whether automated emails are still queued to the same segment
Pros
- Stops new bounces while you investigate
- Costs nothing and takes minutes
Cons
- Pause marketing streams only. Pausing transactional email, such as password resets or receipts, can break things for customers.
- Queued automations may resume with stale timing, so review them before unpausing.
Best for: anyone with scheduled sends to a list that recently changed.
Where it falls short: pausing contains the problem but doesn't fix it.
Pricing: no cost beyond your ESP plan.
Tip: if your ESP has already flagged the account, check the provider-specific guides: Mailchimp suspended my account for bounces: what now, SendGrid account under review for bounce rate or Brevo account suspended for high bounce rate. For the thresholds providers use, see what bounce rate gets your ESP account suspended.
2. Diagnose whether the bounces are dead addresses or blocks (same day)
Split the bounces before you act on them. Export the bounce log, then separate hard bounces (permanent failures, usually SMTP 5xx reply codes) from soft bounces (temporary failures, usually 4xx). The meaning of those reply codes is defined in RFC 5321.
Key features (what to split by)
- Hard versus soft, and the reply text. "User unknown" points to dead addresses. Wording about blocking, reputation or policy points to your sending, not your list.
- Source: import date, signup form or campaign tag.
- Domain: a cluster of failures at one provider or company domain.
- Typos: domains like gmial.com or yaho.com. Correct these rather than deleting the contacts.
Pros
- Tells you whether the fix is list cleaning or reputation work.
- Often points to one import or one domain, which makes the problem small enough to fix.
Cons
- Some ESPs show bounce reasons only for a limited window, so export logs early.
- Diagnosis reads symptoms, not mailboxes. It can't confirm whether an address is dead; that's the verification step's job.
Best for: teams that imported old lists or bought contacts.
Where it falls short: a clean-looking breakdown can still hide a reputation problem that shows up in soft bounces and complaints.
Pricing: no cost.
Worked example. A 12,000-recipient campaign produced 816 bounces, a 6.8% rate. Split by type, that was 602 hard bounces (5.0%) and 214 soft bounces (1.8%). Split by source, a 4,000-contact import accounted for 540 hard bounces, or 13.5% of that segment. The other 8,000 contacts produced 62 hard bounces, or 0.78%. The problem was the import, not the whole list. A spike that starts within 24 to 48 hours of an import often points the same way. A spike spread across every segment, with rising soft bounces, is more likely a reputation problem. That calls for why did my bounce rate jump after importing a list rather than a clean-up alone.
Tip: export the bounce log as CSV before changing anything, and keep the file. If your next import is still pending, read how to avoid ESP suspension when importing old lists before loading it.
Bottom line: if the bounces cluster by source, you have a list problem; if they spread everywhere, you have a sending problem.
3. Suppress every hard bounce permanently (same day)
Add every hard bounce to a permanent suppression list that applies across all your lists. Soft bounces are different. Retry them, and treat an address as hard only after repeated failures. Many ESPs apply a retry rule by default, so check yours. Blocks are not dead addresses, so don't suppress contacts because of a reputation block. Doing that removes real subscribers and leaves the cause untouched.
Key features (rules to set)
- Hard bounce: suppress permanently across every list
- Soft bounce: retry, then suppress after repeated failures
- Block or reputation message: hold and diagnose, don't suppress as invalid
Pros
- Stops repeat sends to known-dead addresses
- Protects against the common error of re-importing an old file that brings them back
Cons
- Suppression only works if it travels with the list. If you export to another tool or re-import from an older backup, suppressed addresses can return.
- Opt-outs are a separate legal duty. The FTC's CAN-SPAM compliance guide says opt-out requests must be honored within 10 business days, so keep opt-outs on the same suppression record.
Best for: every sender. This is the baseline of email verification compliance and hygiene.
Where it falls short: it only covers addresses that have already bounced. Addresses that will bounce next time are caught in step 4.
Pricing: no cost.
Tip: keep one master suppression export and load it before every import.
Bottom line: suppression is only as good as the copy you re-import from, so keep one master list.
4. Verify the affected list before you send again (within 48 hours)
This is where the list gets fixed. A verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and sorts each address into Valid, Risky or Invalid. Risky matters because catch-all domains accept mail for any address at SMTP time, so a basic check can't confirm that a specific mailbox exists. Catch-all email verification explains how Unlimited Verifier handles those domains.
Key features
- Valid, Risky and Invalid sorting, with disposable and role-based addresses flagged
- CSV or Excel upload up to 10MB, with the email column detected automatically
- Export as CSV, Excel or JSON
- Deep verification for addresses that need extra scrutiny. Unlimited Verifier states 99.5% accuracy for deep verification. That is the vendor's claim, so test it on a sample from your own list.
Worked example. Take the 4,000-contact import from step 2. Suppose verification returns 3,350 Valid, 110 Risky and 540 Invalid (3,350 + 110 + 540 = 4,000). The 540 Invalid is close to the 13.5% hard-bounce rate you observed, which is a useful sanity check. If your invalid share differs sharply from your observed hard-bounce share, manually check 50 to 100 addresses with the free email checker before trusting the result.
Now check the limits. On Free, each list holds up to 150 emails and you get 25 lists a month. That is 3,750 emails of capacity a month, which is less than 4,000. Splitting the import needs 27 files, so it can't finish in one month on Free. Free results are also kept for only 24 hours. On Pro, the same 4,000 contacts fit in one list (the cap is 25,000 per list), and Pro includes 25,000 deep verifications a month. The 110 Risky addresses fit within Free's 750 monthly deep verifications, so Free can cover that part.
Pros
- Flat, unlimited standard verification means re-checking doesn't add per-email cost. This matters during a clean-up, when you may check the same file more than once.
- The three buckets map directly to send, suppress and segment decisions.
Cons
- No native ESP, CRM or Zapier integration, so this is a CSV export, verify and re-import loop, or an API call.
- Lists must be split to fit per-list caps.
- Pro results are kept for 30 days, so download your exports.
Best for: senders whose spike traces to an import or an old list.
Where it falls short: it can't see engagement. A Valid address can still be disengaged, and no verifier can predict spam traps with certainty.
Pricing: Free is $0. Pro is $29/month or $25/month billed annually. The flat model is one way to think about email verification pricing, since per-credit tools charge again for each re-check.
Tip: spend deep verifications on the Risky bucket. Addresses already marked Valid rarely need them.
Bottom line: verification fixes the list, but only if you act on all three buckets, not just the Valid ones.
5. Re-warm with small batches and watch each send (next 2–4 weeks)
After cleaning, return to volume gradually. Send the Valid addresses to a small, engaged batch first, check the bounce rate, then ramp up. Keep the target under 1% hard bounces per send. Many ESPs flag hard-bounce rates around 2%, so a 1% working target leaves headroom before a provider intervenes. There is no single industry-wide hard-bounce cap, so the binding limit is usually your ESP's policy.
Worked example. Of the 3,350 Valid addresses, send 1,000 first. At 1%, that batch can produce no more than 10 hard bounces. If it stays under that, send the remaining 2,350 in two batches of about 1,175. Send the 110 Risky addresses last, and only to contacts who opened or clicked recently. The 90-day window is our suggestion, not a standard.
For complaint thresholds, Google's email sender guidelines set a spam rate ceiling of 0.3% in Postmaster Tools and recommend staying under 0.1%. Bounces and complaints are different signals, but a list with many invalid addresses often has abandoned inboxes that generate complaints too. Yahoo's sender best practices cover similar expectations.
To stop the spike from returning, check addresses at entry with real-time email validation and verify every import before its first send. Subscription products can apply the same discipline described in email verification for ecommerce and SaaS.
Pros
- Low risk, and it generates the data you need to decide the next batch.
- Costs nothing beyond the time to review results.
Cons
- Slows reach for a week or two. Reach comes back once the batches are clean.
- Large lists take longer to re-warm, which is why batching helps.
Best for: large lists returning to normal volume.
Where it falls short: if small batches still bounce heavily, the problem is reputation or infrastructure, not the list.
Pricing: no extra cost.
Tip: log the bounce rate per batch in a spreadsheet. The trend across batches tells you more than any single send. For the full timeline, see how to warm up an old email list after cleaning and does one high-bounce campaign hurt deliverability for weeks.
Bottom line: verify before you send, then return to volume in measured batches, because a clean list still has to earn back trust one send at a time.
How do you verify a bounced list with Unlimited Verifier?
This tutorial covers step 4 from start to finish. Once the file is exported, it takes about 20 minutes for a small list. For the wider process, see email list maintenance best practices.
- Export the affected contacts from your ESP as CSV. Include the email column and any tag that identifies the source.
- Split the file if needed. On Free, keep each file at 150 emails or fewer and plan for 25 lists a month. On Pro, each list can hold up to 25,000 emails.
- Sign up and choose Free for small lists or Pro for large ones.
- Upload the file. The email column is detected automatically. Files can be up to 10MB.
- Review the three buckets. Valid goes to the send list, Invalid goes to suppression, and Risky goes to a separate segment.
- Run deep verification on Risky if you have allowance left. Free includes 750 a month; Pro includes 25,000.
- Export as CSV, Excel or JSON. On Free, download within 24 hours, because results are kept only that long. Pro results are kept for 30 days.
- Re-import into your ESP. Add Invalid to suppression, tag Risky, and schedule Valid in batches.
- Automate later. On Pro, the email verification API supports single checks and batches of up to 10,000 emails per request, within a 100,000-email monthly allowance. That's the starting point for email verification API and automation. API access is not available on Free.
Bottom line: the file round-trip is manual, but for a one-time clean it's fast and leaves you with three clear decision lists.
Which step matters most for your situation?
| Your situation | Start with | Then |
|---|---|---|
| Spike started within 48 hours of an import | Steps 1 and 2 | Step 4 on the imported segment |
| Bounce logs say "blocked" or "reputation" | Step 1 | Step 2 (reputation work), not mass suppression |
| Spike across every segment, gradual rise | Step 2 | Step 4 on the full list, then Step 5 |
| ESP has sent a warning or review notice | Step 1 | The account-specific guide, then Steps 3–5 |
| Small list, under 150 contacts | Steps 1–3 | Free plan for Step 4 |
| Legacy list, older than two years | Steps 1–3 | Step 4 on the whole list, then Step 5. See is it safe to email a list that is two years old |
For a broader comparison of verification options, see our guide to the best email verification tools, and for evaluating a provider, how to choose an email verifier. If you run a Mailgun account, the Mailgun high bounce rate warning fix covers provider-specific steps.
Bottom line: match your first move to the bounce pattern you see, not to the size of the spike.
What mistakes make a bounce spike worse?
- Deleting soft bounces immediately. Many soft bounces are full mailboxes or temporary server issues. Retry them before you suppress.
- Treating block bounces as dead addresses. A reputation block suppresses real subscribers and doesn't fix the cause.
- Re-importing without suppression. If the suppression list isn't loaded first, the next import brings the bad addresses back.
- Sending the full cleaned list at once. Large first sends after a spike can recreate the problem. Batch them.
- Deleting every Risky address. Catch-all domains often contain real people. Segment by engagement instead.
- Skipping the consent check. Verification doesn't make a purchased or scraped list lawful. For UK and EU audiences, see the ICO's guidance.
- Trusting accuracy claims without sampling. Test any vendor's claim, including Unlimited Verifier's 99.5% deep-verification figure, against a sample from your own list.
- Waiting for a review notice. Once an ESP flags your account, your options narrow.
For the sender standards behind these steps, M3AAWG publishes industry best practices for messaging.
Bottom line: most spikes get worse through process errors, such as re-importing or sending too much at once, rather than through the original problem.
Verdict
After a bounce rate spike, containment comes first: pause the segment, split hard bounces from blocks, and suppress the hard ones permanently. The list fix comes next, which means verifying the affected segment before you send to it again. Then return to volume in batches, keeping hard bounces under 1% per send.
For the verification step, Unlimited Verifier's flat model suits this work. Standard checks are unlimited on every plan, Valid/Risky/Invalid sorting shows you what to send and what to suppress, and Pro adds 25,000-email lists and API access for ongoing checks. Its main limitation is the manual file round-trip, since it has no native ESP integrations.
Bottom line: start this week's clean-up on the Free plan with the affected segment, and move to Pro when a file exceeds 150 emails, you run out of monthly list allowance, or you need the API.
Worked example: 1% hard-bounce cap
Suppose a segment of 5,000 addresses is due for a re-warm send.
| Item | Value |
|---|---|
| Planned send | 5,000 emails |
| Hard-bounce cap (1%) | 50 bounces maximum |
| Hard bounces observed | 90 (1.8%) |
| Action | Pause, suppress the 90, verify the rest, resend in batches of 1,000 |
Because 90 is above the 50 cap, the send does not go out. After suppression and verification, the next 1,000-address batch is checked against the same cap before the next batch is released. These figures are illustrative.
Frequently asked questions
What is a bounce rate spike?
A bounce rate spike is a sudden jump in the share of emails your sending platform reports as undeliverable compared with your usual baseline. It often follows a large list import, an old segment being mailed again, or a change in sending reputation. Spikes matter because providers may limit or review accounts that keep bouncing.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as a non-existent address or a retired domain, and the address should be suppressed. A soft bounce is temporary, such as a full mailbox or a server timeout, and may succeed later. Blocks and reputation messages are a separate category that points to your sending rather than your list.
How do I know if the spike is a list problem or a reputation problem?
Check the bounce messages. Permanent user-unknown or invalid-domain errors usually point to list quality, while block, reputation or policy messages point to how you are sending. Compare which segments, sources and sending domains are affected. The fixes differ, so diagnose before changing your send strategy.
Should I suppress soft bounces as well as hard bounces?
Not usually at first. Hard bounces should be suppressed permanently. Soft bounces can be retried a limited number of times, and addresses that keep soft bouncing can then be suppressed. Follow your ESP's documented retry policy, since some platforms handle soft-bounce suppression automatically.
Can I email hard-bounced addresses again after fixing the problem?
In most cases, no. A hard bounce means the mailbox or domain is permanently unreachable, so re-sending wastes reputation and can increase future bounces. Keep them suppressed, including through re-imports, unless the contact gives you a confirmed new address.
How long does re-warming take after a bounce spike?
Re-warming usually takes a few weeks of gradually increasing volume to engaged, verified recipients. The exact timeline depends on how severe the spike was and your provider's guidance. Keep hard bounces under 1% per send during this period and pause again if the rate climbs.
Does verifying my list stop future bounce spikes?
Verification helps by flagging invalid and risky addresses before you send, which lowers the chance of hard bounces. It does not replace good list practices. Check addresses at signup, avoid buying lists, and keep suppression rules applied across every import and integration.
What should I do if my account is already under review?
Start with your provider's account review or suspension guidance, because review processes and thresholds differ between platforms. Pause sends, document your clean-up steps, and respond to the provider with specific actions taken. Then follow the steps in this guide to bring bounce rates back under control.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.