KoltrixShared vs dedicated sending IPs: a decision guide
Dedicated IPs give you control and responsibility; shared pools give you a neighbor's reputation. Volume thresholds and questions to decide well.
On this page(9 sections)
- What you are actually choosing
- The case for shared IPs
- Consistent volume without effort
- No warm-up
- Someone else watches the pool
- The risk: neighbors
- The case for dedicated IPs
- Isolation
- Control and visibility
- Allowlisting
- The risk: you own the consequences
- A decision guide
- How many dedicated IPs?
- Questions to ask your provider
- Moving from shared to dedicated
- Checklist
- Key takeaways
A dedicated IP sounds like a premium upgrade: your own address, your own reputation, nobody else's mistakes. For many senders it is the opposite of an upgrade.
Whether it helps depends mostly on how much you send and how consistently you send it.
What you are actually choosing
Shared IPs are pools of addresses your email provider uses for many customers at once. Your messages go out alongside other senders' messages from the same IPs. The provider manages the pool's reputation: warming new addresses, removing abusive customers, balancing load.
Dedicated IPs are addresses used only for your mail. Their reputation reflects only your sending behavior. You, or your provider on your behalf, are responsible for warming them up and keeping them healthy.
Domain reputation is the same either way. Your authenticated From and DKIM domain carries its own history regardless of the IP underneath, and modern filters weigh it heavily. The IP choice determines only the IP part of the picture.
The case for shared IPs
Consistent volume without effort
Receivers build IP reputation from steady, predictable traffic. A well-run shared pool sends a large, continuous stream of mail, which looks normal to receivers. Your few thousand messages a day ride along on that established pattern.
No warm-up
A dedicated IP starts with no history. Receivers treat unknown IPs cautiously and may defer or filter mail from them until a track record builds. On a shared pool, the IPs are already warm.
Someone else watches the pool
Good providers monitor shared pools closely, quarantine customers who generate complaints or bounces, and move senders between pools by behavior. You benefit from that work without staffing it.
The risk: neighbors
The downside is real. If another sender in your pool behaves badly before the provider catches it, the pool's IP reputation can dip and your mail is affected. How much this matters depends almost entirely on how strict your provider is about who it lets into each pool.
The case for dedicated IPs
Isolation
Your IP reputation reflects only your behavior. If you send clean, wanted mail, nobody else can drag it down.
Control and visibility
With dedicated IPs you can enroll in IP-based programs such as Microsoft SNDS and JMRP, look up your IPs on blocklists, and correlate IP-level signals with your own sending. On shared IPs those signals are mixed with everyone else's.
Allowlisting
Some business recipients, especially in regulated industries, allowlist sender IPs in their gateways. A dedicated IP makes that possible.
The risk: you own the consequences
A dedicated IP amplifies whatever you do. Send in bursts, mail stale lists or let complaints rise, and there is no pool to dilute the signal. Low or irregular volume is a problem too: an IP that sends 50,000 messages one day a month and nothing in between looks erratic to receivers and may never build a stable reputation.
A decision guide
| Your situation | Likely better choice |
|---|---|
| Low volume, under tens of thousands of messages a month | Shared |
| Irregular sending: occasional large campaigns, quiet weeks | Shared |
| Steady high volume every day | Dedicated is viable |
| Strict compliance or allowlisting needs from business recipients | Dedicated |
| You want IP-level monitoring and can act on it | Dedicated |
| Your provider's shared pools have a poor track record | Dedicated, or a better provider |
| No one on the team will watch reputation | Shared |
There is no universal volume threshold. Providers commonly suggest dedicated IPs only for senders with consistent daily volume in the many tens of thousands or more, but the deciding factor is consistency. A steady sender at lower volume can do fine on a dedicated IP; a bursty sender at higher volume may not.
How many dedicated IPs?
More IPs are not better by default. Each IP needs enough steady traffic to maintain a reputation. Spreading modest volume across several IPs makes each one look low-volume and irregular. Start with one per mail stream that genuinely needs isolation and add more only when one IP cannot carry the volume receivers will accept from it.
A common pattern is separating streams:
- One dedicated IP, or a small set, for transactional mail.
- A separate IP or shared pool for marketing.
That way a weak campaign cannot affect password resets. You can get much of the same isolation from separate subdomains on shared infrastructure, because domain reputation is tracked separately per stream.
Questions to ask your provider
Before deciding, ask:
- How do you assign customers to shared pools, and on what criteria do you move them?
- How quickly do you act on a customer generating complaints or trap hits?
- If I take a dedicated IP, do you manage warm-up, or do I?
- Can I return to shared pools later without penalty?
- Do dedicated IPs come with a PTR record under my domain?
- What visibility do I get into IP-level data, such as blocklist checks and SNDS?
The answers tell you more than any general rule.
Moving from shared to dedicated
If you do switch:
- Warm up gradually. Move a small share of traffic to the new IP and increase it over several weeks, starting with your most engaged recipients.
- Keep the shared pool during the transition. Send the remainder of your traffic through it while the dedicated IP ramps.
- Set up reverse DNS with a PTR record under your domain that resolves back to the IP.
- Monitor daily for deferrals, bounces and complaint changes, and slow the ramp when they rise.
Checklist
- Measure your daily volume and how consistent it is before deciding.
- Prefer shared IPs for low or bursty volume.
- Choose dedicated IPs only with steady volume and someone to monitor them.
- Separate transactional and marketing streams by IP or subdomain.
- Ask your provider how it manages shared pools.
- Plan a multi-week warm-up for any new dedicated IP.
Key takeaways
- Shared IPs trade isolation for an established reputation and no warm-up; dedicated IPs trade convenience for control.
- Consistency of volume matters more than any single volume threshold.
- Domain reputation travels with you either way, so IP choice is only part of the picture.
- Dedicated IPs amplify both good and bad sending practices.
- Separate streams so one weak campaign cannot hurt critical transactional mail.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
