We peer openly.
We support both public and private peering.
We do not require a minimum amount of traffic to peer.
We do not consider traffic ratios to peer.
While not mandatory, we encourage peering in multiple, mutual locations.
We do not require a contract to peer.
We do not support contracts for public peering.
We can support contracts for private peering if required by our peering partner.
We do not peer with our IP Transit or Internet Access customers.
We may not peer with networks that are customers of our customers.
We announce only AllWorldIT routes and AllWorldIT customer routes.
We announce routes consistently across all peering sessions, barring any customer-induced traffic engineering implementations across our network.
We do not provide any kind of global IP Transit or Internet Access across peering sessions.
We do not provide access to AllWorldIT on-net services or CDNs across peering sessions.
We, generally, do peer with route servers.
We, generally, do peer with route collectors.
We exchange both IPv4 and IPv6 routes.
We do prefix-based filtering based on IRR records but not AS_PATH-based filtering for peer routes. We set “max-prefix” values for route control based on the peers PeeringDB entry. We do not accept (or announce) private or reserved IP address space, we do not accept (or announce) private AS numbers, and we do not accept (or announce) IPv4 routes smaller than a /24 or IPv6 routes smaller than a /64.
We encourage our peers to set “max-prefix” values for route control in order to reduce administrative overhead and speed up improvement in routing quality enabled by peering. However, we understand each network employs its own policy in this regard, and we shall respect it.
We perform a strict and extensive combination of prefix, AS_PATH, and “max-prefix” based filtering on all BGP sessions with our downstream customers. As such, our peers are guaranteed of good, clean routing when they peer with AllWorldIT.
We filter (and drop) traffic sourced from or destined to any private or reserved IP address space, in either direction of the peering session.
We do not accept any routes from route collectors.
We request our peers not to point static routes toward our routers (including default route), even though doing so will not provide any benefit to the offending peer.
We do not accept customer routes from peers.
We do not perform uRPF on our peering routers, as these routers do not hold a full BGP table.