Split the number before acting on it. Hard bounces mean addresses that no longer exist, and those must go. Soft bounces mean full mailboxes, busy servers and greylisting, and those addresses are usually fine. Averaging the two hides which problem you have.
Mailbox providers read the hard share as a sign of how you handle data. Somebody mailing addresses that failed last month tells Gmail something about how they collect and maintain a list, and the inference isn't kind.
Cold email runs on the same rule with less room. Gmail's guidelines, read in September 2026, ask senders of more than 5,000 messages a day to keep spam rates in Postmaster Tools under 0.3%, with 0.1% as the target. Bounces aren't on that list, but a cold list that bounces 4% usually also draws complaints, because the same stale data causes both. Verify every cold list before the first send, and keep catch-all addresses in a smaller batch of their own.
The risky moment is the first send to old data. A file untouched for eighteen months can bounce a fifth of its addresses in one campaign, and that lands as a single spike rather than a slow trend. Verify before that send, not after it.
Watch the figure by source, not as one average. An overall 3% looks fine while one lead vendor inside it bounces at 12%, and that vendor is both your problem and your fix. A bounce rate calculator splits the math per segment in a minute.
A small hard-bounce rate never fully disappears. People leave jobs between your check and your send, so a trickle of failures is a sign your list is made of real people who move. To bring the rest down, bulk verification removes the addresses a mail server says don't exist before they ever cost you a bounce.
Working the number out from one send report
Say your report shows 24,000 sent and 720 bounced. Divide bounces by sent, not by delivered, and you get 3.0%. That figure alone tells you little, so split it. Suppose 410 were hard bounces and 310 were soft. Your hard-bounce rate is 1.7% and your soft rate is 1.3%.
Now read the codes on a few of the hard ones. A 5.1.1 means the mailbox doesn't exist, and that's a list problem. With 5.7.1 you're looking at a policy block, which points at your sending setup and not at the address. On the soft side, 4.2.2 is a full mailbox.
In this example the list problem is 1.7%, which is under the 2% line. The headline 3.0% looked worse than the list really is, and the fix for the rest lies with your sending, where cleaning won't help.
Three cases where the rate misleads you
Small sends are the first. Three bounces out of 60 messages is 5%, and it means nothing. Don't react to a rate until a few thousand messages sit behind it.
Suppression can flatter you as well. Your platform stops mailing addresses that bounced before, so each campaign's rate covers only the survivors. A steady 0.4% can sit on top of a list where a fifth of all contacts are already suppressed. Look at the suppressed count next to the rate, because together they describe the list.
Mixed streams are the third. Password resets and receipts go to people who typed their address a minute ago, so they almost never bounce. If those share a report with marketing sends to year-old data, the blend will look healthy while the marketing stream is in trouble.
A single campaign can also swing on one bad import. Rolling 30-day figures, split by stream, are the version worth putting on a dashboard.
Related questions
What bounce rate is acceptable for cold email?
Keep hard bounces under 2% on cold email, the same line as marketing mail. Gmail publishes no bounce limit, but it caps spam complaints at 0.3% for senders of 5,000 or more messages a day, and stale lists push both numbers up.
What bounce rate triggers filtering?
Filtering usually starts to bite above 5%, when a list looks unmaintained. Providers don't publish a bounce threshold, so treat 2% as your ceiling and act before you reach it.
Do soft bounces count toward the problem?
They're tracked apart and weigh less. A soft bounce that repeats across a retry window is converted to a hard bounce by most sending platforms.
Can a bounce rate be too low?
A rate of zero on a large send usually means suppression is hiding failures, not that every address is perfect. Check the suppressed count beside the rate.