asn.dev

Observed topology

AS44112 SWEB-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44112: 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 RostelecomResidentialIPv4 IPv61,543
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6264
AS59692IQWeb FZ-LLCUnclassifiedIPv4228
AS24482SG.GSHostingIPv4 IPv627
AS37721Virtual Technologies & SolutionsResidentialIPv426
AS57724DDOS-GUARD LTDUnclassifiedIPv412

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS35295JSC "RU-CENTER"HostingIPv4 IPv6413
AS39494JSC "RU-CENTER"HostingIPv4 IPv6161
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv6152

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv62,096
AS35295JSC "RU-CENTER"HostingIPv4 IPv6413
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6356
AS59692IQWeb FZ-LLCUnclassifiedIPv4228
AS39494JSC "RU-CENTER"HostingIPv4 IPv6161
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv6152
AS48287JSC "RU-CENTER"HostingIPv463
AS24482SG.GSHostingIPv4 IPv638
AS37721Virtual Technologies & SolutionsResidentialIPv433
AS57724DDOS-GUARD LTDUnclassifiedIPv412

Provenance

Where this comes from

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