The correct number of dedicated IPs is usually the smallest pool that supports stable volume and meaningful traffic separation. More cold IPs can create more operational risk, not more deliverability.
Start with message streams, not an IP count
Document transactional notifications, marketing campaigns, brands, business units and any customer-specific traffic. Separate streams only when they have different audiences, risk, operational ownership or provider policies.
If volume is low or irregular, a shared or managed pool may establish reputation more consistently than several dedicated addresses.
Use the smallest sustainable pool
Each dedicated address needs enough steady, permission-based traffic for mailbox providers to observe a consistent pattern. Splitting the same volume across too many addresses can keep every address cold and make measurement less useful.
- Forecast ordinary daily volume and peak volume separately
- Reserve isolation for meaningful message or brand boundaries
- Map every IP to a deliberate PTR and HELO identity
- Define provider-specific throttling and connection policies
- Keep a documented rollback and pause procedure
Warm-up is a controlled observation period
Warm-up should begin with the most engaged recipients who have clearly requested the messages. Volume increases only when bounces, complaints, deferrals and engagement remain within the programme's operating thresholds.
A calendar alone is not a warm-up strategy. Provider responses and audience quality determine whether the next increase is justified.
IP rotation is not remediation
When an address is blocked or reputation falls, stop and investigate the underlying cause. Review consent, acquisition source, complaints, content, identity, compromise and volume changes. Rotating to a fresh address to avoid filtering is not a legitimate operating practice.