asn.dev

Observed topology

AS21487 PJSC Rostelecom. Yakutsk branch

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS21487: 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 RostelecomResidentialIPv4567

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48312PJSC ALROSAUnclassifiedIPv4159
AS61041Federal Budgetary Institution "Administration of the Lensky Basin of Inland Waterways"UnclassifiedIPv463
AS196648North-Eastern Federal University n.a. M.K.Ammosov, State Federal Autonomous Educational Organisation of Higher Professional EducationUnclassifiedIPv449

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4838
AS48312PJSC ALROSAUnclassifiedIPv4159
AS61041Federal Budgetary Institution "Administration of the Lensky Basin of Inland Waterways"UnclassifiedIPv463
AS196648North-Eastern Federal University n.a. M.K.Ammosov, State Federal Autonomous Educational Organisation of Higher Professional EducationUnclassifiedIPv449

Provenance

Where this comes from

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