IP transit
A dual-stack transit service on our own European backbone, from a single 1G port to 400G, with the routing policy and the engineers behind it in the same building.
We announce your prefixes from AS216265 and carry your traffic across a backbone we run and engineer ourselves. In Europe that usually means fewer autonomous systems between you and the eyeball networks your users sit behind, because we peer directly at 16 exchanges rather than handing traffic to someone else's upstream.
You choose what you receive. Take the full table if you run your own policy, a partial table if you only want our peering and customer routes, or a default route if you want to keep memory and complexity down. All three are available on the same port, and you can change between them without a new order.
Traffic engineering is done with documented BGP communities rather than support tickets. Prepend, restrict or blackhole per region, per exchange or per upstream, and see the result on the next update. The community reference lists every value we accept.
What the service includes
European routing
Direct peering at AMS-IX, DE-CIX Frankfurt, LONAP, ERA-IX, Frys-IX and others, plus private interconnects with the large content networks. European traffic stays in Europe.
Filtering by default
Every session is built with prefix filters generated from IRR data and RPKI origin validation. Invalids are dropped, not de-preferenced. No opt-in, no extra charge.
Traffic engineering
Large communities for prepending, regional restriction and per-peer control, plus customer-triggered RTBH and FlowSpec where the upstream path supports it.
Visibility
Per-port utilisation, 95th percentile and session state in the control panel, with SNMP polling and NetFlow or sFlow export to your own collector on request.
Technical detail
| Interfaces | 1G, 10G, 25G, 40G, 100G and 400G Ethernet |
| Protocol | BGP-4 with multiprotocol extensions, IPv4 and IPv6 dual stack |
| Routing options | Full table, partial table or default route, changeable on request |
| Sessions | Single or multi-session, MD5 authentication, BFD available |
| Address space | Your own PA or PI space, or assignments from ours where you qualify |
| Security | RPKI origin validation, IRR-generated filters, RTBH, optional FlowSpec |
| Traffic engineering | Documented large communities, published in the community reference |
| Monitoring | SNMP v2c and v3, NetFlow v9 and sFlow export, control panel graphs |
| Service targets | 99.99% core availability, NOC response inside 15 minutes |
How it is billed
Common configurations
- 10G port with a 3, 5 or 10 Gbps commit
- 100G port with a 20 to 80 Gbps commit
- Dual 100G ports in separate facilities, one commit across both
- Transit blended with partial transit to lower the average cost per bit
- A trial period on a live port before you sign anything
Who buys it
Access providers and regional ISPs looking for a European upstream that peers where their subscribers are. Content and streaming platforms that need predictable delivery into European eyeball networks. Hosting and cloud providers that want a second upstream with a different peering profile to the incumbent they already buy from. Enterprises running their own AS and public address space.
Related: partial transit · BGP communities · IRR and RPKI policy · network and facilities · LOA templates