Can You Bring Your Own IPs to an SMTP Provider?

On shared relays the answer is almost always no. Amazon SES is the notable exception: its BYOIP feature accepts a full /24 (256 addresses) registered with an RIR to a business entity, with a clean history, for a monthly fee per address. Getting your own /24 in the first place costs roughly $9,000 to $14,000 on the IPv4 transfer market plus around EUR 1,550 a year for LIR membership. Below about 5 million emails a month, none of that pays for itself, and a dedicated IP that comes with a server does the same job.

The question people ask is "can I bring my own IPs." The question they actually mean is "do I have to start from zero every time I change providers." Those are different problems with different fixes, so let me separate them.

The three levels of IP ownership

Almost every argument about BYOIP falls apart because people mix up three very different arrangements. Here they are, from least to most yours.

Level 1 is what most senders have. Level 2 is what a self-hosted or managed dedicated SMTP setup gives you. Level 3 is the only one that is genuinely "your IP" in the sense a lawyer would recognise.

The gap between level 2 and level 3 is smaller in daily operation than people expect and larger in the one scenario that matters, which is leaving.

Why most providers refuse BYOIP

Every shared relay I've asked has said no, and their reasons are consistent. Two of them are good reasons.

They cannot vouch for the history. An IP block has a past. It might have been a spam operation's block three years ago, sitting on UCEPROTECT level 2 and half a dozen private blocklists nobody publishes. The provider inherits that mess the moment they announce your range from their network, and their other customers' ranges sit in the same neighbourhood.

It breaks pool management. A relay's whole model is moving traffic between IPs based on live reputation. If your addresses are pinned to your account and cannot be swapped, rebalanced or retired, you are a special case in a system designed to have none. Support cost goes up, automation goes down.

The third reason is commercial. Dedicated IP add-ons at $24.95 to $59 a month are pure margin. A customer who brings their own is one they cannot upsell.

I've listed only what these vendors publish. If a provider does not document a BYOIP program, assume there isn't one, because a program like this needs legal paperwork and a documented process to exist at all.

What Amazon SES actually requires

SES publishes its conditions, and they are stricter than most people expect. Straight from the SES BYOIP documentation:

You email the request in and AWS responds within 48 business hours. It is a review, not a form submission, and the stated purpose is stopping their platform being used for unsolicited mail.

Read the second requirement again. "Registered to a business or institutional entity and can't be registered to a person" rules out most individual senders before anything else. So does the /24 floor, because you cannot buy 4 addresses and bring those.

What it takes to get your own block

Assume you want level 3. Here is the actual path, and none of the steps are optional.

1. Become an LIR or work through one. At RIPE NCC that means membership, roughly EUR 1,550 a year plus a one-time sign-up fee. ARIN charges annual registration fees on a similar scale. Some sponsoring LIRs will hold the resource for you for a few hundred a year instead.
2. Get the IPv4 space. There is no free pool left. RIPE hands out at most a /24 from a waiting list that has run years long, so in practice you buy on the transfer market at roughly $35 to $55 per address, which is $9,000 to $14,000 for a /24.
3. Get an ASN if you need one. Free to cheap at the registry level, but you only need it if you announce the block yourself or want it portable across hosts. If one host announces it for you, skip it.
4. Sign ROAs under RPKI. A Route Origin Authorisation says which ASN may announce your prefix. Plenty of large networks now drop routes that fail RPKI validation, so an unsigned prefix is partially unreachable rather than merely untidy.
5. Find a network that will announce it. Not every host does BGP for customer prefixes. The ones that do usually want a commit, a signed LOA, and a technical contact who can answer questions about your routing.

Realistic timeline: 6 to 12 weeks from decision to first packet, most of it waiting on the transfer and the RIR paperwork.

Note what step 5 means. Owning the block does not make it reachable. Somebody with a network still has to announce it, and if they drop you, your mail stops until another network picks it up.

The reputation portability question

This is the real reason people ask about BYOIP, so here it is plainly.

Six to eight weeks of warm-up at 30% ramp every two days is real work and real deferrals. Doing it twice because you changed vendors is the cost people are trying to avoid.

But be honest about the size of that cost. A warm-up is 4 to 8 weeks of reduced volume, once, at a provider change you might make every three years. Against $9,000 to $14,000 plus EUR 1,550 a year, the maths only works if you are switching often or your sending is large enough that eight weeks at reduced volume is a six-figure revenue hole.

There is a second, quieter benefit. An IP registered to your company cannot be taken away by a provider's policy team over a use case they decided they no longer like. If you have been shut down mid-campaign before, you already know what that is worth.

The cost comparison across all three levels

Twelve months, three dedicated IPs' worth of sending capacity, so it is like for like.

The last row is the only one that argues for level 3 on money. IPv4 addresses have held value for a decade, so a /24 is closer to an asset than an expense. That is a treasury argument, not a deliverability one, and I'd rather you decide it as such.

When BYOIP is genuinely worth it

Four situations, and I've seen all four work.

• Sustained volume above 5 million a month. At that scale eight weeks of warm-up costs more than the block, and you probably need multiple IPs anyway.
• You resell sending. An ESP with customers on your infrastructure cannot afford to re-warm the whole platform because an upstream vendor changed terms. SMTP infrastructure for ESPs reselling email covers the pool segmentation that goes with it.
• You have been shut down before. If a provider's policy team has killed your sending once over a legitimate use case, owning the addresses removes that specific risk permanently.
• You already run network infrastructure. If you have an ASN, a BGP session and someone who understands RPKI, the marginal cost is paperwork rather than a new capability.

And when it is not worth it, which is most of the time:

• Under about 5 million emails a month. The setup cost exceeds the value of the warm-up you are protecting, by a lot.
• You want better delivery. A fresh /24 has no reputation. It warms up exactly like a rented IP, over the same 4 to 8 weeks. Ownership buys portability, not inbox placement.
• You do not have a business entity. RIRs and AWS both require one. This is a hard stop, not a hurdle.
• You cannot fill the addresses. A /24 is 256 IPs and each one needs roughly 1,000 to 2,000 emails a day to hold a reputation. Most senders can keep 3 to 5 warm, not 256.

That last point deserves emphasis. You do not have to announce all 256, and nobody does. But if you bought a /24 to use 4 addresses, you spent $12,000 to solve a $549 problem. Work out how many IPs your volume can actually keep warm before anything else, and dedicated IP vs shared IP plus do you need a dedicated IP will get you to that number.

The decision, in order

Run these four questions top to bottom and stop at the first no.

Most people reading this stop at the first row, and that is the correct answer, not a consolation. A dedicated IP assigned to a server you control gives you your own PTR, your own reputation, nobody else's complaints on your addresses, and no shared-pool policy team. The only thing it does not give you is the ability to walk out with the addresses.

How BulkEmailSetup helps

We build dedicated SMTP infrastructure at level 2: your own server, your own dedicated IPs, full SPF, DKIM, DMARC and PTR configuration, MTA tuning, bounce handling and a warm-up schedule that matches your list, not a generic curve. Nobody else sends from those addresses and no policy team decides whether your use case is too risky for other customers on a pool.

Basic is $549 one-time, covering 1 SMTP server, 3 dedicated IPs, 25,000 emails/day and unlimited contacts. Higher tiers scale to 15 IPs and 200,000 emails/day. See pricing. If you get to the volume where owning a /24 makes sense, you will already have the warm-up process and the monitoring in place to use it.

Frequently asked questions