Infobip Email BYOIP Integration Overview
Worth Knowing
IPv4 /24 minimum; IPv6 is explicitly unsupported. Requires LOA and route object/ROA authorizing AS43009 (AFRINIC, APNIC, ARIN, LACNIC, RIPE NCC) and a maintenance window for cutover.
Searching for the best IP providers? Infobip Email supports sending from customer-owned IPv4 prefixes announced through Infobip's network. Onboarding is coordinated with support or an account manager and requires routing authorization and a signed letter of authorization. Customers retain their addresses, while Infobip provides the email delivery service.
Provider Details
| Field | Information |
|---|---|
| Provider Name | Infobip |
| Product | Infobip Email |
| Website | Infobip |
| ASN(s) | AS43009 (Infobip announcing ASN) |
| Tech Article & Date | Infobip Email - Bring your own IP; Jasper release notes (14 October 2026) |
| BYOIP Scope | Customer-owned public IPv4 prefixes announced through Infobip's network for Infobip Email sending |
| Supported Versions | IPv4 only (/24 or larger). IPv6 is explicitly unsupported for this BYOIP product. |
Caveats and Gotchas
- Customer-owned prefix onboarding is distinct from Infobip's ordinary provider-assigned dedicated IP option.
- IPv6 is explicitly unsupported for Infobip Email BYOIP.
- Allow at least two weeks of preparation time after all required authorization documents are received; onboarding is not instant.
- Cutover requires a scheduled maintenance window; uninterrupted zero-downtime migration is not supported.
- Sending IPs require PTR (reverse DNS) records; agree reverse DNS management or delegation with Infobip during setup, and continue to follow standard deliverability and warming practices.
Technical Requirements
| Requirement | Details |
|---|---|
| Prefix Size | IPv4: /24 minimum (or larger). IPv6: Unsupported. |
| ASN Ownership Required | Not established; the documented routing authorization uses Infobip's ASN (AS43009). |
| ROA & Route Object | Required, authorizing AS43009. |
| LOA | Required, signed by an authorized representative of the prefix holder. |
| RIR Limitations | Supports prefixes registered with AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC. |
| Reverse DNS | PTR records are required for sending IPs; coordinate reverse zone delegation or management with Infobip. |
Step-by-Step BYOIP Process
Step 1
Contact Infobip support or your account manager to initiate Email BYOIP onboarding for your IPv4 /24 (or larger) prefix.
Step 2
Create the required RPKI ROA and route object authorizing AS43009 at your Regional Internet Registry (AFRINIC, APNIC, ARIN, LACNIC or RIPE NCC) and submit a signed LOA.
Step 3
Coordinate reverse DNS (PTR) configuration for the sending addresses and allow at least two weeks after document submission for Infobip's network preparation.
Step 4
Schedule a maintenance window for prefix cutover and verify outbound mail flows and sender authentication after announcement.
Related Resources
Published 6 November 2026