asn.dev

Observed topology

AS12737 RIGHTSIDE16

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12737: 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 RostelecomResidentialIPv4763
AS31133PJSC MegaFonMobileIPv4458
AS3216PJSC "Vimpelcom"MobileIPv4345
AS8359MTS PJSCMobileIPv479

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS50439City Telephone Network Ltd.UnclassifiedIPv488
AS208912KrasPromStroy, LLCUnclassifiedIPv461
AS50918PJSC RossetiUnclassifiedIPv418
AS205720LLC MaltatUnclassifiedIPv41

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv41,127
AS31133PJSC MegaFonMobileIPv4528
AS3216PJSC "Vimpelcom"MobileIPv4416
AS210267Maxima, LLCUnclassifiedIPv4352
AS8359MTS PJSCMobileIPv494
AS50439City Telephone Network Ltd.UnclassifiedIPv488
AS208912KrasPromStroy, LLCUnclassifiedIPv461
AS50918PJSC RossetiUnclassifiedIPv418
AS205720LLC MaltatUnclassifiedIPv41

Provenance

Where this comes from

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