asn.dev

Observed topology

AS44112 SWEB-AS SpaceWeb Ltd

Unclassified RIPE

Upstreams 9 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 13
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,479
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6355
AS59692IQWeb FZ-LLCUnclassifiedIPv4223
AS24482SG.GSHostingIPv4 IPv629
AS37721Virtual Technologies & SolutionsResidentialIPv428
AS6939Hurricane Electric LLCTransitIPv412
AS57724DDOS-GUARD LTDUnclassifiedIPv49
AS8732JSC ComcorUnclassifiedIPv42
AS34927iFog GmbHHostingIPv42

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 IPv6394
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv6161
AS39494JSC "RU-CENTER"HostingIPv4 IPv6155

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv62,004
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6461
AS35295JSC "RU-CENTER"HostingIPv4 IPv6394
AS59692IQWeb FZ-LLCUnclassifiedIPv4223
AS43489JSC "RU-CENTER"UnclassifiedIPv4 IPv6161
AS39494JSC "RU-CENTER"HostingIPv4 IPv6155
AS48287JSC "RU-CENTER"HostingIPv461
AS24482SG.GSHostingIPv4 IPv640
AS37721Virtual Technologies & SolutionsResidentialIPv435
AS6939Hurricane Electric LLCTransitIPv412

All 13 adjacent →

Provenance

Where this comes from

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