asn.dev

Observed topology

AS5387 NSC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS5387: 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
AS31200Novotelecom LtdUnclassifiedIPv4 IPv61,016
AS15493"Russian company" LLCUnclassifiedIPv463
AS42451Limited Company Sakha Sprint NetworkUnclassifiedIPv462
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv460
AS49673Truenetwork LLCUnclassifiedIPv412
AS25091IP-Max SAUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208903Federal State Budgetary Institution Budker Institute of Nuclear Physics of Siberian Branch Russian Academy of SciencesUnclassifiedIPv425

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS31200Novotelecom LtdUnclassifiedIPv4 IPv61,062
AS15493"Russian company" LLCUnclassifiedIPv463
AS42451Limited Company Sakha Sprint NetworkUnclassifiedIPv462
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv460
AS208903Federal State Budgetary Institution Budker Institute of Nuclear Physics of Siberian Branch Russian Academy of SciencesUnclassifiedIPv425
AS3267SCIENTIFIC RESEARCH INSTITUTE FOR SYSTEM ANALYSIS OF THE NATIONAL RESEARCH CENTRE "KURCHATOV INSTITUTE"EducationIPv421
AS49673Truenetwork LLCUnclassifiedIPv412
AS25091IP-Max SAUnclassifiedIPv41

Provenance

Where this comes from

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