asn.dev

Observed topology

AS32798 HIGHLINE-AS

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32798: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,233
AS6939Hurricane Electric LLCTransitIPv4 IPv6628
AS3257GTT Communications Inc.TransitIPv4 IPv6458
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv657
AS293ESnetUnclassifiedIPv456
AS35280F5 Networks SARLHostingIPv432
AS852TELUS Communications Inc.ResidentialIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS22480Beulahland Communications, LLCUnclassifiedIPv4240
AS397770Trinity Link LLCUnclassifiedIPv460
AS16716Lake Livingston Communications Inc.UnclassifiedIPv4 IPv652
AS13465Sam Houston Electric Cooperative, Inc.UnclassifiedIPv41

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv61,428
AS6939Hurricane Electric LLCTransitIPv4 IPv6628
AS3257GTT Communications Inc.TransitIPv4 IPv6616
AS22480Beulahland Communications, LLCUnclassifiedIPv4240
AS397770Trinity Link LLCUnclassifiedIPv460
AS14907Wikimedia Foundation Inc.HostingIPv4 IPv657
AS293ESnetUnclassifiedIPv456
AS16716Lake Livingston Communications Inc.UnclassifiedIPv4 IPv652
AS35280F5 Networks SARLHostingIPv432
AS852TELUS Communications Inc.ResidentialIPv4 IPv615

Provenance

Where this comes from

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