Article
Bounce Rate Suddenly Spiked? What to Do in the First 24 Hours
By Unlimited Verifier Team ·

Summary
A sudden bounce rate spike usually comes from mailing a segment with dead addresses or from a change in your sending setup. Pause the affected sends first, then sort bounces by SMTP code, segment and date to find the cause. Calculate rates per segment rather than per account to isolate the problem quickly.A sudden bounce rate spike usually means you mailed a segment full of dead addresses or changed your sending setup. Pause the affected sends, then sort bounces by SMTP code and segment. Treat any single send above 2% bounces as urgent until you know the cause.
Quick answer
- Pause the affected segment now. Every extra send to a bad list adds bounces and weakens your position with your ESP and with mailbox providers.
- Sort bounces by SMTP code. Permanent
5.x.xcodes such as5.1.1mean dead addresses. Temporary4.x.xcodes, including4.7.0, usually mean throttling or a reputation block. - Pivot by source, import date and recipient domain. If one batch or one domain causes most bounces, the problem is the list. If bounces are spread across everything, check your sending setup.
- Remove hard bounces, verify the rest, and re-enter in stages. Aim for under 1% bounces on the first sends back, and keep 2% per send as the ceiling.
What should I do in the first 24 hours after a bounce spike?
Pause the affected segment, export your bounce data with codes and timestamps, then calculate rates per segment before you change anything else. Each step narrows the cause.
- Pause the segment (first hour). Stop the campaign and any automation that targets the same contacts. Do not resend "to catch the people who missed it." Note the exact send time, because that timestamp helps you find the cause.
- Export the bounce report (1–2 hours). Include the email address, SMTP code or bounce reason, timestamp and campaign name. Bounce data can keep updating for hours after a send, so export again later and compare the counts.
- Calculate rates per segment, not per account (2–4 hours). This is the most common analytical mistake. Suppose you send 40,000 emails and 1,000 bounce. Your overall rate is 2.5%. But if 860 of those bounces came from a 9,000-contact segment, that segment bounced at 9.6%, while the other 31,000 contacts bounced at 0.45%. The problem is one segment, not the whole list.
- Review what changed in the last 7–14 days. Check imports, new signup forms, DNS edits, a move to a new sending domain or ESP, new automations, and any team member who started sending.
- Check your account status. Read any notice from your ESP and note whether it names a campaign, a threshold or a metric. If you are already restricted, follow the reinstatement appeal process.
For a shorter version of this sequence, see the five-step post-spike checklist.
Bottom line: Stop sending, then calculate bounce rates by segment and review what changed before you decide anything.
How do I tell a list problem from a sending problem?
Concentrated bounces point to the list. Bounces spread across segments that start on one date point to your sending setup. The table below maps common patterns to the first check to run.
| Pattern in your bounce data | Most likely cause | First check |
|---|---|---|
| Bounces concentrated in one import batch or source | Stale, purchased or scraped list | Bounce rate by import date and source |
| One recipient domain makes up most bounces | Company shut down, was acquired, or moved its mail domain | Group bounces by domain and check its MX records |
| Bounces across all segments, starting on one date | Broken SPF, DKIM or DMARC, or a sending IP or domain on a blocklist | Authentication records, then a blocklist lookup on Spamhaus |
Mostly soft bounces with 4.7.0 after a volume increase |
Throttling or reputation deferral | Send-rate history; slow down rather than delete |
| Bounces on contacts created in the last 48 hours with random-looking addresses | Bot signups through an unprotected form | Signup source and form submission logs |
| Sends to old contacts at unexpected times | Duplicated or re-triggered automation | Automation run history |
As a working rule, if one batch or one domain accounts for more than half of the bounces, investigate the list first. This threshold comes from practice rather than a published standard. It is useful because list problems tend to concentrate in one place.
Authentication problems need special attention. A common pattern is a DNS change that drops the include for your new sending service from your SPF record. Bounces then appear across every segment on the same day. Check your DNS change log before you clean anything, because cleaning will not fix a sending-side fault. If you send through Mailgun, its bounce warning fix guide covers the platform-specific checks.
Bottom line: Bounces concentrated in one place point to the list. Bounces spread across segments that start on one date point to your sending setup.
What do the bounce codes actually tell me?
The first digit of an SMTP enhanced status code tells you whether the failure is temporary (4) or permanent (5). The second digit identifies the subject: addressing (5.1), mailbox (5.2), or security and policy (5.7). RFC 3463 defines this format.
| Code | What it usually means | Action |
|---|---|---|
5.1.1 |
Mailbox does not exist | Suppress permanently |
5.2.2 |
Mailbox full, reported as permanent | Suppress if it repeats across sends |
4.2.2 |
Mailbox full, temporary | Retry later; suppress after repeated failures |
4.7.0 |
Temporary block or rate limit | Reduce send speed; keep the contacts |
5.7.1 |
Policy refusal, often reputation or authentication | Investigate your sending side, not the list |
ESPs display these codes differently, and many collapse them into a single "bounced" label. Always use the raw code from your bounce log. A dashboard label can hide a 5.7.1 that tells you your domain is the problem.
Many teams suppress a contact after three consecutive soft bounces. This is a convention rather than a standard, but it is a sensible limit because a mailbox that keeps deferring is effectively dead.
Bottom line: Permanent 5.x.x codes are a list problem. Temporary 4.7.0 and 5.7.x codes are a sending problem, and deleting contacts will not fix them.
Should I keep sending while I investigate?
No, not to the affected segment. More sends to a list that just spiked add bounces and make your ESP's review harder. For the full picture of how platforms escalate, read our pillar guide on high bounce rate account suspension.
Sources disagree on exact thresholds. Amazon SES's documentation describes reviewing an account at a 5% bounce rate and possibly pausing it at 10%. Other platforms act at lower levels, especially on a single campaign to an unproven list. Google's sender guidelines address spam complaints rather than bounces. They set 0.3% as the level to stay below and recommend aiming under 0.1%.
Our recommendation is to treat 2% bounces on any single send as the ceiling. Pause anything above it, and investigate anything above 1%. Automated triggers vary by platform and are rarely published, so a 2% ceiling leaves room before most of them engage.
If the spike is in marketing mail, check whether transactional messages, such as password resets or receipts, share the same sending domain or list. Those messages rarely cause bounces, but they share the domain's reputation, so a marketing problem can affect them too.
For platform-specific behaviour, see our guides on Mailchimp suspensions, SendGrid's under-review status and Brevo bounce suspensions. For the thresholds in more depth, see what bounce rate gets your ESP account suspended.
Bottom line: Stop sending to the affected segment, and use 2% per send as your ceiling.
How do I find the exact segment that caused the spike?
Join your bounce export to a contact export that records where each contact came from. This takes a spreadsheet and roughly an hour for most lists under a few hundred thousand rows.
- Export bounces from your ESP with the email, code, timestamp and campaign.
- Export contacts with the email plus any field that shows origin: import batch, signup form or date added.
- Join the two files on the email column using
XLOOKUPorVLOOKUP. Each bounce now has a source. - Count bounces and sends by source and by month added. Divide bounces by sends for each group to get a rate per group.
- Pivot by recipient domain. Split each address at the
@and count the top 20 domains. Look for any domain that appears far more often among bounces than in your list. - Save the worst group as a separate file. This is the file you will verify.
The result is evidence you can show a client, a manager or an ESP reviewer.
Bottom line: Joining bounces to contact sources shows you which batch, form or domain is responsible.
How should I clean the affected list?
Verify the affected segment, suppress Invalid addresses, and hold Risky addresses back until you have evidence. Each cleaning option leaves a different amount of risk behind.
| Option | What it removes | Risk during a spike | When to use it |
|---|---|---|---|
| Delete only addresses that bounced | Addresses already failed | Leaves untested addresses in place | Minimum step; never sufficient alone |
| Resend to the segment to "see who's left" | Nothing reliable | Creates more bounces | Never during a spike |
| Verify, then remove Invalid | Syntax errors, dead domains, nonexistent mailboxes | Low, because no campaign is sent | Default first step |
| Verify, then hold Risky | Catch-all, disposable and role addresses until you have proof | Low, if held back | Before any re-entry |
| Sunset by inactivity | Long-dormant contacts | Removes some real people | Ongoing policy after the cleanup |
Verification is the only option that checks the whole list without sending mail. Start with the affected segment, then move to the rest of the list.
How to verify the list with Unlimited Verifier
- Export the affected segment as a CSV. Keep the email column and the source field so you can match results back later.
- Sign up if you have not already. The Free plan includes 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Free results are kept for 24 hours, so export them the same day.
- Upload the file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains, disposable addresses and role-based addresses are flagged.
- Read the three buckets. Valid addresses are safe for re-entry. Invalid addresses should be suppressed permanently. Risky addresses include catch-all domains, which accept every address, so a specific mailbox cannot be confirmed. Hold Risky addresses back.
- Export the results as CSV, Excel or JSON, and save the counts.
- Re-import Valid contacts to your ESP as a new segment, and add Invalid addresses to its suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this export-and-re-import step is manual unless you call the API from your own scripts.
For a single address, such as a key customer who came back Risky, the free email checker gives a quick result. Standard verification is unlimited on every plan, so you can re-run a list after each fix at no extra cost. Deep verifications are the monthly quota: 750 on Free and 25,000 on Pro.
Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, so check results against your own bounce data.
Bottom line: Verify before you send, suppress Invalid, hold Risky, and keep the counts for your records.
Worked example: a 40,000-send campaign with a 2.5% spike
The numbers below are hypothetical. The arithmetic and plan limits are real.
What happened: A campaign went to 40,000 contacts and produced 1,000 hard bounces. That is 1,000 ÷ 40,000 = 2.5%, above the 2% ceiling.
Where the bounces came from:
- A 9,000-contact segment imported three weeks earlier produced 860 bounces. 860 ÷ 9,000 = 9.6%.
- The other 31,000 contacts produced 140 bounces. 140 ÷ 31,000 = 0.45%.
One segment caused the spike. The rest of the list is behaving normally, so it does not need the same treatment.
Cleaning and verification:
- Suppress the 1,000 hard bounces so they are never mailed again.
- Run deep verification on the 9,000 imported contacts as one list. That fits under the Pro plan's 25,000-per-list limit and uses 9,000 of the 25,000 monthly deep verifications, leaving 16,000.
- Run standard verification on all 40,000 contacts in two lists, 25,000 and 15,000, to satisfy the per-list cap. Standard verification is unlimited, so this adds no cost.
- Check whether Free works. Free allows 25 lists × 150 emails = 3,750 addresses a month. A 9,000-row segment cannot fit on Free, so this job needs Pro at $29 for one month, or $25 a month billed annually ($300 a year).
Hypothetical results for the imported segment:
- Valid: 6,300 (70%)
- Risky: 1,800 (20%)
- Invalid: 900 (10%)
Check: 6,300 + 1,800 + 900 = 9,000.
Re-entry plan for the 6,300 Valid contacts (most engaged first):
| Day | Cumulative audience | Bounce target | Maximum bounces at target |
|---|---|---|---|
| 1 | 1,000 most recent engagers | Under 0.5% | 5 (0.5% × 1,000) |
| 4 | 3,000 | Under 0.5% | 15 (0.5% × 3,000) |
| 8 | 6,300 (all Valid) | Under 1% | 63 (1% × 6,300) |
The 1,800 Risky contacts stay out until the main list shows stable results. The best catch-all addresses can then go in a small test send. The 31,000 healthy contacts stay on their normal schedule once their Invalid addresses are suppressed.
Bottom line: The arithmetic shows one segment caused the spike, and the fix costs one Pro month plus about an afternoon of work.
How do I know the spike is over and when can I send again?
Return to full volume only when three conditions hold: the root cause is fixed, your last few sends to the cleaned audience each stayed under 1% bounces, and complaints stay below 0.1%.
Fixing the cause means correcting the DNS record or removing the bad import. Your last few sends matter more than the first one, because a single good send can hide a remaining problem in a small segment.
Mailbox providers recover more slowly than your dashboard does. Expect a period of cautious inbox placement after a major spike. Our article on whether one high-bounce campaign hurts deliverability for weeks explains that lag.
If your ESP has already restricted your account, a complete first message with counts and a plan usually moves the review along faster than waiting.
Bottom line: Do not return to full volume until the cause is fixed and your last several sends have stayed under 1%.
How do I stop the next spike from happening?
Verify data at the three points where it enters your system, then monitor every send.
- At signup: Add real-time email validation to your forms. Unlimited Verifier's REST API supports single-email checks, and Pro includes API access for 100,000 emails a month. Bulk requests accept up to 10,000 emails each.
- At every import: Verify before upload, and treat each new batch as a risk until its results show otherwise.
- On a schedule: Re-verify the full list monthly or quarterly. Lists decay as people change jobs or abandon addresses. Our guide to email list maintenance sets out a schedule.
- In every send: Set an alert at 1% bounces and a pause at 2%. Recheck SPF, DKIM and DMARC after any DNS change.
Before you reactivate an older list, follow the process for sending to an old email list safely. If you are moving providers, check emails bouncing after switching email providers, because a clean list still fails on a misconfigured domain.
If you are comparing verification options, our guide to choosing an email verifier explains what to look for. For a wider comparison, read our roundup of the best email verification tools. The email verification pricing entry shows how plan limits change the cost of a real job. If you send to ecommerce or SaaS audiences, the email verification for ecommerce and SaaS entry covers the signup patterns that most often cause spikes. For automating checks, the email verification API and automation entry describes common workflows.
Bottom line: Verify at signup and import, re-verify on a schedule, and alert on every send.
Common mistakes that turn a spike into a suspension
- Resending the failed campaign to "catch people who missed it." This adds bounces to the same dead addresses.
- Using the account-wide average to judge the problem. A 2.5% overall rate can hide a 9.6% segment.
- Deleting contacts with
4.7.0bounces. Those are throttling signals, and slowing down fixes them. - Blaming the ESP without checking your own list and authentication records.
- Cleaning only the bounced addresses. Untested addresses remain on the list.
- Letting Free-plan results expire. Free results are kept for 24 hours, so export them the same day.
- Re-importing Invalid addresses because they look like real customers in your CRM.
- Treating verification as proof of consent. A valid address is not an opted-in address. Review how the list was collected, and use email verification compliance and hygiene as a checklist. The FTC's CAN-SPAM compliance guide sets the baseline for US commercial email.
- Diagnosing from a dashboard label instead of the raw SMTP code.
Bottom line: Most avoidable damage comes from sending again before you know the cause.
How we compared (and limitations)
This article is based on public documentation: RFC 3463 for enhanced status codes, Amazon SES's published thresholds, Google's sender guidelines and Google Postmaster Tools documentation, and Spamhaus's blocklist lookup. We have not tested any ESP's review process. Thresholds and response times change without notice, so check your platform's current documentation.
The Unlimited Verifier details come from the company's published plan facts. The 99.5% accuracy figure is the company's own statement. The verification engine is also open source at github.com/unlimitedverifier/free-email-verifier, so you can inspect the checks yourself. The worked example uses hypothetical numbers. The 2% ceiling and 1% alert level are our recommendations, not platform rules.
Bottom line: Use the codes, thresholds and cleanup steps here as a starting point, then confirm them against your own bounce data and your ESP's current rules.
Segment bounce rate calculation
You send 40,000 emails and 1,000 bounce, an overall rate of 2.5%. But 860 of those bounces come from a 9,000-contact segment, so that segment bounced at 9.6%. The other 31,000 contacts bounced at about 0.45%. The fix is to pull the 9,000-contact segment, not the whole list.
Frequently asked questions
What is a good bounce rate?
Most email teams aim for a hard bounce rate under 1% per send. Treat anything above 2% on a single send as urgent. Your ESP's acceptable-use policy may set its own threshold, so check that too.
What does SMTP code 5.1.1 mean?
A 5.1.1 code means the recipient address does not exist. It is a permanent failure, so remove that address from your list immediately and do not retry it.
What does SMTP code 4.7.0 mean?
A 4.7.0 code is a temporary failure, often from throttling or a reputation block. Slow your sending, wait, and check whether the bounce persists before retrying.
Should I resend emails that bounced?
No. Resending to hard-bounced addresses adds more bounces and damages sender reputation. Only retry soft bounces, and only after the cause is fixed.
Can a bounce spike hurt deliverability?
Yes. High bounce rates can push mailbox providers to filter your mail to spam and can get your ESP to restrict or suspend your account.
How long do bounces take to show up?
Some bounce reports keep updating for hours after a send. Export your data again later and compare counts before drawing final conclusions.
Should I check SPF, DKIM and DMARC after a bounce spike?
Yes, if bounces are spread across many segments and started on the same date. Broken authentication or a blocklisted sending IP or domain can cause widespread failures.
How do I re-enter sending after fixing a bounce problem?
Start with your most engaged, verified contacts, keep bounces under 1% on early sends, and expand in stages while monitoring each send's bounce rate.
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.