asn.dev

Observed topology

AS48739 IRNET-AS LTD SPUTNIK

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS48739: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4703
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6483
AS20764CJSC RASCOMUnclassifiedIPv4136
AS62255BiMajLink d.o.o.UnclassifiedIPv498
AS31133PJSC MegaFonMobileIPv451
AS25478iHome LLCUnclassifiedIPv422
AS24482SG.GSHostingIPv4 IPv616
AS49673Truenetwork LLCUnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv613
AS50384iHome LLCUnclassifiedIPv47

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57420LLC "Foratelecom"UnclassifiedIPv433

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4703
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv6491
AS20764CJSC RASCOMUnclassifiedIPv4192
AS62255BiMajLink d.o.o.UnclassifiedIPv498
AS57420LLC "Foratelecom"UnclassifiedIPv465
AS31133PJSC MegaFonMobileIPv451
AS25478iHome LLCUnclassifiedIPv422
AS24482SG.GSHostingIPv4 IPv616
AS49673Truenetwork LLCUnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv613

All 13 adjacent →

Provenance

Where this comes from

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