Network services & IP transit

A transit session is a BGP peering with our routers. You announce your prefixes to us; we announce a full routing table — or a single default route, if you would rather keep your edge simple — to you. From that moment your address space is reachable everywhere our network reaches, and the global internet is reachable through us.

Sessions are dual-stack (IPv4 and IPv6 over the same peering) and support the traffic engineering you would expect: BGP communities and MED to steer traffic, and prefix filtering built from your IRR objects and validated against RPKI, so a mis-origination on either side is dropped rather than propagated.

Ports and commit levels are matched to your traffic profile — from a modest commit on a shared port up to dedicated high-capacity ports for volume customers. Tell us your expected volume and target markets and we will put together options.

• Full table or default route, your choice — dual-stack IPv4 and IPv6
• BGP communities and MED for traffic engineering
• IRR- and RPKI-based prefix filtering on every session
• Announce your own IP space, or use ours

DDoS protection here is not a separate product you route to when something goes wrong. It runs inline and always on, at the same network edge that carries your transit. Traffic is inspected and filtered before it reaches you, so an attack is absorbed in the backbone rather than at your doorstep.

Mitigation profiles are tuned for the traffic our customers actually run — common web and application patterns, and specific game-server titles — and you keep self-service control over the filtering rules for your own prefixes.

• Always-on and inline — no redirect, no “time to mitigation” delay
• Filtering at the network edge, ahead of your host
• Profiles tuned for application and game-server traffic
• Self-service filtering rules for your own address space

Need addresses? Lease IPv4 and IPv6 from our pools, sized to your deployment. Already hold your own space? Bring it: we will announce your prefixes from AS55285 once we have a valid Letter of Authorisation and your IRR and RPKI (ROA) records line up.

Everything is dual-stack by default. IPv6 is native on our network, not bolted on, so you can build IPv6-first and treat IPv4 as the compatibility layer it is becoming.

• IPv4 leasing from our pools, sized to your deployment
• IPv6 allocations, native and dual-stack
• BYOIP: we announce your prefixes with a valid Letter of Authorisation
• IRR and RPKI (ROA) guidance so your routes validate cleanly

Our routers sit in carrier-neutral facilities operated by the likes of Netrality, DataBank and Digital Realty. If you are in one of the same buildings — or can reach them — a cross-connect puts your equipment directly onto our fabric, with no middle-mile in between.

We peer settlement-free at the internet exchanges we sit on, with an open policy registered on PeeringDB, and offer remote hands for the times you cannot be on site. See the full live footprint on our network page, and facility addresses and compliance on our datacenters page.

• Private cross-connects in our carrier-neutral facilities
• Open, settlement-free peering at the exchanges we sit on
• Remote hands when you cannot be on site
• Compliance-audited buildings (SOC 2, ISO 27001, PCI DSS and more)