AS394177 (Shift Hosting LLC)

Peering

Requirements

You must have an ASN and publicly routable IP space (minimum of /24 IPv4 and/or /48 IPv6).
You must maintain an entry at PeeringDB and have a NOC reachable by email or phone.
You must maintain an AS-Set containing your ASN and any downstreams.
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.

Route source	Default Localpref	Community
Originated by AS394177	N/A	`394177:101:1`
Learned from Direct Peer	130	`394177:101:2`
Learned from IX Routeserver	120	`394177:101:3`
Learned from Transit	100	`394177:101:4`
Learned from Customer	140	`394177:101:5`

Location learned	Community
Learned in Dallas	`394177:102:1`
Learned in Atlanta	`394177:102:2`
Learned in Chicago	`394177:102:3`

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.

Location	Community
Active path in Dallas (DAL1, 1515 Round Table)	`394177:112:1`
Active path in Atlanta	`394177:112:2`
Active path in Chicago	`394177:112:3`
Active path in Dallas (DAL2, 2323 Bryan)	`394177:112:4`
Active path in Dallas (DAL3, 1950 Stemmons)	`394177:112:5`

Control

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

Prepend & No export

Action	Community
Prepend 394177 1x to ASXXXXX	`394177:51:XXXXX`
Prepend 394177 2x to ASXXXXX	`394177:52:XXXXX`
Prepend 394177 3x to ASXXXXX	`394177:53:XXXXX`
Do not export to ASXXXXX	`394177:50:XXXXX`

For XXXXX, use a specific supported ASN or one of the class targets below:

0 - everyone outside our network: direct peers, route servers, and transit providers
2 - all direct peers
3 - all route servers
4 - all transit providers

Examples: 394177:50:2914 means do not export to NTT AS2914; 394177:53:2914 means prepend three times to NTT AS2914; 394177:50:4 means do not export to transit providers. Use 394177:50:0 when you want us to keep the route from being announced to peers, route servers, or transits.

Common supported transit ASN targets include:

Transit provider	ASN	Example no-export community
Cogent	174	`394177:50:174`
Arelion	1299	`394177:50:1299`
NTT	2914	`394177:50:2914`
GTT	3257	`394177:50:3257`
Lumen	3356	`394177:50:3356`

To modify exports to all route servers, use target 3. For named IX route-server sets, use the IX-specific communities below. These avoid ambiguity where the same route-server ASN is used in multiple metros.

Action	Community pattern
Do not export to IX route-server set ID	`394177:54:ID`
Prepend 394177 1x to IX route-server set ID	`394177:55:ID`
Prepend 394177 2x to IX route-server set ID	`394177:56:ID`
Prepend 394177 3x to IX route-server set ID	`394177:57:ID`

IX route-server set	ID	Example no-export community
DRIX Dallas route servers at DAL2 / 2323 Bryan	1	`394177:54:1`
Digital Realty / DRT IX Atlanta route servers	2	`394177:54:2`
DRIX Chicago route servers	3	`394177:54:3`
DE-CIX Dallas route servers	4	`394177:54:4`
DE-CIX Chicago route servers	5	`394177:54:5`
CIX Atlanta route servers	6	`394177:54:6`
Equinix Dallas / DAL3 route servers	7	`394177:54:7`

Currently validated IX-specific route-server controls:

DRIX Dallas: 394177:54:1, 394177:55:1, 394177:56:1, 394177:57:1
DRT IX Atlanta: 394177:54:2, 394177:55:2, 394177:56:2, 394177:57:2
DRIX Chicago: 394177:54:3, 394177:55:3, 394177:56:3, 394177:57:3

Local Preference

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

Local Preference	Community
`90` (Below transit)	`394177:2:90`
`100` (Same as transit)	`394177:2:100`
`110` (Above transit, below peering)	`394177:2:110`
`120` (Same as RS Peers)	`394177:2:120`
`130` (Same as Direct Peers)	`394177:2:130`
`135` (Above all peering/transit, below customers)	`394177:2:135`
`140` (Same as customers)	`394177:2:140`
`150` (Above customers)	`394177:2:150`

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.

Action	Community
Do not export in Dallas	`394177:32:1`
Do not export in Atlanta	`394177:32:2`
Do not export in Chicago	`394177:32:3`
Confine to the receiving router / do not redistribute across the AS394177 core	`394177:77:0`
Confine to Dallas metro only: DAL1 1515 Round Table, DAL2 2323 Bryan, and DAL3 1950 Stemmons	`394177:77:1`
Only export externally from Dallas	`394177:34:1`
Only export externally from Atlanta	`394177:34:2`
Only export externally from Chicago	`394177:34:3`

⚠️ Backbone and location-control communities may reduce or remove geographic failover. 394177:77:1 is enforced on Dallas metro routers; outside Dallas, it has no special default behavior. 394177:34:1, 394177:34:2, and 394177:34:3 control external export by location. The location-export controls are being standardized across the fleet; contact NOC before relying on them for production traffic during rollout.

Default Traffic Engineering

We modify our routing using BGP communities and other fields to ensure optimal latency. This may be undesirable for some customers. Permanent traffic engineering actions that can be changed by customers are listed below.

Default action	Community	New action
Tag routes announced to Cogent AS174 with community `174:991` (only announce to internal + customers)	`394177:505:174`	Remove this community, allowing the route to be announced to all peers and the greater internet by Cogent where this policy is active.