What’s the acceptable burst volume for bulk sends?

You've got a big promotional send coming up. Maybe it's a Black Friday campaign, a product launch, or a one-time announcement to your whole list. The question every sender asks is the same: how much volume can I throw at mailbox providers before they start throttling me?

The honest answer is that there's no universal number. But there are patterns that hold true across most sending scenarios.

The 2-3x rule of thumb

Most experienced senders treat doubling or tripling their normal daily volume as the outer edge of safe bursting. If you typically send 100,000 emails a day, a 200,000 to 300,000 message burst is usually manageable. A sudden jump to 1,000,000 from that same baseline is a different story. Mailbox providers like Gmail and Outlook build a model of your normal sending behavior. When you deviate hard from that model, they apply friction.

Why ISPs care about burst rate

Volume spikes look a lot like spam behavior. Compromised accounts, botnet activity, and list-purchase blasts all share one pattern: a sudden flood from a sender that doesn't normally flood. ISPs protect their users by throttling, deferring, or filtering that traffic until they can re-evaluate the sender. Even with a strong reputation, you're asking them to take your word for it.

What actually determines how much you can burst

• Your sending history. A sender who's been warming their IP for 90 days and consistently hitting 100k/day has built a baseline. A sender who's been quiet for three weeks and then tries to blast 500k in an hour hasn't.
• Your recent complaint and bounce rates. If your last few campaigns ran clean (low complaints, low bounces, solid engagement), providers are more willing to absorb a spike. If your reputation has been shaky, a burst is the worst time to test it.
• Your list quality. A burst to a recently cleaned, engaged list is very different from a burst to a stale list that hasn't been mailed in six months. Stale lists generate unknown-user bounces and spam trap hits, which look terrible during a high-volume window.
• Your infrastructure. Are you on a dedicated IP with your own reputation? Or a shared IP pool where other senders affect your standing? (Shared pools give you less predictable headroom.)

How to run a large burst send safely

The best approach is phased deployment. Send the first 10-20% of your list before you send the rest. Watch your deliverability signals for 30-60 minutes. If soft bounces and deferrals stay low and your engagement starts moving, continue. If you're seeing a wave of "452 too many connections" or "421 service temporarily unavailable" responses, slow down. Don't push volume into a wall.

Spreading the send over several hours instead of hammering all at once also helps. Mailchimp's send-time optimization and similar features in Klaviyo and Brevo partly exist for this reason. Distributing delivery across time windows reduces peak connection pressure on any single receiving server.

If you're planning a genuinely large burst (think 10x your normal volume or more), the safer move is to treat it like a ramp-up sequence in reverse. Notify your ESP in advance if you're on a shared infrastructure. Some providers have dedicated support channels for exactly this situation.

And before any big send, it's worth checking whether your send velocity baseline is actually in good shape. A burst on top of a shaky foundation is how senders end up in trouble for weeks after a campaign.