AS394177 (Shift Hosting LLC)

Peering

Requirements

1. You must have an ASN and publicly routable IP space (minimum of /24 IPv4 and/or /48 IPv6).
2. You must maintain an entry at PeeringDB and have a NOC reachable by email or phone.
3. You must maintain an AS-Set containing your ASN and any downstreams.
4. You must only send us traffic for prefixes we advertise. Do not point a static, default, or route of last resort at us.

Additional Info

• If you would like to peer over a PNI or XC, you are responsible for the cost of the interconnect. In certain circumstances and subject to engineering approval, we may share the cost.
• We reserve the right to terminate peering temporarily or indefinitely, at any time, and for any reason, with or without notice.
• We advertise the same routes to routeservers as we do to bilateral peers with direct sessions. This means you should have justification for establishing bilateral sessions if we already exchange routes via RS.
• We filter bogon routes, routes longer than /24 or /48, and RPKI invalid routes.

Communities

We maintain a set of informational and control communities to be used by network operators to influence their routing within our network. Control communities can only be used by customers. They will be filtered out on peering sessions.

Informational

Informational communities are filtered out on all BGP sessions.

Looking glass informational communities

We feed routes to many community-run BGP looking glass services including bgp.tools and lg.ring.nlnog.net. We send these services multiple routes we hold in each location, even though only one is active. The following BGP communities indicate which route is active within our network at a given location.

Control

These communities can be used by customers to influence their routing within our network.

Prepend & No export

You may also use 2, 3, and 4 to specify all direct peers, route servers, and transits respectively. In addition, 0 can be used to specify all peers.
To modify exports to route servers of IXPs, you may use the following ASNs:

Local Preference

You may use BGP communities to change a route's Local Preference within our network.

Blackhole

We allow customers to blackhole any prefix up to a /32 IPv4 and /128 IPv6 on our network using a BGP community. Alongside discarding traffic to the prefix/IP on our routers, applying this community to a route also applies an equivalent community for upstream transit providers that support blackhole by BGP community.

394177:666:0

Backbone control

We operate a backbone of 10G waves or better between all of our locations. We understand that having traffic traverse this backbone may be undesirable for some customers. As such we provide the following communities to control announcements to other locations.

If you do not have transit other than AS394177, 394177:77:0 may break connectivity in unexpected ways

Default Traffic Engineering

By default, we modify our routing using upstream BGP communities to ensure optimal latency. This may be undesirable for some customers.

• By default, routes exported to Cogent (AS174) will be tagged with the community 174:991. This makes the route only be reannounced to Cogent and their direct customers (peering). If you wish to remove this and use Cogent for transit, you may use community394177:505:174.