AS394177

Shift Hosting LLC peering and BGP communities.

Dallas Atlanta Chicago

Peering

Requirements

  • Public ASN and routable IP space: /24 IPv4 and/or /48 IPv6 minimum.
  • PeeringDB entry with reachable NOC contact.
  • Valid AS-SET for your ASN and downstreams.
  • No static, default, or route of last resort toward us.

Policy

  • We filter bogons, RPKI invalids, IPv4 longer than /24, and IPv6 longer than /48.
  • PNI/XC costs are customer responsibility unless otherwise approved.
  • We may suspend peering when needed to protect the network.

Customer control communities

Control communities are accepted from customers only. They are filtered on peering sessions.

Export control format

ActionCommunity
Do not export394177:50:TARGET
Prepend 1x394177:51:TARGET
Prepend 2x394177:52:TARGET
Prepend 3x394177:53:TARGET

Common targets

TargetMeans
0All external exports: direct peers, route servers, and transits.
2All direct peers.
3All route servers.
4All transit providers.
ASNOne supported provider, peer, or unique-ASN route server.

Transit targets

TransitASNNo-export example
Cogent174394177:50:174
Arelion1299394177:50:1299
NTT2914394177:50:2914
GTT3257394177:50:3257
Lumen3356394177:50:3356
GSL137409394177:50:137409

Route-server targets

IX route serversASN / targetNo-export example
All route servers3394177:50:3
DE-CIX DallasAS62499394177:50:62499
DE-CIX ChicagoAS62760394177:50:62760
CIX AtlantaAS63221394177:50:63221
Equinix DallasAS24115394177:50:24115

DRIX / DRT route-server controls

DRIX Dallas, DRT IX Atlanta, and DRIX Chicago share the same route-server ASN. Use these city-specific communities when you want to control one of those IXs only.

IX route serversDo not exportPrepend 1xPrepend 2xPrepend 3x
DRIX Dallas394177:54:1394177:55:1394177:56:1394177:57:1
DRT IX Atlanta394177:54:2394177:55:2394177:56:2394177:57:2
DRIX Chicago394177:54:3394177:55:3394177:56:3394177:57:3

Each IX has four communities because there are four actions: block export, prepend once, prepend twice, or prepend three times.

Location export controls

ActionCommunity
Only export externally from Dallas394177:34:1
Only export externally from Atlanta394177:34:2
Only export externally from Chicago394177:34:3

Local preference

Local preferenceCommunity
90 - below transit394177:2:90
100 - transit level394177:2:100
110 - above transit394177:2:110
120 - route-server level394177:2:120
130 - direct-peer level394177:2:130
135 - above peering/transit394177:2:135
140 - customer level394177:2:140
150 - highest customer preference394177:2:150

Blackhole

Blackhole a customer prefix on our network:

394177:666:0

Backbone and location controls

ActionCommunity
Do not export in Dallas394177:32:1
Do not export in Atlanta394177:32:2
Do not export in Chicago394177:32:3
Keep inside the receiving router394177:77:0
Keep inside Dallas metro394177:77:1
Keep inside Atlanta metro394177:77:2
Keep inside Chicago metro394177:77:3

Backbone and location controls can reduce failover. Use them only when that is intended.

Informational communities

Route source

SourceCommunity
Originated by AS394177394177:101:1
Learned from direct peer394177:101:2
Learned from IX route server394177:101:3
Learned from transit394177:101:4
Learned from customer394177:101:5

Location learned

LocationCommunity
Dallas394177:102:1
Atlanta394177:102:2
Chicago394177:102:3

Looking-glass active path

Active pathCommunity
Dallas - DAL1 / 1515 Round Table394177:112:1
Atlanta394177:112:2
Chicago394177:112:3
Dallas - DAL2 / 2323 Bryan394177:112:4
Dallas - DAL3 / 1950 Stemmons394177:112:5

Default traffic engineering

CommunityEffect
394177:505:174Allow routes to be announced more broadly by Cogent where this policy is active.