asn.dev

Observed topology

AS210464 AVSISP ANDREW KRISTULI

Residential RIPE NSP

Upstreams 7 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 15
Adjacent (IPv6) 10
Upstream graph Who carries AS210464, and who carries them, drawn as a map up to the transit-free core. 4 exchanges Where AS210464 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210464: 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
AS6939Hurricane Electric LLCTransitIPv6576
AS213900RS Computers L.L.CUnclassifiedIPv4 IPv6404
AS205941Lungu Stefan GabrielUnclassifiedIPv637
AS401753BIXCE IncUnclassifiedIPv621
AS1103SURF B.V.UnclassifiedIPv618
AS24482SG.GSHostingIPv618
AS25091IP-Max SAUnclassifiedIPv618

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23507AV SERVICES LLCUnclassifiedIPv4 IPv696
AS205563Marc GomezUnclassifiedIPv670
AS218219Ivan Danailov DenevUnclassifiedIPv465
AS212985Mingjie WuUnclassifiedIPv636
AS50833FIBER TELECOM s.r.o.ResidentialIPv41

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6621
AS213900RS Computers L.L.CUnclassifiedIPv4 IPv6575
AS205941Lungu Stefan GabrielUnclassifiedIPv6111
AS23507AV SERVICES LLCUnclassifiedIPv4 IPv696
AS205563Marc GomezUnclassifiedIPv670
AS218219Ivan Danailov DenevUnclassifiedIPv465
AS213753InterEdge B.V.UnclassifiedIPv443
AS212985Mingjie WuUnclassifiedIPv636
AS401753BIXCE IncUnclassifiedIPv4 IPv622
AS1103SURF B.V.UnclassifiedIPv4 IPv619

All 19 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.