When dedicated IPs make sense
Three rough thresholds help decide. Below 50,000 emails per month, shared sending is almost always cheaper per email and the reputation build time for a dedicated IP is longer than you have volume to sustain. Between 50,000 and 250,000, a single dedicated IP starts to pay back because the warm-up completes in a reasonable window and you benefit from full reputation isolation. Above 250,000 per month, dedicated IPs become essential: shared providers throttle heavy senders and you want your reputation in your own hands.
Special cases where dedicated IPs are needed regardless of volume: regulated industries where you need auditable control of the sending infrastructure, cold email programmes that benefit from domain+IP isolation per campaign class, recovery scenarios after a shared IP pool got blacklisted through no fault of your own, and multi-brand agencies running 5+ end clients where reputation isolation per client matters.
How our warm-up differs from a generic schedule
Most IP warm-up guides hand you a table: day 1, 50 emails; day 2, 100; day 3, 200; etc. That table is a starting point, not a plan. It ignores content engagement, list quality, per-ISP variance and the current market behaviour of spam filters in 2026. Our warm-up is a managed process: we send real engagement traffic from our 50,000+ inbox network during the first two weeks, mix in your real campaigns at graduated percentages, pause when bounce or complaint rates trend the wrong way, and escalate to a specialist if signals are contradictory.
The AI Assistant continuously analyzes warm-up signals — DKIM/SPF/DMARC alignment, content patterns, reputation drops detected by Postmaster Tools, anomalies in Microsoft SNDS data — and surfaces specific issues with recommended actions. Real-time Spamhaus protection auto-pauses sending if a listing is detected, preventing the situation where the warm-up continues to send while reputation is compounding damage. At the end of the warm-up window, you receive a handoff report with the established reputation baseline, recommended steady-state limits per ISP, and any lingering issues that will shape your first weeks of real sending.
What happens if you burn an IP
Stuff happens. A bad content test, a forgotten list hygiene cycle, a cold-email cadence that is too aggressive, a spamtrap hit from a list segment that should have been cleaned — sometimes an IP's reputation drops despite good practices. Our standard response is: investigate, fix the upstream cause, run a recovery warm-up, and if recovery is not economic, rotate the IP out of your pool at no charge. The 5 IP pool plan and above include automatic replacement-on-blacklist (Spamhaus excluded because Spamhaus needs behavior fixes upstream, not IP swaps).
Three principles guide our approach to burned IPs. First, investigate the cause before requesting delisting. Premature delisting requests get re-listed within days, often with worse standing. Second, fix the upstream issue, then rebuild reputation. Rotating IPs without fixing the cause means the new IPs burn too. Third, rotate when uneconomic, not when convenient. Some IPs can be rehabilitated with 2-4 weeks of focused remediation; others have structural damage that costs more than the IP is worth. We tell you which is which on the diagnostic call.
Dedicated IPs by industry — what each operator profile actually needs
Five operator profiles dominate our dedicated IP client base, and the IP allocation patterns differ significantly. Understanding which profile fits shapes the right pool size and warm-up approach.
E-commerce and marketplace operators sending order confirmations, shipping updates, abandoned-cart reminders and lifecycle marketing run a hybrid pool: 2 IPs dedicated to transactional traffic with priority queuing (so password reset arrives in 5 seconds even mid-campaign), 3-5 IPs for marketing with broader throttling tolerance. Transactional IPs sustain very high per-IP volume because engagement is strong; marketing IPs follow conventional per-IP caps. Typical setup: 5-IP pool €114.75/mo for sub-1M monthly senders (€22.95 × 5), scaling to /29 subnet €137.70/mo (6 usable IPs) as volume grows past 1M.
SaaS companies running product-driven email (signup confirmations, billing notifications, feature announcements, lifecycle nurture) often start with a Single Email IP at €22.95/mo for the transactional flow and add a 5-IP pool €114.75/mo when marketing volume exceeds 250K monthly. The hybrid pattern: critical operational mail isolated on its own dedicated IP, marketing on the pool. The architectural separation prevents marketing complaint signals from bleeding into transactional reputation.
Publishers and newsletter operators running 5-10 newsletter brands on a single platform need IP allocation by aggregated volume rather than per-newsletter. A single 5-IP pool €114.75/mo serving all newsletters at 2-15M monthly is more reputationally stable than 10 single-IP allocations because each IP gets enough volume to maintain warm reputation. We do this allocation calculation during onboarding — operators new to dedicated IPs frequently want one IP per brand, which is the wrong architecture.
Cold-email agencies and outbound operators running B2B outreach for multiple clients need different IP allocation than marketing operators. Cold email per-IP capacity is lower (5K cold sends/IP/day max), so 1M monthly cold email needs ~8 IPs. Our /29 subnet plan €137.70/mo (6 usable IPs in /29 block + BGP available) suits this profile, with custom rDNS per IP allowing each client to have apparent separation. Above 5M monthly cold email, we typically recommend our Cold Email Infrastructure product instead, which bundles pre-warmed mailboxes with the underlying IP pool.
Enterprise IT teams consolidating internal mail traffic from corporate applications (HR systems, ERP notifications, monitoring alerts, internal newsletters) typically need 2-3 dedicated IPs serving 200K-2M monthly internal volume. The cost saving versus per-application SaaS subscriptions is real; the deliverability improvement on internal-to-external corporate mail is also real because dedicated IPs avoid the shared-pool reputation drag of Office 365 SMTP submission limits.
Hosting and infrastructure clients running web servers, application backends, API endpoints, or CDN edge nodes use our €7.95/IP hosting product instead — this is a different product category from the email IPs above, with no deliverability stack because the workload is not email outbound. Common use cases: dedicated IPs for SSL/TLS certificate isolation per domain, IPs for outbound API calls that need consistent egress addresses, IPs for application-level rate limiting that depends on stable client IPs. Do not buy hosting IPs intending to send email — see the disclaimer above and the FAQ below for why.
Provisioning timeline — what the first 60 days look like
Day 1: payment received, provenance audit on candidate IPs runs within 4 hours (history check, ownership verification, 60+ blacklist screening). rDNS configured to match your sending domain. SPF, DKIM 2048-bit selector, DMARC records generated for you to publish on your domain. We confirm DNS propagation before any traffic flows. By end of day 1 the IPs are technically ready but operationally cold — no traffic yet.
Days 2-7: warm-up traffic begins from our 50,000+ inbox engagement network. Initial volume 50-200 emails per IP per day, calibrated to your typical content profile. Per-ISP throttling profiles tuned based on early signals from Gmail Postmaster Tools and Microsoft SNDS (registration confirmed receiving data). AI Assistant active, real-time Spamhaus monitoring active. We meet briefly mid-week to review early reputation signals. At this stage you can start moving small portions of real campaign traffic, but we recommend keeping shared-pool fallback active for the first 14 days.
Days 8-30: ramp-up phase. Volume scales 1.5-2× per IP per day based on engagement signals. Bounce and complaint rates monitored continuously. Any reputation alerts trigger temporary throttling and root-cause review. AI Assistant surfaces specific patterns warranting attention. Real-time Spamhaus protection auto-pauses if a listing is detected. By day 30 most workloads have reached 50-70% of target capacity with stable reputation signals.
Days 31-60: consolidation phase. Volume reaches target capacity. Postmaster Tools showing High reputation in Gmail (or stable Medium for very new domains), Microsoft SNDS Green or Yellow, Yahoo Sender Hub Reputation Score above 70. Daily reporting active in Grafana with read-only access for client. The shared-pool fallback can be decommissioned once you are comfortable with the dedicated infrastructure performance. Handoff report delivered with steady-state recommendations.
Day 60+: steady-state operation. Continuous monitoring through the entire IP lifecycle: daily blacklist scans, weekly specialist review, real-time Spamhaus protection, AI Assistant continuously surfacing optimization opportunities. The 60-day timeline assumes a clean sender profile with established domain reputation — senders with damaged domain reputation should plan for 90 days because the domain reputation rebuild adds runway.
