as395089 BGP & Peering Info

AS Number(s)




AS Type

Research and Public Benefit

IPv4 Originated Prefix

IPv4 Prefix Count


IPv6 Originated Prefixes

2620:132:3000::/40 le 48

2605:e200:d000::/44 le 48

IPv6 Prefix Count


AS Sets

You may use the following AS set to include our own ASNs and customer ASNs for both IPv4 and IPv6:


Local Preference

We automatically set the following local preference values at our routers, unless overriden by customers with an action community (see BGP communities for further information):

Description Preference
Route learned from transit 100
Route learned from IXP 200
Route learned from customer 300

BGP Communities

Below are listed the BGP communities available with our BGP session. Not all BGP sessions support Hextet Systems Received Communities. Please contact our NOC for more information.

Please note that the Large Communities shown here are planned and not yet available.

Informational Communities

Community Large Community Meaning (Informational)
64579:1 395089:0:1 Originated from Hextet Systems
64579:2 395089:0:2 Peering Routes
64579:3 395089:0:3 Downstream Routes
64579:101 395089:5:1 Accepted from peer because of valid IRR entry
64579:102 395089:5:2 Accepted from peer because of valid ROA
64579:103 395089:5:3 matching valid ROA exists
64579:10 395089:6:10 received from downstream IPv6 BGP Tunnel
64579:11 395089:6:11 received from downstream Thomas King

Action Communities

Community Large Community Meaning / Action
64579:50 395089:1:50 Route of last resort, set LOCAL_PREF to 50
64579:190 395089:1:190 Set LOCAL_PREF to 190 (prefer IXP routing)
64579:290 395089:1:290 Set LOCAL_PREF to 290 (backup connection)
64579:300 395089:1:300 Set LOCAL_PREF to 300 (customer normal)
64579:310 395089:1:310 Set LOCAL_PREF to 310 (higher priority)
- 395089:2:0 Prepend 395089 once to all eBGP peers
- 395089:2:nn Prepend 395089 once to peer AS nnn
- 395089:3:0 Prepend 395089 twice to all eBGP peers
- 395089:3:nn Prepend 395089 twice to peer AS nnn
- 395089:4:0 Do not export to eBGP peers
- 395089:4:nn Do not export to peer AS nnn
65535:666 - BLACKHOLE [RFC 7999]

Our BGP Peering Policy

AS395089 practices an open peering policy which means that we peer with everyone who wants to peer with us. We do not require any kind of written contract, but assume that you can agree to the following rules:

  • Peerings may only send traffic from their own networks and downstreams to us, please do not give others (partial) transit without asking for permission.
  • Peerings must operate a Network Operations Center (NOC) which can be contacted by email.
  • Peerings must be registered at any well known IRR and shall keep all registry data up to date.
  • Peerings shall cooperate in any case of network abuse, e.g. filtering DoS attacks.
  • Peerings shall enforce a strict routing policy by using filters for their downstreams.
  • Peerings shall aggregate their routes as much as possible to avoid inflating the routing tables.

Please also note the following preferences and technical information:

  • Prefixes shorter than a /24 (IPv4) or /48 (IPv6) may be filtered.
  • Prefixes with private or other invalid ASNs in AS_PATH will be filtered.
  • Prefixes with invalid AS_PATHs (leaks) will be filtered.
  • Please use MD5 authentication whenever it is possible for additional security.
  • An individual prefix limit will be set for all peerings. The session will automatically recover one minute after you stopped exceeding your prefix limit.