asn.dev

Observed topology

AS44034 HI3G

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS44034: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6163
AS1299Arelion Sweden ABTransitIPv4 IPv6147
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS9002RETN LimitedUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv613
AS42708Glesys ABUnclassifiedIPv4 IPv613
AS50304Blix Solutions ASUnclassifiedIPv4 IPv613
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv611
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv611

All 26 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 26

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6163
AS1299Arelion Sweden ABTransitIPv4 IPv6147
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS9002RETN LimitedUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv613
AS42708Glesys ABUnclassifiedIPv4 IPv613
AS50304Blix Solutions ASUnclassifiedIPv4 IPv613
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv611
AS48185team.blue NVUnclassifiedIPv4 IPv611
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv611

All 26 adjacent →

Provenance

Where this comes from

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