Updated · 8 min read
Bounce rate management: the thresholds and the fix order
Every deliverability dashboard has a bounce chart. Most lifecycle teams glance at it, see a number under 2%, and move on. But bounce rate has texture — hard vs soft, by ISP, by cohort — and the texture is where the operational decisions live.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Hard vs soft — and why it matters
Bounce rate is the fastest-moving deliverability signal you have. Complaint rate is slower but nastier when it shifts — by the time complaints move, the reputation is already in the hole.
Hard bounces are permanent. The address doesn't exist, has been disabled, or is otherwise unreachable. Treatment: immediate permanent suppression. Covered in the list hygiene policy. No retries. Retrying a hard bounce is one of the cheapest ways to damage sender reputation — a permanent negative signal you're paying to re-send.
Soft bounces are temporary. Mailbox full, server briefly unavailable, greylisting. Retry a reasonable number of times, then suppress after repeated failures. Three consecutive is the operator default.
Here's the gotcha: some providers report soft bounces that are actually persistent. A mailbox that's been full for six months isn't getting emptied. When an address has soft-bounced on every send for three months or more, treat it as hard regardless of what the provider category says.
The thresholds that matter
< 2%
Healthy total bounce rate. Below this, no action needed.
2–5%
Warning zone. Investigate acquisition channels; audit recent imports.
> 5%
ISPs start rate-limiting. Gmail and Yahoo may temporarily block further sending.
These are cumulative across recent sends, typically a 30-day rolling window. A single send with a 10% bounce rate on a badly-targeted broadcast doesn't break you if the rest of the program is healthy. A rolling average above 5% does — and once ISPs start rate-limiting, everything else gets harder at the same time.
The deliverability guide covers the broader connection between bounce rates and sender reputation. Bounce rate is the fastest-moving indicator; complaint rate is slower but more damaging when it moves.
The five causes, in order of frequency
1. Stale list data. The single most common cause. Addresses that were valid 18 months ago have been abandoned, disabled, or rotated. Fix with an aggressive sunset policy plus validation on any long-dormant segment before sending to it. Usually shows up as a gradual climb, not a sudden spike.
2. Bad acquisition.An import from a legacy source. A promotion that accepted fake emails. A co-marketing deal where the partner's list was dirty and nobody audited before importing. Trace bounces back to the acquisition path — high-bounce segments almost always lead to a specific event.
3. Authentication failure. SPF, DKIM, or DMARC suddenly failing. Bounces climb because receiving servers reject what they can't authenticate. Symptoms: a sharp spike, not a gradual rise. Check DMARC reports, confirm DNS hasn't changed, verify ESP configuration. Covered in the authentication guide.
4. Reputation damage. Accumulated negative signal — volume spike, complaint surge, authentication issues — and one or more ISPs are now blocking. Symptoms: bounces concentrated at specific providers. Gmail and nowhere else. Microsoft and nowhere else. Full reputation recovery is the only path: scale volume back, tight segmentation to engaged users, monitor via Postmaster Tools and SNDS.
5. Content triggering spam filters. Specific message content tripping provider filters. Symptoms: bounces on one campaign, not across the program. Isolate the campaign, seed-test, adjust content — links, images, flagged phrases.
The fix order when bounce rate spikes
1. Stop and segment. Pause non-critical sends. Bucket bounces by ISP, by campaign, by user cohort. The pattern tells you which of the five causes you're dealing with, usually within 30 minutes.
2. Apply immediate suppression. Hard bounces from the spike go to permanent suppression. Soft bounces past the retry threshold go to temporary suppression.
3. Investigate the pattern. Walk the five causes in order of frequency. The shape of the spike tells you more than any single metric.
4. Fix the underlying cause. Authentication is fast — usually minutes to hours once diagnosed. Reputation recovery is slow — three to six weeks for most programs. List-data fixes sit in the middle: once the bad acquisition path is found, cleanup is straightforward.
5. Resume gradually. Don't snap back to full volume the day the fix deploys. Ramp over a week, monitoring bounce rate daily. Impatience here is how incidents become recurring incidents.
The Orbit Deliverability Management skill runs this triage and produces the structured diagnosis. Worth having in the toolkit before a spike happens — the decision pressure during an incident is exactly the condition under which people skip step one.
Frequently asked questions
- What's a good email bounce rate?
- Hard-bounce rate below 1% is healthy. 1-2% is the warning zone — usually signals list-acquisition problems (purchased lists, scraped emails, typo traps). Above 2% is a reputation risk and mailbox providers start rate-limiting. Soft-bounce rate has less strict thresholds — 3-5% can be normal depending on your audience's behaviour, but chronic soft bounces on the same addresses should convert to suppression after 14 days.
- How do I reduce my email bounce rate?
- Three steps. First, fix list acquisition — remove any third-party lists, add real-time email verification to signup forms (ZeroBounce, NeverBounce, similar), require double opt-in for uncertain sources. Second, audit the existing list — run it through a verification service, suppress hard bounces immediately, and set up soft-to-hard conversion at 7-14 days. Third, watch the trend — bounce rate should decline after interventions. If it doesn't, the problem is acquisition, not hygiene.
- Why do hard bounces damage sender reputation?
- Mailbox providers interpret repeated sends to invalid addresses as a sign the sender has poor list hygiene, doesn't honour unsubscribes, or is using scraped / purchased lists. The reputation hit is substantial — a campaign to a list with 5% hard-bounce rate can drop domain reputation visibly in Google Postmaster Tools within 24-48 hours. Recovery takes weeks of clean sending. The discipline: every hard bounce should be in suppression before the next campaign sends to that address.
- What's the difference between a bounce and a block?
- A bounce is a delivery failure reported by the receiving mail server — your ESP accepted the message, attempted delivery, and got an error back. A block is the receiving server refusing the connection upfront (or accepting and dropping silently). Blocks often don't produce bounce records in your ESP because the message never reached the recipient's server. Bounce rate reporting can look deceptively clean even when blocks are high — only seed-list testing + Google Postmaster reveal blocks.
- Should I send to a list I haven't mailed in six months?
- Not without a re-engagement sequence first. A list that's been dormant for six months has accumulated hard bounces silently, users have forgotten they subscribed, and a cold send to it triggers reputation damage from the mass complaints and bounces. Correct approach: run a reconfirmation or winback sequence to the most-recently-engaged subset first, prove reputation is intact, then gradually extend to the full dormant cohort over several weeks.
This guide is backed by an Orbit skill
Related guides
Browse allList hygiene: the six-rule policy
List hygiene isn't cleanup; it's a continuous policy that runs automatically. Here's the six-rule policy every lifecycle program should have written down, each tied to a specific deliverability outcome.
Reputation recovery: the 90-day playbook for dropping from High to Low
Domain reputation at Low or Bad isn't a problem you fix this week. It's a 6–12 week project of disciplined sending to engaged users only, while the reputation signals slowly reset. Here's the plan.
Spam complaints: the playbook for detecting and reducing them
Spam complaints are the hardest-hitting negative reputation signal in email. They compound faster than bounces and recover slower. This is the playbook — what actually triggers them, how to catch them early, and the four levers that reliably bring the rate back down.
Bounces vs blocks vs deferrals: what your ESP's error codes actually mean
SMTP error codes are the mechanical reason emails don't arrive. Most programs lump them all into 'bounces' and miss the signal. Here's the actual taxonomy — hard bounce, soft bounce, block, deferral — and what each one tells you.
Email deliverability — the practitioner's guide
Deliverability isn't a setting. It's the running total of every send decision you've made since you bought the domain. Four pillars hold it up. Break one and the whole program starts leaking.
The unsubscribe page is the most important page in your lifecycle program
The page every lifecycle team ignores is the one quietly deciding sender reputation, suppression-list quality, and the fate of next quarter's deliverability. A short defence of why it deserves the ten-minute rebuild.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.