Dedicated IPs

Dedicated IPs

By default your endpoints share the region's edge IPs with other tenants. A dedicated IP gives an endpoint a stable, exclusive ingress address — useful when a partner or upstream firewall needs to allowlist a single, unchanging IP. Manage them from Account → Dedicated IPs (/account/dedicated-ips).

There are two modes, and they are mutually exclusive on a single endpoint:

  • Single — one IP in one region. Your endpoint hostname publishes as a plain DNS A record pointing at that fixed IP. Best when all your traffic ingresses in one region.
  • Per-region (GeoDNS) — a group of one IP per region (two or more), geo-routed via Route 53 geolocation. Your endpoint hostname publishes as a CNAME to the group's geo FQDN (grp-<id>.<geo-zone>), and each visitor resolves to the nearest regional IP — so callers worldwide hit a stable, exclusive address close to them.
Plan-gated & billed: dedicated IPs require the dedicated_ips entitlement and a valid payment method on file. The page shows the monthly add-on price (charged per IP) and tells you which blocker applies — an upgrade prompt if your plan doesn't include the entitlement, or a payment-method banner if it does but you have no card. A one-time setup fee may also apply — see Pricing & the setup fee below.

Request → approve flow

Dedicated IPs are provisioned through a request that an administrator reviews — they aren't allocated instantly self-serve.

  1. Request. Click Request dedicated IP and choose a mode:
    • Single — pick the one region you want the IP in (required).
    • Per-region — pick two or more distinct regions (required); approval allocates one IP per region as a geo-routed group.
    Optionally add a reason. The request is submitted for review, and you can cancel a pending request before it's actioned.
  2. Admin approval. An administrator reviews and approves the request (or rejects it). For a single request the admin picks an IP from that region's pool; for a per-region request the system auto-assigns one IP per chosen region — no manual pick. Once approved, the IP (or group) appears in your assignments.
  3. Billing starts on assignment. The monthly add-on charge (per IP) applies once the IP is assigned to your account, alongside any one-time setup fee — see Pricing & the setup fee.
Per-account cap: an account can hold at most 6 dedicated IPs total. A per-region request counts each region toward that cap, so a request that would push you over is rejected.

The page is organised into tabs — your assigned IPs, your per-region groups, your requests (with status and mode), and current attachments (which endpoint each IP or group is bound to) — each independently paginated.

Attach & detach to endpoints

An assigned IP (or group) does nothing until you bind it to an endpoint. You can attach from two places:

  • From the Dedicated IPs page — pick an endpoint and one of your assigned IPs (or a per-region group) and attach.
  • From the endpoint's settings — the endpoint settings page offers an attach/detach control.

Single IP

Attaching a single IP updates the endpoint's DNS to a plain A record pointing at the dedicated IP. Detaching reverts the endpoint to the shared region target (and updates DNS back).

Per-region group

Attaching a per-region group publishes the endpoint hostname as a CNAME to the group's geo FQDN (grp-<id>.<geo-zone>), so visitors resolve to the nearest member IP. Detaching reverts the endpoint to the shared region target.

Only endpoints eligible for a dedicated IP appear in the attach picker.

Mutually exclusive: an endpoint can carry a single IP or a per-region group, never both. Attaching one automatically clears the other.
Apex caveat: a geo CNAME can't sit on an apex (root) domain, so per-region groups attach to a sub-domain endpoint, not an apex hostname. For a single IP this isn't a concern (it's a plain A record). If per-region (GeoDNS) routing isn't configured on the server, the group attach is refused with a 503.

Pricing & the setup fee

Two charges apply to dedicated IPs:

  • Recurring add-on — a monthly per-IP charge for as long as the IP is assigned. A per-region group bills per member IP (one charge per region).
  • One-time setup fee — a single charge applied when an IP is provisioned. The amount differs for single vs per-region, and the per-region fee is charged per region (× the number of regions in the group).

The setup fee is set by your provider's administrators — there's no self-serve control for it — and the request modal shows the applicable amount before you submit. Two important details:

  • The setup fee is non-refundable: releasing or downgrading an IP does not credit it back (the recurring add-on stops as usual).
  • The setup fee is charged again on re-activation — if a standby IP is re-attached after a downgrade-then-upgrade (see below), the setup fee applies once more.

Releasing a per-region group

From the Dedicated IPs page you can release a whole per-region group in one action. This frees all member IPs, stops their billing, reverts any attached endpoints to the shared region target, and deletes the group's GeoDNS record set. Releasing an already-released group is a harmless no-op.

You can also release a single member of a group (it's an assignment like any other). When you do, the group reconciles its geo set automatically — it rebuilds the record set from the remaining members, or, if you've released the last member, tears the group down entirely.

Release & the standby window

Releasing a dedicated IP (single or group) stops its billing and reverts any attached endpoints to the shared region target. You can release from the Dedicated IPs page at any time.

When an IP is released because of a plan downgrade, it isn't handed straight back to the general pool. Instead it's parked in a standby reservation for your account for 7 days. If you re-subscribe (re-upgrade) within that window, the same IP is re-attached to your account — so a downgrade-then-upgrade doesn't cost you your stable address. A parked per-region group is reconstituted: the group is reactivated and its geo record set republished. After the 7-day window expires the IP returns to the pool for anyone. (IPs released for other reasons are freed immediately.)

Re-activation re-charges the setup fee and does not automatically re-attach the IP to its old endpoints. After a re-upgrade, re-attach the recovered IP (or group) to the endpoints you want it on. See Pricing & the setup fee.
Admin re-attach: a standby IP can only be re-assigned to the account it was reserved for — an administrator approving a new request gets the reserved IP back for that account, and any other account is refused it. This is a backstop on top of the regional pool.
Homepage Docs Dashboard Docs API Docs nvelox Dashboard
Iris