AS395394 Peering Info

BGP peering information & policies for AS395394

Communities

Accepted / Sent Community Value Purpose More Information
Accepted 65001:1075 Set LOCAL_PREF to 75 LOCAL_PREF=75 would make this a backup route
Accepted 65001:1085 Set LOCAL_PREF to 85 LOCAL_PREF=85 would make this a preferred route
Accepted65001:911BlackholeAccepted as a /32, will blackhole a host.
Sent65001:10Transit Route
Sent65001:20Peering Route
Sent65001:30Customer Route

Local Preference Defaults

Source Value
Transit 90
Peers 95
Customers 100

Policies

  • We will not peer with anyone who is a xyTel transit customer
  • We are a fully IPv6-enabled network and prefer to establish v4/v6 peerings
  • Peers are encouraged to have accessible NOCs with email addresses and phone numbers
  • Peers must agree to actively cooperate re: security violations, denial of service attacks, route leaks, and similar incidents
  • Peers must not abuse the peering relationship by doing any of the following:
    • Sending a default route
    • Resetting next hop
    • Sending prefixes longer than /24 or /48
    • Sending private ASNs in the AS_PATH
    • Excessive AS padding (100+)
  • We reserve the right to temporarily suspend peering if it causes harm to the xyTel network
  • All peering arrangements will be filtered; any change requests to the filter list will be answered and implemented promptly with a valid, signed LoA