IP transit & peeringOpen peering, your own ASN, no ratio test.
1,960 Gbit to the edge across eight regions, on thirteen exchanges, with RPKI origin validation and IRR objects maintained for everything we announce. Bring your prefixes to a $2.79 instance if you want to — the session costs nothing either way.
Peering policy
Open, and short enough to read.
We peer with anyone at any exchange we are both on, without a traffic ratio and without asking what you carry. A ratio test makes paths longer to win a negotiation, and the visitor waiting for a page has no stake in that negotiation.
- Policy
- Open We peer with anyone at any exchange we are both on, without a ratio requirement and without asking what you carry. The point of peering is shorter paths, and a ratio test makes them longer.
- Your own ASN
- Welcome, on any product Bring your ASN and your prefixes to a VPS, a dedicated server, a private cloud or a rack. We set up the session, agree filters and help with the LOA and RPKI if you have not done it before.
- RPKI
- Origin validation on We publish ROAs for our own space and drop RPKI-invalid announcements from peers and customers. A hijack of your prefix through us is meant to be arithmetically difficult rather than merely unlikely.
- IRR
- Objects maintained Route and route6 objects for everything we originate and everything we announce on a customer's behalf, so filter generation elsewhere does not have to take our word for anything.
- Blackholing
- Community-triggered A BGP community you can send us to drop traffic to a single address upstream, for the rare case where that is genuinely what you want.
- What we log
- Flow counters, not content Interface and prefix counters for capacity planning. No netflow retention that could reconstruct who talked to whom, because that is a record we would then be asked for.
Where we are
Every region takes transit from more than one carrier on physically diverse paths, and sits on the local exchange where one exists.
ReykjavíkIceland
BucharestRomania
SofiaBulgaria
ChișinăuMoldova
ZurichSwitzerland
AmsterdamNetherlands
Panama CityPanama
SingaporeSingaporeCarriers are not named here on purpose. A contract ends, a building changes hands, and a carrier list on a marketing page becomes wrong long before anyone remembers to edit it — at which point it is a claim rather than a fact. An engineer will tell you exactly who is in the building you are evaluating, and the looking glass shows you the path.
Bringing your own ASN
On any product, including the cheapest instance. The session, the filters and the help with LOA and RPKI cost nothing.
-
01
Tell us the numbers
Your ASN, the prefixes you want to announce, and whether they are already in an IRR. If any of that is not in place yet, an engineer walks you through the RIR side.
-
02
We agree the filters
Prefix lists built from your IRR objects, max-prefix set with you rather than at you, and ROAs checked so the announcement is RPKI-valid on the way out.
-
03
The session comes up
IPv4 and IPv6, BGP communities documented, and blackhole triggering available for the rare case where dropping traffic upstream is genuinely what you want.
Every region takes transit from more than one carrier, on physically diverse paths into the building.
No single carrier carries a majority of any region's traffic, so one of them having a bad day is a routing event rather than an outage.
Traffic is never billed by the terabyte on any product we sell. The port speed on the price list is the ceiling and the whole of it is yours.
Where an exchange exists in a region, we are on it — peering shortens the path for your visitors and costs them nothing.
For the network engineer.
Will you peer with us?
Yes, at any exchange we are both on, without a ratio requirement and without a minimum traffic level. Write to the address on the contact page with your ASN and PeeringDB record and the session is usually up the same week.
Which carriers do you use?
We do not publish the list, because contracts end and buildings change hands, and a stale carrier list on a marketing page is a claim rather than a fact. An engineer will tell you exactly who is in the building you are evaluating, and the looking glass shows you the path from where you actually are.
Do you validate RPKI?
Origin validation is on: RPKI-invalid announcements from peers and customers are dropped rather than depreferenced, and we publish ROAs for our own space. A hijack of your prefix through this network is meant to be arithmetically difficult rather than merely unlikely.
Can I announce my own space from a VPS?
Yes. There is no product tier at which BGP becomes available — a $2.79 instance can carry a session if that is what you need. What limits it is RIR policy on your side, not a line on our price list.
Is traffic metered anywhere?
Nowhere, on any product. The port speed on the price list is the ceiling and the whole of it is yours. There is no per-terabyte billing, no 95th-percentile line and no commit to negotiate, which also means there is no incentive for us to route your traffic the long way.
What do you log about traffic?
Interface and prefix counters, for capacity planning. We deliberately do not retain netflow detailed enough to reconstruct who talked to whom, because a record like that is one we would then be asked to hand over — and the honest answer to that request is that it was never created.