IP Warmup for Dedicated Senders: Volume Ramp-Up Schedule

Warming a dedicated IP is a different exercise from warming a domain. The domain accumulates engagement signals across every IP it ever sends from. The IP, by contrast, is judged on raw sending behaviour — volume curve, retry pattern, complaint rate, what RBLs say about its history. A new dedicated IP starts at zero everywhere, and each major mailbox provider has its own tolerance for how fast you can ramp.

TL;DR

Start at 50 emails per provider per day. Double every 2–3 days for the first two weeks, then increase by 50% every 3 days until you hit your target volume. Hard caps differ: Gmail tolerates faster ramp than Outlook; Yahoo throttles aggressively early. Any 4xx throttling response means hold volume steady for 48 hours.

Who actually needs IP warmup

Dedicated IPs make sense when you're sending consistently above 100k messages per month and you want full control of your own reputation. Below that volume, a shared IP at a reputable ESP almost always outperforms a low-volume dedicated IP — there simply isn't enough send volume to maintain a strong reputation signal.

If you're reading this for a cold-outreach use case at a few thousand messages per month, you probably don't want a dedicated IP at all. The remaining article assumes legitimate bulk transactional or marketing volume on the order of hundreds of thousands per month.

The 30-day ramp schedule

Volumes below are per major mailbox provider. So "day 1: 50" means 50 to Gmail, 50 to Outlook, 50 to Yahoo, sent across the day, not 50 total.

Days 1–2: 50 per provider per day.
Days 3–4: 100 per provider per day.
Days 5–6: 200 per provider per day.
Days 7–8: 400 per provider per day.
Days 9–10: 800 per provider per day.
Days 11–12: 1,500.
Days 13–14: 3,000.
Days 15–17: 5,000.
Days 18–20: 8,000.
Days 21–24: 12,000.
Days 25–28: 18,000.
Days 29–30: 25,000+ per provider, depending on target steady-state.

This is a doubling cadence for the first two weeks (when absolute volumes are small enough that doubling is safe), slowing to a ~50% increase every 3 days as the absolute numbers get large. Past day 30, increase no more than 25% per week.

Per-provider caps you cannot ignore

Each major mailbox provider applies its own connection and recipient limits, and they kick in earlier than you'd expect:

Gmail. Tolerates a faster ramp than most. The early throttle signal is a 421 4.7.0 "Try again later". Hard limit on a fresh IP is roughly a few hundred per hour for the first week; respect it or face soft-bouncing for days afterward.
Outlook (Hotmail/Live/Outlook.com). Slowest to trust. Daily caps on fresh IPs are conservative — expect 4xx deferrals if you exceed ~200/hour in week 1. Subscribe to SNDS and JMRP early; they're the only feedback loop.
Yahoo / AOL. Aggressive early throttling. A new IP sending 500 in an hour will see 421 deferrals on most messages. Spread sends across the full day. Their reputation response is faster once trust builds — second week is much easier than first week.
Apple iCloud / Me / Mac. Generally permissive on volume, strict on content. SPF and DKIM must align; otherwise deferrals.
Mail.ru / Yandex. Conservative. Treat like Outlook on early ramp.

Spread across the day

A burst of 500 messages in 5 minutes is a much worse signal than 500 messages spread evenly over 8 hours, even if the daily total matches. Throttle your sender to send at a steady rate during the warmup. Most ESPs let you set a per-IP messages-per-hour ceiling.

Engagement during warmup

IP reputation is volume-and-complaint based, but it can't be cleanly separated from engagement. The recipients you send to during warmup directly affect whether the IP graduates from "new sender" status into trusted territory. Send your most-engaged segments first: customers who opened in the last 7 days, transactional recipients, opt-ins from this month.

Avoid the temptation to point a fresh IP at a re-engagement campaign aimed at dormant addresses. Re-engagement is the single fastest way to rack up complaints and bounces — exactly the signals that kill a new IP.

Reading throttle responses

Mailbox providers communicate their patience through SMTP response codes. The ones to watch:

4xx deferrals. Soft failures. The provider is asking you to slow down or retry later. A 421 typically means you're hitting a connection or rate limit.
421 4.7.0. Throttling for sender reputation. Pause increases.
5xx hard rejections. Specific reasons: complaint threshold reached, blacklist match, content filter. Hard rejects need investigation, not retries.
Silent acceptance into spam. The most dangerous signal — provider accepts the message with a 250 OK and routes it straight to spam. Only seed tests detect this.

Hold and step-back rules

The schedule above assumes everything goes well. When it doesn't:

4xx rate above 5%. Hold today's volume for 48 hours, do not increase. Investigate per-provider patterns.
4xx rate above 15%. Step back to the previous day's volume and hold for 72 hours.
Complaint rate above 0.3% on any provider. Pause campaigns to that provider for 24 hours. Investigate the source list.
Postmaster reputation drops to Bad. Stop the warmup immediately and diagnose. A Bad rating during warmup means the IP is being marked as a spammer; continuing makes it permanent.
Blacklist appearance (Spamhaus, SORBS, Barracuda). Stop, delist, then resume from one day earlier.

Reset versus restart

A reset means you pause for several days then continue from a slightly lower volume. A restart means going back to day 1. Restart is required if the IP has hit a major blacklist or if Postmaster shows Bad reputation for over 7 days. Resets are recoverable; restarts cost you a month.

Domain warmup runs in parallel

Warm the IP and the sending domain together, on the same schedule, sending the same content. Don't front-load IP warmup with domain A then switch the domain at day 20 — that looks like a hijacked IP and triggers reviews at major providers. The IP and domain are two reputations, but they ramp better when they ramp together.

Verifying the warmup

Daily seed test across 20+ provider mailboxes. Inbox rate should rise day over day.
Postmaster Tools reputation visible by day 30, ideally Low or Medium.
SNDS data for Outlook IPs — green/yellow status, complaint rate under 0.3%.
No blacklist appearances at Spamhaus, Barracuda, SORBS, URIBL throughout.
4xx deferral rate trending down across the schedule, not up.

Frequently asked questions

Can I warm up a dedicated IP with cold leads?

No. Cold lists during warmup produce complaint and bounce rates that destroy the new IP's reputation before it has any cushion to absorb them. Use engaged transactional or opt-in volume for warmup, then transition to cold campaigns after day 30.

What if my ESP requires a faster ramp?

Push back. Any ESP forcing you to start at 5,000/day on a fresh IP is setting you up for a Bad reputation tag inside the first week. The schedule above is what mailbox providers will tolerate; ESP business pressure does not change that.

How long is the warmup if I already have a warmed domain?

Still ~30 days. The IP reputation is independent of the domain. A warmed domain helps engagement signals during the IP ramp but does not let you skip the volume curve.

Should I rotate sends across multiple new IPs?

Only if you have the volume to warm each one properly. Spreading 5,000/day across four cold IPs gives each one 1,250/day — too low to build reputation at any single one. One IP warmed to its target beats four IPs stuck at low volume.

IP warmup for dedicated senders: volume ramp-up schedule