IP Warming: How to Warm Up a New Sending IP (Step-by-Step)

A new dedicated IP address carries no sending history, so mailbox providers have nothing to judge it by except what you do in the first few weeks. IP warming is the process of ramping volume on that specific IP gradually, starting with your most engaged recipients, so Gmail, Outlook, and Yahoo build a positive reputation for it before you send at full scale. Skip the ramp, and a sudden burst of mail from an unfamiliar IP reads as a spam signal, triggering throttling, deferrals, or the spam folder no matter how good your content is.

This guide covers dedicated IP warming specifically. If you are sending through a shared IP pool, most of what determines your inbox placement is domain reputation, not IP reputation, and you can likely skip this process entirely. Read on to find out which situation applies to you.

IP Warming vs. Domain Warming: Different Signals, Different Ramps

Mailbox providers track domain reputation and IP reputation as separate signals. Domain warmup builds trust for your sending domain and applies every time you introduce a new domain or subdomain, regardless of infrastructure. IP warming only matters when you add or switch to a dedicated IP address that you alone control.

The two problems overlap but are not identical. Your domain reputation follows your brand across infrastructure changes. Your IP reputation resets every time you get a new dedicated IP, even if your domain has years of clean history. If you migrate a well-established domain onto a brand-new dedicated IP, you still need to warm the IP, because that specific address has never sent mail from any provider’s point of view.

Do You Actually Need a Dedicated IP?

Most senders never need this step. A dedicated IP only makes sense once your volume and consistency justify the reputation management it requires.

Postmark’s guidance on the decision is direct: “We recommend sending at least 300k messages a month to be able to properly maintain a dedicated IP.” Below that, a shared pool run by your ESP or SMTP relay benefits from the aggregate reputation of many senders, and, per Postmark, “there’s no need to go through a warming-up period on your own with a shared IP.” Mailgun draws the line lower, at weekly rather than monthly volume: “If you are sending a lot of email (greater than 50K per week), it is best to isolate your reputation by having a dedicated IP address.”

Situation	Recommended setup
Under roughly 50,000-100,000 emails per month	Shared IP pool, no warmup needed
100,000-300,000 emails per month, consistent daily sending	Either works; dedicated only if you need isolation from other senders
300,000+ emails per month, consistent volume	Dedicated IP, with warmup
Any volume, but irregular or bursty sending	Shared IP pool, dedicated IPs punish inconsistency

Consistency matters more than the raw number. A dedicated IP that sends 50,000 emails one week and nothing the next looks suspicious to filtering systems regardless of total volume. If you are not sure your product’s sending pattern justifies dedicated infrastructure yet, Coldletter’s free trial lets you send real campaigns on shared infrastructure and observe your actual volume and engagement before you commit to the switch.

Why Mailbox Providers Throttle Unknown IPs

An IP with no history is, by definition, indistinguishable from a spammer’s IP at first contact. Per Twilio SendGrid’s IP warmup documentation: “When an ISP observes email coming from an added or ‘cold’ IP address, they begin evaluating the traffic coming from that IP address.” Volume is the first signal they check, because a sudden spike from an address with no track record matches the pattern of spam campaigns far more often than legitimate senders.

Three inputs determine how that evaluation goes: how much volume you send relative to your history on that IP, how recipients engage with the mail (opens, clicks, replies, versus complaints and deletes-without-opening), and your complaint rate. All three compound. High volume with strong engagement builds reputation quickly. High volume with weak engagement or rising complaints gets you throttled, deferred, or filtered before you notice anything is wrong.

A Representative Dedicated IP Warmup Schedule

The schedule below is illustrative, built from published SendGrid warmup guidance, not a fixed formula. SendGrid notes that “the majority of Twilio SendGrid clients warm up their IPs within 30 days, and some complete the process in as little as 1-2 weeks,” while very high-volume senders can take up to 60 days. Your actual pace depends on your list size, engagement quality, and how your metrics respond at each step.

