Network: IPs, prefixes, BGP and tunnels

/30 through /23 prefixes are available to order directly. For anything larger or a specific architecture - multi-datacenter, Anycast - our network team scopes the request with you.

Yes, and you keep ownership of your block: BYOIP transfers no rights. You need a letter of authorisation (LOA), IRR routing objects and an RPKI/ROA authorisation consistent with the origin chosen after technical review.

An AS number and routable prefixes, or an LOA if you are announcing our blocks. We scope routing policies, BGP communities and security measures together. Turn-up usually takes under 24 business hours once prerequisites are validated.

An IP tunnel carries protected Infrawire addresses to infrastructure of your choice, wherever it is hosted. Most tunnels are live in under 2 hours, with 1 to 64 IPv4 addresses and DDoS protection up to 100 Gbps included.

rDNS is configured from your client area on the relevant plans. For dedicated blocks (/24, /23 and larger), geolocation can be adjusted on request to fit your marketing or compliance constraints.

Yes. IPv6 is available on our VPS, dedicated servers and tunnels. For volume needs or a specific delegation, contact our network team to size the allocation.

The public Looking Glass runs ping, traceroute and BGP queries from our POPs without an account. It is the most reliable way to compare locations before ordering.

Mitigation runs upstream of your machines, on our network, and is included at no extra cost on VPS, dedicated servers and cloud instances. IP tunnels carry that protection up to 100 Gbps to infrastructure hosted anywhere.

Yes. Your additional IPs are announced from our POPs and can be reassigned from one of your services to another - VPS, dedicated server or rack - from your client area or on request, with routing updated immediately.

An LOA is the document in which the holder of a prefix authorises an operator to announce it. You need one to announce your own block from our network (BYOIP), and we issue one to you when you announce our addresses from your own AS.

Run a BGP query from the public Looking Glass: it shows the route as seen from our POPs, the AS path and the communities applied. Also check that your IRR objects and your RPKI/ROA match the origin AS, otherwise part of the internet will filter the announcement.

Single additional addresses are routed immediately. Blocks from /29 to /23 are allocated once the technical justification has been reviewed, usually within one business day; larger blocks, or a specific geolocation, are scoped with the network team.

RPKI is the cryptographic record stating which AS is allowed to announce a prefix. Signing yours is no longer optional in practice: a growing share of the internet drops invalid or unsigned announcements, because a missing ROA looks exactly like a hijack.

They are handled case by case with our network team, since everything depends on your AS, your prefixes and the POPs you want to announce from. Send us the target design and we scope it with you.

It is almost always about what was sent from it: by you, by a compromised service, or by a previous holder. Fix the cause first, then request delisting from the blacklist concerned; support can confirm from our side that the address is clean. If the reputation cannot be recovered, we can swap the address.

Each product page states either an unmetered port or an included volume - there is no third, hidden model. Where a port is unmetered, what matters is sustained saturation rather than peaks, which is what the acceptable use rules describe.

Run the same test from our Looking Glass and from your own machine. If the route is visible from our POPs and the latency there is normal, the problem sits between your users and us rather than inside our network. Attach both outputs to a ticket and support can take it further.