You're sitting at your desk wondering how many emails you can actually send per hour without getting your domain blacklisted. You've read conflicting advice online - someone says 50 per hour is fine, someone else says never go above 20, and you're stuck guessing.

Here's the truth: there's no single "safe" number. Your hourly limit depends on your sender reputation, domain age, email provider, list quality, and sending infrastructure. But there are concrete numbers you should know based on what actually works in 2026.

Why Hourly Limits Matter (And Why Most People Get It Wrong)

ISPs watch sending patterns. If you go from sending 0 emails to 200 emails per hour overnight, their spam filters notice. They don't care about your conversion rate or how good your copy is - they care about behavioral anomalies.

The mistake most people make is treating hourly limits as a universal constant. They're not. A warm, aged domain with a solid track record can safely send 80-100 emails per hour. A brand new domain with no history will get throttled or blocked at 30 emails per hour, even with perfect list quality.

The actual constraint isn't the hourly limit itself - it's the sender reputation that determines what your hourly limit can be.

Baseline Hourly Sending Limits by Scenario

Brand new domain (0-30 days old):

New domains get scrutinized heavily. ISPs expect new senders to build reputation gradually. If you blast 500 emails on day one from a brand new domain, you're going straight to spam - or getting blocked entirely. The infrastructure providers know this, which is why most email services automatically throttle new accounts.

Established domain (3-6 months old with positive history):

Once you've been sending consistently for a few months with good metrics - low bounce rates, low complaint rates, people actually opening your emails - ISPs trust you more. You have room to scale without immediate consequences.

Warm domain (6+ months, strong sender reputation):

This is where real volume becomes possible. If you've been sending clean, relevant emails for six months with consistent opens and replies, you're not a spam risk anymore in the eyes of ISPs. Your hourly limits become less about safety and more about optimizing for engagement.

The Ramp-Up Timeline That Actually Works

Don't jump straight to your "safe" hourly limit. ISPs notice acceleration. Here's the pattern that works:

The key is consistency. Send at a steady pace within your tier for at least a week before moving up. This builds trust with ISPs - they see a gradual, predictable sender, not someone trying to dump volume.

The Variables That Change Your Limit (Real Numbers)

List quality: This is the biggest factor after domain age. A clean, well-researched list from a reputable source lets you push closer to the upper limit. A purchased list or one with old contacts will tank your reputation fast.

If your bounce rate is above 2%, your safe hourly limit drops 20-30%. If it's above 5%, cut your hourly volume in half. Clean your list before scaling.

Email provider: Gmail's infrastructure is forgiving up to a point. Office 365 and corporate domains are stricter. If your target audience is mostly Office 365 users and you're sending through a shared IP, your hourly limit should be 30-40% lower than the baseline above.

Open and reply rates: If your emails get opened and replied to, ISPs see you're sending wanted mail. This compounds over time. After 30 days of 20%+ open rates and 5%+ reply rates, you can safely push 15-20% harder on hourly volume without risk.

Complaint rate: This kills everything. If your unsubscribe or complaint rate is above 0.5%, your reputation takes damage that takes weeks to repair. Keep it below 0.2%. One complaint per 500 emails is the threshold where you're still safe to scale.

Practical Hourly Pacing for a Real Campaign

You've got a 500-person list and you're launching a campaign from an established domain. Here's how to send it:

Spread 500 emails across 6-8 hours, not all at once. Send 60-80 emails per hour. That's one email every 45-60 seconds - slow enough that ISPs see natural sending patterns, fast enough to finish in one business day.

Here's what NOT to do:

Send all 500 emails at 9am in a 30-minute window. Your domain looks like a bot. Gmail flags it as suspicious. You hit spam or get throttled immediately.

Here's what works:

Send 75 emails at 9am, 70 at 10am, 75 at 11am, 80 at 1pm, 70 at 2pm, 60 at 3pm. Spread across the day naturally. ISPs see normal sending behavior from a trusted sender.

Monitoring What Matters (Not What Doesn't)

Don't obsess over daily limits. Hour-to-hour limits matter because they affect how ISPs perceive your sending pattern. What you actually need to track:

If you see throttling errors, cut your hourly volume by 25% and hold it there for a week. If you see zero throttling after two weeks at a given hourly rate, you can increase by 15-20%.

The Gap Between Knowing and Doing

Reading this guide tells you what the limits are. Actually running a campaign at scale while maintaining these limits is different. You need to monitor bounce rates in real-time, adjust sending patterns on the fly, handle infrastructure issues without nuking your sender reputation, and manage reply handling as volume scales. It's doable solo, but it's also where most people either send too fast and destroy their domain, or send too slow and take six months to build pipeline. The infrastructure setup, monitoring, and ongoing optimization is where most teams lose the thread - especially once you're managing multiple domains or campaigns simultaneously.

Related Guides