Platform/Connectivity/Public IP

Addresses that belong to your services.

IPv4 and IPv6 allocations with reverse DNS and BYOIP — the boring resource that's suddenly expensive everywhere else.

IPv4 + IPv6BYOIPReverse DNS

Talk to us All Connectivity

Capabilities

Public addressing, sorted

Flexible, reliable and built for the way you operate.

Dual stackIPv4 and IPv6 side by side on every service.IPv4 and IPv6 together

Bring your ownAnnounce your existing ranges from our network (BYOIP).Your ranges, announced

Reverse DNSPTR records managed with the allocation — mail servers thank you.

PTRs managed properly

PortabilityMove addresses between services without re-architecting.

IPs follow workloads

RPKI validatedAnnouncements are signed and validated against hijack.

Route integrity proven

Reputation careClean ranges with abuse handling that actually answers.

Mail that lands

Elastic attachmentRe-map addresses between servers in seconds.

Failover-friendly IPs

Geo-consistentAddresses geolocate to your served region.

Right country, right content

Usage inventoryEvery address accounted to a workload and an owner.

No orphan IPs

Firewall-integratedPublic IPs land behind your policy by default.

Exposed on purpose only

Compare the allocations

IPv4, IPv6, or bring your own

All three come with reverse DNS and a managed address plan — the difference is whose address space it is.

ProductionEdgeComing soon

ALLOCATION 01Most common

IPv4 Allocations

The addresses everything needs

IPv4 blocks assigned to your estate with reverse DNS and documented allocation — the scarce resource, handled without scarcity pricing.

Best for

Public endpointsVPN concentratorsMail & service IPs

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiSingaporeAbu DhabiMilanFrankfurtNairobi

Plans

Block/29 · 5 usable addresses · rDNSSign in →Block Plus/28 · 13 usable addresses · rDNSSign in →CustomAny block size your services needSign in →

ALLOCATION 02

IPv6 Allocations

Room to stop worrying

IPv6 prefixes for services that should have been dual-stacked already, with the same routing and reverse DNS management.

Best for

Dual-stack servicesMobile-facing platformsModern APIs

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

Prefix/64 per subnet · rDNSSign in →Prefix Plus/56 per network · delegated managementSign in →CustomAny prefix size and delegation modelSign in →

ALLOCATION 03

Bring Your Own IP

Your space, announced

We announce your existing ranges from our network, so a migration keeps every address, firewall rule and reputation intact.

Best for

Datacentre migrationsMail reputationFixed partner allow-lists

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

BYOIPYour prefix announced · rDNS delegatedSign in →BYOIP PlusMulti-zone announcement · RPKI validatedSign in →CustomAny prefix set and announcement policySign in →

Two ways to hold them

Assigned to the estate, or drawn from a pool

Both include reverse DNS and documentation. The difference is whether addresses belong to the estate or come from a shared pool.

To the EstateEstate-wideSpecific blocks assigned to your estate and documented against your services.

Addresses tied to named services

Reverse DNS managed for you

No per-address scarcity pricing

Best for:Stable public estates

Explore To the Estate plans

To a PoolSelf-service poolA shared pool your team allocates from through the console or API, with IPAM keeping the record straight.

Self-service allocation inside quotas

IPAM as the source of truth

Reclaim addresses when services retire

Best for:Platform teams shipping often

Explore To a Pool plans

Who decides, who runs it

What each group gets from Public IP

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“Addressing stopped being a migration blocker”

Existing ranges move with the estate, so partner allow-lists and mail reputation survive the transition.

GovernedSovereignPredictable

FAQs

Can we keep our existing IP ranges?

Yes — BYOIP lets us announce your prefixes, so allow-lists and reputation follow you.

Is IPv6 available everywhere?

In production regions today, with edge locations following as they are upgraded.

Who manages reverse DNS?

We do, or you do through the API — either way it is part of the service rather than an afterthought.

Are addresses charged individually?

No. Allocations sit inside the flat fee; there is no per-address monthly meter.

How are allocations tracked?

Through IPAM in Virtue Suite, so every address has an owner, a purpose and a history.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together