IP transit offers

IP transit is access to the whole of the Internet from your own network. You need it as soon as you announce your own IP addresses over BGP: an operator, a hosting provider, a company with its own AS number. If you are simply looking for an Internet connection for your offices or bandwidth for a server, this is not what you need — look at our fibre or hosting offers instead.

Prices and tiers are in the table above. Links are delivered on a 1 or 10 Gbps single-mode fibre port, the 1 Gbps also being available on 25 or 40 Gbps. Pro anti-DDoS protection is available as an option. Beyond the published tiers, we quote.

Our AS212815 backbone totals more than 700 Gbps of port capacity. That is installed capacity, not our traffic: we commonly carry 10 to 20 Gbps. Both figures are given because they do not measure the same thing, and confusing them distorts any comparison between operators.

We buy transit from 4 operators. We do not publish the breakdown of the mix: it moves with our traffic engineering, and a fixed list would be out of date before it was useful — that said, our BGP sessions are visible in public data, we make no secret of them. The table above lists the operators deliverable at our sites, which is a different question. What matters on your side is that losing any one of them does not cut you off from the Internet, and we can deliver a backup link on a router separate from the first.

6 in total: France-IX Paris, GNM-IX, INTERIX and LONAP at 100 Gbps, NL-ix, plus Cogent's Global Peer Exchange at 40 Gbps. In practice, a good part of the traffic towards French and European networks goes through direct peering rather than through a transit provider: fewer intermediaries on the path, and a latency that does not depend on a third party's commercial agreements.

To our Paris sites and to the points of presence where our network is already installed: Telehouse Paris 2, our sites in the Paris region, Marseille, Lille and Grenoble, the Cogent facilities in around fifteen French cities — Bordeaux, Dijon, Grenoble, Lille, Montpellier, Nantes, Nice, Poitiers, Rennes, Rouen, Strasbourg, Toulouse, Tours and Vélizy — as well as Equinix PA2 through PA6. The current list of our interconnections is public on our PeeringDB record. If your datacenter is not on it, ask anyway: depending on the location, an L2 link or a remote IX often gets us there.

Yes. Our border routers validate the origin of received announcements with RPKI: a route whose origin is "Invalid" against the published ROAs is rejected, not merely de-preferred. "Valid" and "NotFound" are accepted normally — refusing "NotFound" would cut off the part of the Internet that has no ROA yet. On your side, if you announce your prefixes through us, publish the matching ROA with your RIR: without it your announcements stay "NotFound" at every operator that validates, and with a badly made ROA — a maxLength that is too wide, a wrong origin AS — they become "Invalid" and disappear. We check this with you at turn-up.

Yes to both. You receive the full BGP table and announce your prefixes normally; our IRR object is AS-DYJIX. The smallest announceable prefix is a /24 in IPv4 and a /48 in IPv6: below that, a prefix is not accepted on the public Internet, whichever operator you use. IPv6 is treated like IPv4, not as a paid option: we announce around 1,500 IPv6 prefixes ourselves against a little under 1,000 in IPv4.

Open, with no contract to sign and no traffic ratio requirement. We are on the route servers of most exchange points where we are present: if we already exchange traffic with you there, a direct session adds nothing, and we will simply ask what it would bring you. In every other case, write to us.