asn.dev

Observed topology

AS39125 RUBIN-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39125: 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
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4228
AS59589LLC KA-2UnclassifiedIPv418

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35713Careerum OUUnclassifiedIPv463
AS49346Internet Service Ltd.UnclassifiedIPv463
AS48969Parus-Telecom Ltd.UnclassifiedIPv441

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4336
AS59589LLC KA-2UnclassifiedIPv477
AS35713Careerum OUUnclassifiedIPv463
AS49346Internet Service Ltd.UnclassifiedIPv463
AS48969Parus-Telecom Ltd.UnclassifiedIPv441

Provenance

Where this comes from

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