—————————————————–
Upstreams:
—————————————————–
—————————————————–
Downstreams:
—————————————————–
—————————————————–
Peerings (IPv4 & IPv6) are welcome ;-)
——————————————————–
Community Support Definitions for Customers
——————————————————–
1. Communities controlling AS path prepending for routes on egress:
12732:1000 do not announce at BCIX
12732:1001 prepend once at BCIX
12732:1002 prepend twice at BCIX
12732:2000 do not announce at DECIX
12732:2001 prepend once at DECIX
12732:2002 prepend twice at DECIX
12732:3000 do not announce at ECIX-DUS
12732:3001 prepend once at ECIX-DUS
12732:3002 prepend twice at ECIX-DUS
12732:3050 do not announce at ECIX-BER
12732:3051 prepend once at ECIX-BER
12732:3052 prepend twice at ECIX-BER
12732:3100 do not announce at ECIX-HAM
12732:3101 prepend once at ECIX-HAM
12732:3102 prepend twice at ECIX-HAM
12732:4300 do not announce at AMSIX
12732:4301 prepend once at AMSIX
12732:4302 prepend twice at AMSIX
12732:9000 backup only (below peers, uplink, customer)
12732:9001 to customer only
12732:9001 to customer and peering
12732:9013 do not announce to Cogent
12732:9014 do not announce to KPN
12732:9015 do not announce to Lumen
12732:9016 do not announce to SysEleven
2. Communities tagging the source of routes
12732:100 peer route, learned at BCIX
12732:200 peer route, learned at DECIX
12732:300 peer route, learned at ECIX-DUS
12732:305 peer route, learned at ECIX-BER
12732:310 peer route, learned at ECIX-HAM
12732:430 peer route, learned at AMSIX
12732:21 peer route, learned in D�sseldorf, DE
12732:31 peer route, learned in Amsterdam, NL
12732:30 peer route, learned in Berlin, DE
12732:40 peer route, learned in Hamburg, DE
12732:69 peer route, learned in Frankfurt, DE
——————————————————–
The above information was collected from whois.ripe.net, using
object “AS12732” on November 1, 2026