Stage	Approx. timeframe	Daily volume per major provider	Recipient focus
Stage 1	Days 1-7	50-500	30-day actives only
Stage 2	Days 8-14	500-2,500	30-60 day actives
Stage 3	Days 15-21	2,500-10,000	60-90 day actives
Stage 4	Days 22-30	10,000-50,000	Full engaged list
Extended (high volume)	Days 31-60	Continue ramping to target	Full list, monitor per-provider

Senders targeting a few hundred thousand emails a month usually finish in the 30-day column. Senders targeting millions per month should plan on the extended timeline. Either way, SendGrid’s own advice is the safest default: “The slower you can warm up the better. This way, you can locate and fix any anomalies and issues that arise when you first begin sending.”

Splitting your ramp by provider, tracking Gmail, Outlook, and Yahoo separately rather than in aggregate, catches problems that a blended view hides. A deliverability issue at one provider rarely shows up in your overall numbers until it has already done damage there.

Send to Your Most Engaged Recipients First

Engagement is the input you control most directly, so sequence your warmup around it. Segment your list by recency of activity (opens, clicks, replies in the last 30, 60, and 90 days) before you start, and send only to your most recent actives in the first stage. Expand to less-recent segments only as your metrics on the new IP stay healthy.

Sending to cold or unengaged contacts in the first week of a new IP’s life is the single fastest way to generate complaints before you have any reputation cushion to absorb them.

What to Monitor During IP Warming

Check these before every volume increase, not after problems appear. They are IP-specific versions of the same metrics covered in our broader email deliverability best practices guide.

Spam complaint rate. Google’s sender guidelines set the bar: “keep your spam rate below 0.1% and should prevent spam rates from ever reaching” the 0.3% threshold, since “rates of 0.3% or higher have an even greater negative impact on email inbox delivery.” Treat 0.1% as your ceiling during warmup, not your target.

PTR record and reverse DNS. A dedicated IP needs a valid PTR record whose forward DNS entry matches the sending IP, a check domain warmup does not involve at all. Missing or mismatched records are a common reason a warmup stalls even when volume and engagement look fine. Verify this before your first send, not after a bounce spike.

Google Postmaster Tools. Set it up before your first warmup send so you can see spam rate and domain reputation as Gmail records them. Cross-reference it against your ESP’s per-IP dashboard, since Postmaster Tools reports primarily at the domain level.

Deferrals and throttling responses. A 4xx response on a new dedicated IP usually means the receiving provider is rate-limiting you deliberately while it evaluates the address. Repeated deferrals at the same stage are a sign to hold volume steady, not push forward, until they clear.

Bounce rate. Keep total bounces under roughly 2-3%. Hard bounces on a new IP should be removed immediately; they carry more weight against an unproven address than against one with years of good history, per general sender reputation guidance from ESPs.

Common IP Warming Mistakes

Treating the schedule as a guarantee. Every table in this guide, and every table any vendor publishes, is a starting point. Pull back if your metrics deteriorate at any stage, regardless of what day the calendar says you should be on.

Letting a warmed IP go cold. SendGrid is explicit: “if you haven’t sent email messages through your IP address in more than 30 days, warm it up again.” A dedicated IP’s reputation decays with inactivity the same way it builds with activity.

Warming the IP but ignoring the domain. If you are moving to a dedicated IP on a domain that also needs its own warmup, run both processes together and prioritize domain-level authentication and engagement first. An IP with a perfect ramp cannot rescue mail sent from a domain that fails SPF or DKIM.

Sending to a purchased or unverified list during warmup. Bad addresses produce hard bounces at the exact moment your new IP has zero tolerance for them. Verify your list before the first send, not during it.

Skipping the volume-vs-consistency check. Getting a dedicated IP because your monthly total looks impressive, then sending it in irregular bursts, produces worse outcomes than staying on a shared pool. Consistency is part of what you are trying to prove to the receiving provider, not a secondary concern.

---

Frequently Asked Questions