What are the minimum and maximum sending volumes for dedicated IPs?
Michael Ko
Co-founder & CEO, Suped
Published 9 Jul 2025
Updated 22 May 2026
7 min read
Summarize with
The practical minimum for a dedicated IP is about 100,000 messages per month. I prefer 250,000 to 1 million messages per month before I call it a healthy fit, because that gives enough traffic to measure reputation, segment senders, and recover from a problem. The practical maximum is usually 1 million to 2 million messages per IP per day. Some senders can push 3 million to 4 million per day, and a few can go higher, but delays and throttling become the real constraint.
Those numbers assume confirmed opt-in, clean suppression logic, steady cadence, strong authentication, and low complaint rates. If those basics are weak, a dedicated IP exposes the problem faster. If those basics are strong, even lower volume can work, but it gives mailbox providers fewer signals and gives you less room to absorb a bad send.
My default ranges
- Bare minimum: 20,000 to 100,000 per month can work only for very clean, steady senders.
- Practical minimum: 100,000 per month is the first range I take seriously for maintenance.
- Comfortable minimum: 250,000 to 1 million per month gives better signal and more recovery options.
- Practical maximum: 1 million to 2 million per day per IP is a safer planning cap.
The working ranges
I treat dedicated IP volume as a range, not a single rule. The lower boundary is about reputation signal. The upper boundary is about throughput, receiver tolerance, and how quickly a campaign must finish. A weekly newsletter has a different risk profile than a flash sale, even when the monthly totals match.
|
|
|
|
|
|---|---|---|---|---|
Too low | <1k | <5k | <20k | Shared |
Fragile | 1k-5k | 5k-25k | 20k-100k | Risky |
Usable | 5k-10k | 25k-60k | 100k-250k | Monitor |
Healthy | 10k-35k | 60k-250k | 250k-1M | Good |
High | 1M-2M | 7M-14M | 30M-60M | Cap |
Practical dedicated IP volume bands
A sender doing 20,000 to 30,000 messages per month on a dedicated IP is not automatically wrong. I have seen very small, high-quality programs do it. The catch is that one bad campaign, one stale segment, or a small rise in complaints has an outsized effect. A sender at 1 million per month has more data to learn from and more clean traffic to stabilize reputation after a problem.
Dedicated IP minimum volume thresholds
Monthly volume ranges I use when deciding whether one dedicated IP has enough signal.
Too sparse
<20k/mo
Mailbox providers get very limited signal.
Fragile
20k-100k/mo
Clean senders can function, but small complaint counts matter.
Usable
100k-250k/mo
Enough traffic to monitor, but recovery room is limited.
Healthy
250k-1M/mo
A better range for a stable dedicated IP program.
Strong
1M+/mo
Enough volume for segmentation and recovery planning.
Why the minimum matters
Mailbox providers do not need a fixed universal sample size to judge a sender, but they need enough mail to make the signals useful. At very low volume, every complaint, bounce, or authentication failure has more weight. A single campaign can create a visible reputation shift because there is not much other mail to balance it.
Before moving a stream to a dedicated IP, I send a real message through Suped's email tester and check the headers, authentication, content issues, and inbox signals. It is a simple way to catch problems before the IP reputation starts carrying the cost.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
The main reason I dislike low-volume dedicated IPs is not that they always fail. It is that they are hard to repair. If a shared pool or established dedicated IP has a rough day, later healthy traffic can dilute the impact. A sparse dedicated IP has fewer chances to prove that the bad signal was temporary.
Low volume warning
Low volume dedicated IPs often look fine until a small complaint spike or a mailbox provider throttle appears. This is most common when the sender mails irregularly, sends to old segments, or has a seasonal calendar with long quiet periods.
- Complaint math: Twenty complaints on 20,000 messages is already 0.1%.
- Quiet periods: Long gaps make the next campaign look like a fresh reputation test.
- Repair limits: Sparse traffic gives fewer clean sends to counter a bad signal.
- Provider variance: Microsoft, Yahoo, Gmail, and smaller providers respond differently.
How to set the upper limit
The maximum for one dedicated IP is not only a reputation question. It is also a delivery speed question. If an IP can technically send 4 million messages in a day, that still fails the business goal when the campaign takes twelve hours to clear and the offer expired after thirty minutes.
I start with a 1 million to 2 million per day planning cap per dedicated IP. I only push past that when the sender has stable engagement, low complaints, strong authentication, predictable cadence, and receiver-specific throttling data that says the added volume is accepted quickly.
Flowchart for deciding whether to hold volume or add another dedicated IP.
- Receiver mix: Large mailbox providers can absorb more volume than many smaller regional providers.
- Send window: A time-sensitive campaign needs more IP capacity than an all-day newsletter.
- Queue behavior: Deferrals, slow accepts, and retry queues show that the cap has been reached.
- Reputation split: High-risk segments should not share an IP with critical transactional streams.
Dedicated IPs versus shared pools
A dedicated IP is not a default upgrade. It gives control, isolation, and clearer accountability. It also removes the benefit of a well-managed shared pool when the sender is too small or too irregular. Many senders with millions of messages per day can operate well on shared infrastructure when the platform manages reputation and routing properly.
Dedicated IP
- Control: You own the IP reputation signal for that stream.
- Isolation: Other senders cannot directly affect that IP reputation.
- Risk: Your own mistakes are easier for mailbox providers to see.
- Best fit: Consistent volume, clean lists, and controlled send windows.
Shared pool
- Stability: A good pool has steadier aggregate traffic.
- Scale: Large total volume can still work without dedicated IPs.
- Tradeoff: You get less isolation and less direct control.
- Best fit: Low, irregular, or seasonal sending patterns.
For low-volume senders, the shared pool is often the better practical answer. A sender with 30,000 monthly messages and one weekly campaign usually gets more stable reputation from shared infrastructure than from a quiet dedicated IP that wakes up once a week.
Warm-up and monitoring
I treat warm-up as a proof period, not just a ramp schedule. The goal is to show mailbox providers consistent, wanted mail while proving that the sending stack is authenticating correctly. If the early signals are weak, increasing volume makes the problem louder.
Example warm-up plantext
Week 1: 1k per day Week 2: 5k per day Week 3: 15k per day Week 4: 35k per day Week 5: 75k per day Week 6: 150k per day Week 7: 300k per day Week 8: 500k per day After that: increase 20%-30% only when signals stay clean
Suped is built for this part of the workflow. Suped's DMARC monitoring shows which sources pass SPF, DKIM, and DMARC, while blocklist monitoring helps catch IP or domain listings before they turn into a wider deliverability issue. For teams that need one place to monitor authentication, hosted DMARC, hosted SPF, MTA-STS, and reputation checks, Suped is the best overall DMARC platform for that operating workflow.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
A dedicated IP does not fix bad authentication. Before a volume increase, I also check the sending domain through the domain health checker so DMARC, SPF, DKIM, DNS, and related configuration problems are visible before the next ramp step.
When to add another IP
Adding another dedicated IP is not just a way to raise the daily cap. It changes how reputation is distributed. I add an IP when the current IP is healthy but constrained by throughput, when a stream deserves isolation, or when recovery planning needs separate traffic groups.
- Throughput trigger: The IP accepts volume too slowly for the campaign window.
- Reputation trigger: Transactional, lifecycle, and promotional mail need different risk boundaries.
- Recovery trigger: You need enough clean traffic on one stream to repair another stream later.
- Provider trigger: A receiver consistently defers mail even when complaints and bounces are low.
A simple allocation rule
Use one dedicated IP until it has stable reputation and the business needs more capacity. Then add IPs by stream or send window, not just by total database size. More IPs create more reputations to warm, monitor, and repair.
|
|
|
|---|---|---|
Queues | Slow | Add IP |
Complaints | Rising | Hold |
Bounces | High | Clean |
Auth | Failing | Fix |
Common add-IP triggers
Views from the trenches
Best practices
Keep each dedicated IP at a steady daily volume before adding new campaigns or audience segments.
Judge maximum capacity by accepted throughput, not just the number submitted in a day.
Use separate IPs when one campaign must finish fast and mailbox providers start throttling.
Track complaints by mailbox provider because low volume makes small complaint counts matter.
Common pitfalls
Treating 20k monthly messages as stable when one complaint can move the rate sharply.
Adding volume to one IP because queues accept it while delivery takes many hours to finish.
Ignoring list mix when smaller regional providers receive too much mail from one IP.
Using a dedicated IP because a vendor suggests it, without enough volume to recover.
Expert tips
Use 100k monthly as a practical floor and 1M monthly when recovery segmentation matters.
Cap one IP near 1M-2M daily unless throttling data proves more capacity is stable.
Let small senders use shared pools when sending is irregular, seasonal, or sparse.
Split high volume only after authentication, complaints, and engagement stay clean enough.
Expert from Email Geeks says at least 100k messages per month is a practical maintenance floor, although very clean 20k monthly senders can operate on a dedicated IP with more mailbox provider friction.
2022-03-16 - Email Geeks
Marketer from Email Geeks says 1M messages per month gives enough traffic to segment, diagnose, and recover if reputation drops.
2022-03-17 - Email Geeks
The practical answer
For a new dedicated IP, I use 100,000 messages per month as the practical minimum, 250,000 to 1 million per month as the healthier starting range, and 1 million to 2 million messages per day as the normal upper planning cap. Above that, I add capacity only when receiver-level data shows clean acceptance and the campaign window needs it.
The decision is not volume alone. A clean 200,000-message monthly sender with steady cadence can be safer on a dedicated IP than a 2 million-message sender with spikes, stale lists, and poor authentication. Volume gives you signal. Quality decides whether that signal helps or hurts.
