Email infrastructure
Warming up a dedicated IP — and the question to answer before you do.
A new dedicated IP has no reputation, so sending at full volume gets it throttled, deferred, or blocked. Warm-up is the 4-8 week ramp that builds trust: start at 50-200 a day to your most engaged recipients, never grow more than 50% day-over-day, and segment by engagement recency throughout. But the honest first question is whether you need a dedicated IP at all — under roughly 50,000 emails a month, a shared IP is safer and needs no warm-up. Buying dedicated infrastructure too early is the most common deliverability mistake.
In short
- Most senders don't need a dedicated IP. Under ~50k/month, a shared IP is safer and already warmed.
- The ramp is 4-8 weeks. Longer for very high volume; never rush below 2 weeks.
- Segment by engagement recency. 30-day engaged first, then 60-day; never 90+ inactive in the first six weeks.
- Authentication and a clean list come first. Auth failures and bounces cancel out the reputation work.
- Watch the gates. Complaints above 0.3% or bounces above 5% mean stop, not slow down.
Do you even need a dedicated IP?
Start here, because the answer is no more often than the vendors selling dedicated IPs would suggest. A dedicated IP gives you a reputation that is entirely your own — nobody else's sending can help or hurt it — but that cuts both ways, and it only becomes an asset when you send enough volume, consistently enough, for mailbox providers to form a stable picture of you. Under ~50,000 emails/month, or inconsistent volume: stay on a reputable ESP's shared IP. It is already warmed by collective sending; you do not manage IP warm-up at all.
The threshold where a dedicated IP starts to make sense is real and fairly high. Around 100,000+ emails/month, sent consistently: a dedicated IP becomes worthwhile, roughly $30-60/month, and it must be warmed. 1,000,000+ emails/month: plan multiple dedicated IPs, roughly one per million per month, each warmed. Below that, a shared pool at a reputable provider is not a compromise; it is the better choice, because the pool's combined volume keeps the IP warm and its reputation stable in a way a low-volume dedicated IP never could.
The most common deliverability mistake is buying dedicated infrastructure too early. More control only helps if you can maintain it with clean data, stable sending, and monitoring; if you cannot, shared infrastructure is usually safer. A clean warm-up schedule cannot compensate for a dirty list, a weak domain, or erratic cadence — many problems blamed on under-warming are really bad sequencing. We lead with this because we watch teams buy a dedicated IP, send the campaign they had been holding back, and get throttled by the second day — then blame the warm-up schedule, when the real error was provisioning dedicated infrastructure they did not have the volume or the discipline to keep warm.
The threshold
Shared, dedicated, or several?
The decision is mostly about volume and consistency, not ambition. Match your real monthly volume to the row, not the volume you hope to reach.
| Your volume | What it means | Setup |
|---|---|---|
| Under ~50k/month | Stay on a reputable ESP's shared IP. It is already warmed by collective sending; you do not run a warm-up at all. | Shared IP |
| ~100k+/month, steady | A dedicated IP becomes worthwhile, roughly $30-60/month, and must be warmed over 4-8 weeks. | Dedicated IP |
| 1M+/month | Plan multiple dedicated IPs, roughly one per million per month, each warmed independently. | Multiple IPs |
There is one more situation that forces a warm-up regardless of these thresholds: a new sending identity. A new dedicated IP (even an additional IP at your current ESP), a new sending domain or subdomain, or a new esp (which usually means new ips) all start cold even for an established sender, and so does a sending gap of 90+ days, which lets engagement history go stale. If any of those apply, you are warming up whether or not your volume says you need a dedicated IP.
What has to be true before the first send
A warm-up only works on top of a sound foundation, and two prerequisites do more to determine success than the schedule itself. The first is authentication. Authentication first: SPF, DKIM, and DMARC correctly configured and aligned before the first warm-up send. Authentication failures cancel out the reputation work. If your mail is failing SPF, DKIM, or DMARC alignment, every careful day of ramping is building reputation on sand — the providers cannot even confirm the mail is really yours, so the positive signals do not accrue the way you intend.
The second is list quality, and it is the one teams most often underestimate. Verify the list first: every bounce during warm-up counts double against reputation, so clean and verify addresses before sending. A bounce on a new IP is not a neutral event; it is a strong negative signal that you do not know who you are emailing, and a cluster of them early in a ramp can undo weeks of work in a single send. Verifying the list — removing invalid addresses, spam traps, and long-dead contacts — before the first message is not optional housekeeping, it is part of the warm-up.
The third prerequisite is a habit rather than a setup task: consistency. Consistency: send every day during warm-up — gaps reset the momentum providers are tracking. Mailbox providers are watching for a stable, predictable pattern, and an IP that sends heavily one day and goes silent for three reads as erratic. A smaller daily volume you can sustain every single day is worth more than a larger one you send in bursts.
The ramp, and the gates that govern it
Here is the shape of a ramp toward 50,000 a day. The exact numbers are illustrative — you scale them to your own target — but the structure holds at any size: a small start, gradual proportional growth, and a hard ceiling of 50% increase from one day to the next.
# A proportional ramp toward 50,000/day — adjust to YOUR target
# Week 1 engaged-30d only · never +50% day-over-day
Day 1 50 Day 8 1,500 Day 15 12,000
Day 2 100 Day 9 2,500 Day 18 20,000
Day 3 250 Day 10 4,000 Day 21 30,000
Day 4 500 # Week 2-3 expand to engaged-60d Day 25 42,000
Day 7 1,000 Day 14 8,000 Day 30 50,000
# Hold the day's volume if metrics dip. Send EVERY day.The schedule is only half of it. What actually decides whether you scale, hold, or stop is a set of metric gates you check every day. These are not targets to admire after the fact; they are the controls that tell you, in real time, whether the providers are accepting your mail or beginning to distrust it.
# The gates that decide whether to scale, hold, or stop
spam_complaint_rate <= 0.1% # above 0.3% -> STOP, audit segment
hard_bounce_rate <= 2-3% # above 5% -> STOP, clean list
inbox_placement > 90%
engagement_rate > 20% # on warm-up sends
gpt_domain_reputation None -> Low -> Medium -> High
# 421/450 temp-fail (e.g. Yahoo) -> pause 24h, drop a tierThe playbook
From cold IP to full volume, step by step
Six steps in order. The first is a decision, not an action — and it is the one that saves the most grief.
- 1
Decide whether you need a dedicated IP at all
This is the step most teams skip, and getting it wrong is the most expensive mistake in deliverability. If you send under roughly 50,000 emails a month, or your volume swings unpredictably, a shared IP at a reputable ESP is safer and needs no warm-up — it is already warmed by everyone else sending on it. Only commit to a dedicated IP if your volume is high and consistent and you can sustain clean data and daily monitoring.
- 2
Finish authentication and clean the list before sending
Set up SPF, DKIM, and DMARC and confirm they align with your From domain before the first warm-up send, because authentication failures cancel out every bit of reputation you build. Then verify the list: every bounce during warm-up counts double against a new IP, so remove invalid addresses, spam traps, and stale contacts up front rather than discovering them mid-ramp.
- 3
Start small and send to your most engaged recipients
Begin on the order of 50 to 200 messages a day, aimed only at people who opened or clicked in the last 30 days. Their positive engagement is what teaches mailbox providers your IP is trustworthy, and starting with a strong audience builds reputation fastest. A weak or cold first audience poisons the ramp before it has begun.
- 4
Ramp gradually and segment by engagement recency
Increase volume day over day but never by more than 50%, holding the previous day's number whenever a metric dips. Expand the audience as you go: weeks one and two to your 30-day engaged, weeks three and four out to 60-day engaged, and never to contacts inactive for 90 days or more in the first six weeks. This segmentation rule prevents more warm-up failures than any tool.
- 5
Watch the gates and react
Monitor daily. Keep the spam-complaint rate at or below 0.1% and the hard-bounce rate at or below 2 to 3 percent; if complaints pass 0.3% or bounces pass 5%, stop and audit rather than pushing on. Watch Google Postmaster Tools climb from None toward High. If a provider returns a 421 or 450 temporary failure, pause about a day and restart at the previous tier.
- 6
Keep sending consistently after the ramp ends
Reputation management does not end when the warm-up does. Providers keep evaluating your behaviour, so avoid sudden volume spikes, keep cadence steady, and do not let a long gap reopen the cold-start problem. A careful ramp wrecked by erratic post-warm-up sending is a common and avoidable failure.
Warm-up ends; reputation management does not. Providers keep evaluating behaviour, so keep volume steady, avoid sudden spikes, and many practitioners maintain a base of ongoing engaged sends rather than flipping abruptly between warm-up and full campaigns.
Why a clean schedule fails on a stale list
The most common way a textbook-perfect ramp still fails is sequencing — the order and quality of the audience, not the daily numbers. Segment by engagement recency throughout the ramp: weeks 1-2 send only to contacts who engaged in the last 30 days, weeks 3-4 expand to 60-day engaged, and never send to 90+ day inactive contacts in the first six weeks. Practitioners call this the single rule that prevents the most warm-up failures. The reasoning is simple: warm-up works by accumulating positive engagement, and only recently active recipients reliably produce it. Send week one to a list you last touched a year ago and the opens will not come, the complaints will, and the IP learns exactly the wrong lesson about you.
This is why so many problems blamed on under-warming are really audience problems in disguise. A team slows the schedule, sees no improvement, slows it further, and never fixes the actual cause, which was a cold or dirty first segment all along. The schedule is a control on volume; it cannot manufacture the engagement that a stale audience will never give. Get the sequencing right — best recipients first, widening only as reputation builds — and a moderate schedule succeeds where an extremely cautious one on a bad list would not.
It is also why the warm-up tool question has a nuanced answer. Engagement-network warm-up tools make sense for cold-outreach senders running many mailboxes. For a marketing dedicated IP sending to real opt-in recipients, you do not need manufactured seed engagement — you need a volume ramp, clean data, and real recipients. Providers increasingly detect artificial seed patterns (opens with no deletes or natural variation). For the opt-in marketing and transactional mail most of our customers send, the better investment is in list verification and genuinely engaged segments than in a seed network that simulates engagement the providers are increasingly able to see through.
When a ramp stalls
The decision loop when metrics turn
A warm-up is a controlled test, not a fixed template. Each day's metrics decide the next day's move.
When a ramp stalls, the recovery is the same regardless of provider: stop adding volume to a system that is signalling distrust, drop back to the last tier that was healthy, find and fix the cause — usually a segment that was too cold or a list that was not clean — and resume from the safe volume. If a provider returns a 421/450 temporary failure (e.g. Yahoo), pause about 24 hours and restart at the previous volume tier rather than pushing through. Pushing harder into a temporary failure or a complaint spike turns a pause into a lasting reputation problem.
Where we stand
We sell dedicated IPs, and we will still tell most senders they do not need one. The honest threshold is volume and consistency: below roughly 50,000 emails a month, or with volume that swings, a shared IP at a reputable provider will give you better, steadier deliverability than a dedicated IP you cannot keep warm — and it spares you the entire warm-up project. We would rather set you up correctly on shared infrastructure than sell you a dedicated IP that becomes a liability the first time you send a real campaign.
For the senders who genuinely have the volume, a dedicated IP is worth it, and we run the warm-up as a controlled test rather than a fixed calendar: authentication and list verification first, a proportional ramp to your most engaged recipients, daily monitoring against the gates, and a willingness to hold or drop back the moment the metrics say so. When migrating ESPs or moving to a new IP, overlap sending: keep the old infrastructure active and shift volume gradually rather than flipping a switch. AWS SES adds its own sandbox mode and rate limits on top of standard warm-up. The schedule is the easy part. The judgement — knowing whether you need the IP, keeping the list clean, and reacting to the gates instead of pushing through them — is the part that actually protects your inbox placement, and it is the part we are glad to handle with you.
Questions
Answered plainly
The questions teams ask before provisioning a dedicated IP.
Do I actually need a dedicated IP?
Probably not, and that is the most important answer here. If you send under roughly 50,000 emails a month, or your volume is inconsistent, you are better off on a reputable ESP's shared IP, which is already warmed by the collective sending of everyone on it and requires no warm-up from you. A dedicated IP only earns its place at around 100,000 or more emails a month sent consistently, where the volume is enough for providers to build a per-IP reputation. Buying dedicated infrastructure before you have that volume is the single most common deliverability mistake — more control only helps if you can sustain clean data and steady sending.
How long does warming up a dedicated IP take?
Four to eight weeks for most senders. Very high-volume programs, on the order of 500,000 or more a day, should plan eight to twelve weeks, and if most of your mail goes to Microsoft inboxes you should add about a week because their filtering is stricter. The one hard rule is not to rush below two weeks: providers throttle or block IPs that ramp too fast. The exact length depends on your target volume, the cleanliness of your list, and how consistently positive your engagement stays throughout.
What daily volume should I start at?
On the order of 50 to 200 messages a day, sent only to your most engaged recipients, then increased gradually with a ceiling of 50% growth day over day. The specific numbers matter less than the shape: a proportional ramp that grows from a small base toward your real target, never spiking, and holding steady whenever a metric dips. A sender targeting 50,000 a day and one targeting 500,000 a day follow the same percentage curve at different scales rather than hitting the same arbitrary daily figures.
Why does segmentation matter more than the schedule?
Because engagement is what actually builds reputation, and your most recently engaged contacts produce the strongest positive signals. The rule practitioners point to as preventing the most failures is to segment by recency throughout the ramp: weeks one and two to people who engaged in the last 30 days, weeks three and four out to 60 days, and never to anyone inactive for 90 days or more during the first six weeks. A perfect day-by-day spreadsheet sent to a stale or cold audience will still fail, because the opens, clicks, and low complaints that warm an IP simply will not be there.
What metrics tell me to slow down or stop?
Keep the spam-complaint rate at or below 0.1% and the hard-bounce rate at or below 2 to 3 percent. If complaints climb above 0.3%, stop immediately and audit the segment you are sending to; if hard bounces exceed 5%, stop and clean the list, because that is a data problem a slower schedule will not fix. Inbox placement should stay above 90% and engagement above roughly 20% on warm-up sends, and Google Postmaster Tools should show domain reputation climbing from None through Low and Medium toward High. A 421 or 450 temporary failure means pause about a day and drop back a tier.
Should I use a warm-up tool with a seed network?
It depends on what you are warming. For cold-outreach senders running many mailboxes, engagement-network tools that generate opens and replies at scale can make sense. But for a marketing dedicated IP sending to real opt-in recipients, you do not need manufactured engagement — you need a clean list, a volume ramp, and your own real recipients. Providers increasingly detect artificial seed patterns, such as opens that never delete or vary the way human behaviour does, and a sudden shift from manufactured warm-up activity to real campaigns can itself look suspicious. Clean data and real engagement beat a seed network for opt-in marketing mail.
Not sure if you need a dedicated IP?
Tell us your monthly volume and how steady it is. We will tell you honestly whether a shared IP is the better call — and if you do need a dedicated one, we will run the warm-up with you.