asn.dev

Observed topology

AS48092 NSB-AS T2 Russia Network

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48092: 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 RostelecomResidentialIPv4583
AS39374T2 Mobile LLCUnclassifiedIPv4344
AS13116Tele2 Sverige ABUnclassifiedIPv455
AS20764CJSC RASCOMUnclassifiedIPv422
AS50673Serverius Holding B.V.UnclassifiedIPv422
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv411
AS24482SG.GSHostingIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS49673Truenetwork LLCUnclassifiedIPv411
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv411

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39374T2 Mobile LLCUnclassifiedIPv468

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4948
AS39374T2 Mobile LLCUnclassifiedIPv4818
AS13116Tele2 Sverige ABUnclassifiedIPv455
AS50673Serverius Holding B.V.UnclassifiedIPv438
AS20764CJSC RASCOMUnclassifiedIPv435
AS6939Hurricane Electric LLCTransitIPv423
AS24482SG.GSHostingIPv420
AS37721Virtual Technologies & SolutionsResidentialIPv420
AS49673Truenetwork LLCUnclassifiedIPv420
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv420

All 17 adjacent →

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.