asn.dev

Observed topology

AS63066 7HOOPNETWORK - 7Hoop Network Telecom, LLC

Residential ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS63066: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6236
AS1299Arelion Sweden ABTransitIPv4 IPv6126
AS3257GTT Communications Inc.TransitIPv4 IPv642
AS9002RETN LimitedUnclassifiedIPv49
AS24482SG.GSHostingIPv4 IPv68
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS293ESnetUnclassifiedIPv43
AS3130RGnet OUUnclassifiedIPv43
AS7575Australian Academic and Research Network (AARNet)EducationIPv43
AS34927iFog GmbHHostingIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS216435Plim Mobile Telecom LLCUnclassifiedIPv4 IPv61,669
AS1979627HOOP MOB TELECOM LLCUnclassifiedIPv6842

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv62,311
AS216435Plim Mobile Telecom LLCUnclassifiedIPv4 IPv61,669
AS1979627HOOP MOB TELECOM LLCUnclassifiedIPv6842
AS1299Arelion Sweden ABTransitIPv4 IPv6442
AS3257GTT Communications Inc.TransitIPv4 IPv6121
AS34927iFog GmbHHostingIPv4 IPv640
AS24482SG.GSHostingIPv4 IPv612
AS9002RETN LimitedUnclassifiedIPv49
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv65
AS293ESnetUnclassifiedIPv43

All 12 adjacent →

Provenance

Where this comes from

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