Shared IP Pools: How a Stranger’s Sending Can Hurt Your Inbox Rate

Most senders never choose an IP. You sign up for a provider, send, and your mail leaves from an address shared with hundreds or thousands of other accounts. Receivers score that address, which means part of your reputation is decided by people you will never meet.

How pool reputation works

Receivers maintain reputation at several levels at once: IP, domain, and increasingly the combination. The IP component answers "has mail from this machine been wanted?" — measured by complaint rates, spam-trap hits, bounce rates and engagement across *everything* the IP sends.

On a shared IP you inherit that aggregate. One account blasting a purchased list can move the pool's complaint rate enough to push every sender on it from inbox to Promotions, or from Promotions to spam. You will see it as an unexplained drop that correlates with nothing you changed.

The flip side is real: a well-managed pool with high volume and low complaints gives a small sender far better standing than they could build alone. Domain reputation then does the work of distinguishing you inside the pool — which is why SPF, DKIM and DMARC alignment matter even more on shared infrastructure.

Diagnosing a pool problem

The tell is a deliverability change you cannot attribute to your own behaviour. Check in this order:

1. Find your sending IP. Read the Received header of a test message, or the X-Originating-IP if your provider sets one.
2. Check it against blocklists — Spamhaus, Barracuda, SORBS, and the vendor lists your recipients' filters subscribe to.
3. Compare domain and IP reputation. If your authentication passes, your content is unchanged, your complaint rate is flat, and placement still fell, the IP is the variable.
4. Test from a second path. Send the same message through a different provider to the same seed mailboxes. If one path lands and the other does not, you have isolated it.

Shared versus dedicated

A dedicated IP is not an upgrade by default. It gives you full control and full blame, and it needs volume to work: receivers build IP reputation from observed traffic, so an IP sending a few hundred messages a week stays permanently unknown, which behaves like mildly suspicious.

Rough guidance:

Moving to a dedicated IP also means warming the IP, not just the domain: a slow volume ramp over two to four weeks while receivers form an opinion.

What you control on a shared IP

• Pick the provider deliberately. Ask how they police the pool, whether they segment by sending type, and whether cold outreach shares IPs with transactional mail. Providers that answer vaguely are telling you something.
• Protect your domain reputation. It is the part of the signal that is yours. Authenticate, keep lists clean, keep complaint rates low.
• Separate your streams. Cold outreach, marketing and transactional mail should not share a sending identity, whatever the IP situation.
• Monitor placement, not just delivery. "Accepted" tells you nothing about which folder. Seed-inbox testing across Gmail, Outlook and Microsoft 365 is the only way to see a pool problem early.

MailPilot tracks placement and reputation per mailbox per day, so when a shared pool turns against you it shows up as a dated inflection in the chart rather than a quarter of bad results you explain away afterwards.