Skip to content

BGP Information

BGP Peering Information

365 Data Centers has an open peering policy, however we do have several basic requirements:

  • Peering partners must maintain a 24×7 Network Operations Center
  • Peering partners must cooperate in the troubleshooting of any peering related issues, denial of service attacks, UCE, hacking or virus penetration
  • Peering partners are prohibited from abusing our peering relationship by pointing default or resetting any next-hop
  • 365 Data Centers does not peer with current IP transit customers
  • Peers must participate at all available peering locations and advertise consistent routes

365 Data Centers operates under the global autonomous system number of 29838
All routes originating from 365 Data Centers will be registered in the IRR under the AS Macro of AS-AMC

We maintain a PeeringDB record located at http://as29838.peeringdb.com

To establish peering, please contact us via email at [email protected]

BGP Communities

365 Data Centers utilizes BGP communities attached to every route to help determine
how the route was learned and to manipulate traffic flows.

For more information please contact us at [email protected]

Routes residing on the 365 Data Centers network will be tagged to indicate their route type, and location where the route was learned. They will be tagged in the following format:

29838:TRSLL

T Route Type
R Region
S Sub-region
LL Location

Route Type
Region
Sub-region
Transit
North America (ARIN)
North East
Public Peer
European (RIPE)
North
Private Peer
Asia (APNIC)
North West
Customer
Central and South America (LACNIC)
East
Internal
Africa (AFRINIC)
Central
West
South East
South
South West

All routes within the 365 Data Centers network carry a local preference as follows

45
Depreferred Transit
50
Standard Transit
55
Preferred Transit
75
Depreferred Peering
80
Standard Peering
85
Preferred Peering
100
Depreferred Customer
120
Standard Customer or 365 Data Centers Originated

Customer BGP Communities

29838:10
Backup Route
365 will re-advertise routes tagged with this community to service provider partners with their respective ‘Backup’ community. 365 will still prefer the route internally with a local-preference of 100
29838:50
Decrease Local Pref
Decrease local-preference within 365s network to 50
29838:100
Decrease Local Pref
Decrease local-preference within 365s network to 100
29838:666
Blackhole Ref
Announce any /32 (IPv4) or /128 (IPv6) to black hole the given IP within 365s network, and with service provider partner networks
Carrier
No-Export
Prepend 1x
Prepend 2x
Prepend 3x
365 Backbone
29838:0000
29838:0001
29838:0002
29838:0003
365 All Egress
29838:5000
29838:5001
29838:5002
29838:5003
All Transit
29838:1000
29838:1001
29838:1002
29838:1003
NTT
1299:1000
1299:1001
1299:1002
1299:1003
Telia
1299:1000
1299:1001
1299:1002
1299:1003
Cogent
174:1000
174:1001
174:1002
174:1003
GTT
3257:1000
3257:1001
3257:1002
3257:1003
All Peering
29838:2000
29838:2001
29838:2002
29838:2003
NYIIX
29838:2100
29838:2101
29838:2102
29838:2103
Equinix NY
29838:2200
29838:2201
29838:2202
29838:2203
Equinix Chicago
29838:2300
29838:2301
29838:2302
29838:2303
Equinix Miami
29838:3000
29838:3001
29838:3002
29838:3003
Any2 LAX
29838:2500
29838:2501
29838:2502
29838:2503
DE-CIX-NY
29838:2600
29838:2601
29838:2602
29838:2603
DE-CIX Frankfurt via LGA12
29838:2700
29838:2701
29838:2702
29838:2703
DE-CIX Frankfurt via FRA1
29838:3100
29838:3101
29838:3102
29838:3103
DE-CIX Dallas
29838:2800
29838:2801
29838:2802
29838:2803
FL-IX
29838:2900
29838:2901
29838:2902
29838:2903
SeattleIX (SIX)
29838:3200
29838:3201
29838:3202
29838:3203
BostonIX
29838:3300
29838:3301
29838:3302
29838:3303
FD-IX
29838:3400
29838:3401
29838:3402
29838:3403
TorIX
29838:3500
29838:3501
29838:3502
29838:3503
LINX
29838:3600
29838:3601
29838:3602
29838:3603