asn.dev

Observed topology

AS62382 KDV

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS62382: 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
AS12389PJSC RostelecomResidentialIPv4232
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4136
AS9198JSC KazakhtelecomUnclassifiedIPv461
AS12406Business Network LtdHostingIPv449
AS57681PJSC Moscow city telephone networkUnclassifiedIPv442
AS8359MTS PJSCMobileIPv421
AS43727JSC KVANT-TELEKOMResidentialIPv420
AS28849JSC GLOBALONEBELUnclassifiedIPv416
AS57304JSC "RetnNet"UnclassifiedIPv415
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv411

All 13 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4232
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4136
AS9198JSC KazakhtelecomUnclassifiedIPv461
AS12406Business Network LtdHostingIPv449
AS57681PJSC Moscow city telephone networkUnclassifiedIPv442
AS8359MTS PJSCMobileIPv421
AS43727JSC KVANT-TELEKOMResidentialIPv420
AS28849JSC GLOBALONEBELUnclassifiedIPv416
AS57304JSC "RetnNet"UnclassifiedIPv415
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv411

All 13 adjacent →

Provenance

Where this comes from

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