Shared IP intelligence for Klaviyo senders
Nearly every Klaviyo brand sends from shared IPs, so your deliverability is averaged with dozens of companies you have never heard of, and the lineup changes without notice. Nobody shows you who they are. This does: the companies on your addresses, how much of your pool each one holds, and the day Klaviyo quietly moves you.
Check your domain against the panel
184 brands and 311 Klaviyo IPs mapped so far. 294 of those addresses carry more than one company; the busiest carries 58.
Or open a live pool first: bioma.health · duckcamp.com
If none of these have happened to you, you do not need this yet.
The checklist came back clean and the client still wants an answer.
Auth aligned, complaint rate under 0.1%, sunset policy running, nothing changed in the creative, and Gmail placement still slid. You have run out of variables you can observe. Pool composition is the one you never could, and it is the only one that moves without you doing anything.
"Should we pay for a dedicated IP?"
Today that answer is judgement. With a roster it is evidence: here is your pool, here is who else is on it, and here is how much of your pool they occupy. It is also the argument you take to Klaviyo when you want to be moved rather than upsold.
You fixed it. Did the platform notice?
You suppressed the dead weight and tightened the segments six weeks ago. Domain reputation in Postmaster is a coarse, lagging band. A change in the IPs you draw from is an early sign the platform re-rated you, and your DMARC reports show it whole.
Every figure below came from real campaigns and public DNS. You can reproduce all of it.
3,338
Klaviyo shared IPs mapped, across two separate networks
876
Dedicated IPs, resolving to 287 named brands
20,894
Klaviyo campaigns observed, from 184 brands
58
Brands sharing one single address
$ dig +short -x 167.89.100.92 o1308.shared.klaviyomail.com. ← FCrDNS confirms a shared node $ dig +short TXT klaviyomail.com "v=spf1 include:sendgrid.net ~all" ← the SendGrid half $ whois 170.203.24.13 | grep OrgName OrgName: Klaviyo, Inc ← a second network, their own /20 $ dig +short -x 170.203.25.10 kl-203-25-10.k3.mail.horze.com. ← dedicated IPs name the customer
Klaviyo runs on SendGrid, and SendGrid documents the mechanism themselves: "if there is a sender in your pool that starts to underperform, within a day they will be automatically transitioned to a different pool." Sorted by engagement quality, not just complaints. Nobody is notified in either direction.
STEP 01
Comma-separated onto your existing rua=. Nothing about your sending changes
and no subscriber sees anything.
STEP 02
Gmail, Yahoo, Microsoft and the long tail already report every source IP that sent as your domain, with volumes. Adding our address puts us on the same report.
STEP 03
Not when an IP changes, which is constant and meaningless. When the set behind it changes, with the sends that preceded it.
Not because it is hard to build. We checked the category. It is who they sell to.
They run the largest email panel in the industry, and Everest already sells competitive intelligence on what rival brands send. It does not publish co-tenancy. They also sell reputation and certification services to the ESPs whose pools this would expose, at $1,000–2,000 a month. That is a conflict of interest, not a technical gap.
GlockApps and the seed-list tools tell you where your mail landed. A placement test only ever observes one sender, so it structurally cannot see who else was on the address that carried you. That needs a panel receiving many brands at once.
dmarcian, EasyDMARC, Valimail and Postmark's free digest parse the same reports and list every IP that sent as your domain. None cross-references those addresses against other senders, because none of them holds other brands' received mail.
Asked on their own forum why a customer's pool had changed, Klaviyo's answer was “I believe that we have IP pools run on an automatic basis.” SOURCE: KLAVIYO COMMUNITY, “CHANGED IP POOL”
You have been pitched by every vendor in this category. Here is the part they leave out.
Gmail weights domain reputation above IP, and Klaviyo says so themselves. If your domain is the problem this will not save you. IP matters more at Microsoft, which since November 2025 rejects non-compliant bulk mail rather than junking it. SOURCE: KLAVIYO HELP CENTRE, EMAIL DELIVERABILITY FAQs
GlockApps does seed-based placement well. This answers a different question: which infrastructure carried your mail, and who else was on it.
We checked every IP our own panel observed against Spamhaus, Barracuda and SpamCop. All clean. At ESP scale that signal is dead, so we do not sell it.
There is no pool to map. Paste a header into the free check and we will tell you which you are on, then tell you to keep your money.
Rotation and co-tenancy are measured. That Klaviyo's pools are cleanly ranked by quality is inference from SendGrid's documentation, and we will keep labelling it as inference until our panel proves it.
Not a dashboard to check. One document that tells you whether your sending infrastructure changed, so you can stop guessing and go fix the right thing.
Pool audit
£2,500one-off, delivered inside a week
The sample is the exact document, built on a real sender from the panel. Ordering is one email and one DNS record; the report arrives inside a week.
What it will not tell you
Whether your neighbours’ inbox placement moved when yours did. That question needs several senders in the same pool reporting at once, and today we do not have them. When we can answer it we will, and until then we would rather write this than guess.
It also cannot move you. Klaviyo requires roughly a million marketing emails a month plus an enterprise plan before a dedicated IP is on the table, so for almost everyone the pool is not a choice. What changes is that you stop paying for the wrong fix.