asn.dev

Observed topology

AS42437 T2-ROSTOV-AS T2 Russia Network

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42437: 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 RostelecomResidentialIPv41,170
AS31133PJSC MegaFonMobileIPv4286
AS50673Serverius Holding B.V.UnclassifiedIPv452
AS24482SG.GSHostingIPv426
AS37721Virtual Technologies & SolutionsResidentialIPv426
AS49673Truenetwork LLCUnclassifiedIPv426
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv426

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39374T2 Mobile LLCUnclassifiedIPv4248

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv41,350
AS31133PJSC MegaFonMobileIPv4330
AS39374T2 Mobile LLCUnclassifiedIPv4254
AS50673Serverius Holding B.V.UnclassifiedIPv462
AS37721Virtual Technologies & SolutionsResidentialIPv432
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv432
AS24482SG.GSHostingIPv430
AS49673Truenetwork LLCUnclassifiedIPv430

Provenance

Where this comes from

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