asn.dev

Observed topology

AS215017 -Reserved AS-

Unclassified RIPE

Upstreams 12 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 12
Upstream graph Who carries AS215017, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS215017 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS215017: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS52025ParadoxNetworks LimitedUnclassifiedIPv6148
AS11967Hop179 OUUnclassifiedIPv4 IPv6141
AS835GoCodeIT IncUnclassifiedIPv676
AS205941Lungu Stefan GabrielUnclassifiedIPv434
AS6939Hurricane Electric LLCTransitIPv630
AS47272HYEHOST LLCHostingIPv65
AS1103SURF B.V.UnclassifiedIPv4 IPv62
AS20473The Constant Company, LLCHostingIPv62
AS24482SG.GSHostingIPv4 IPv62
AS205794JINZE YANGUnclassifiedIPv62

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS215017 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS201300Mirkamal EmiraslanovUnclassifiedIPv633
AS214946EMIRASLAN EMIRASLANOVUnclassifiedIPv62

Adjacency

Adjacent networks

All 14

Every AS seen directly next to AS215017 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS11967Hop179 OUUnclassifiedIPv4 IPv6176
AS52025ParadoxNetworks LimitedUnclassifiedIPv6148
AS835GoCodeIT IncUnclassifiedIPv676
AS205941Lungu Stefan GabrielUnclassifiedIPv434
AS201300Mirkamal EmiraslanovUnclassifiedIPv633
AS6939Hurricane Electric LLCTransitIPv630
AS47272HYEHOST LLCHostingIPv65
AS1103SURF B.V.UnclassifiedIPv4 IPv62
AS20473The Constant Company, LLCHostingIPv62
AS24482SG.GSHostingIPv4 IPv62

All 14 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.