asn.dev

Observed topology

AS49320 INN361-AS LLC Nauka Svyaz

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49320: 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"UnclassifiedIPv4331
AS50509Transroute Telecom LTDUnclassifiedIPv4292
AS35598INETCOM CARRIER LLCUnclassifiedIPv461
AS48166FORTEX CJSCUnclassifiedIPv448
AS62255BiMajLink d.o.o.UnclassifiedIPv414
AS24482SG.GSHostingIPv413
AS37721Virtual Technologies & SolutionsResidentialIPv413
AS6939Hurricane Electric LLCTransitIPv412
AS25091IP-Max SAUnclassifiedIPv41
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS199021Greenline Ltd.UnclassifiedIPv4130
AS50760Mozhaisk Computer Networks Ltd.UnclassifiedIPv4128
AS205657Golitsyno Telecom LtdUnclassifiedIPv465

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4489
AS8641LLC "Nauka-Svyaz"UnclassifiedIPv4402
AS199021Greenline Ltd.UnclassifiedIPv4130
AS50760Mozhaisk Computer Networks Ltd.UnclassifiedIPv4128
AS35598INETCOM CARRIER LLCUnclassifiedIPv4119
AS48166FORTEX CJSCUnclassifiedIPv4103
AS205657Golitsyno Telecom LtdUnclassifiedIPv465
AS62255BiMajLink d.o.o.UnclassifiedIPv433
AS37721Virtual Technologies & SolutionsResidentialIPv422
AS24482SG.GSHostingIPv421

All 13 adjacent →

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.