asn.dev

Observed topology

AS202246 VALOO

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS202246: 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 LLCTransitIPv4 IPv6376
AS12552GlobalConnect ABUnclassifiedIPv4 IPv6218
AS1299Arelion Sweden ABTransitIPv4 IPv6184
AS6667Elisa OyjResidentialIPv4 IPv638
AS24482SG.GSHostingIPv4 IPv618
AS50304Blix Solutions ASUnclassifiedIPv418
AS20473The Constant Company, LLCHostingIPv69
AS20764CJSC RASCOMUnclassifiedIPv49
AS5405Inter.link GmbHUnclassifiedIPv4 IPv68
AS33891Core-Backbone GmbHHostingIPv48

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20798EPTE OyUnclassifiedIPv439
AS51319KajoNet OyUnclassifiedIPv4 IPv624

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6390
AS12552GlobalConnect ABUnclassifiedIPv4 IPv6259
AS1299Arelion Sweden ABTransitIPv4 IPv6204
AS51319KajoNet OyUnclassifiedIPv4 IPv642
AS20798EPTE OyUnclassifiedIPv439
AS6667Elisa OyjResidentialIPv4 IPv638
AS50304Blix Solutions ASUnclassifiedIPv420
AS24482SG.GSHostingIPv4 IPv619
AS20473The Constant Company, LLCHostingIPv611
AS20764CJSC RASCOMUnclassifiedIPv410

All 13 adjacent →

Provenance

Where this comes from

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