Observed topology

AS15024 PACKET-WORKS - Packetworks Inc.

Unclassified ARIN

Upstreams 5 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

Upstream graph Who carries AS15024, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS15024 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15024: 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.

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	300
AS174	Cogent Communications, LLC	Transit	IPv4	72
AS22652	Videotron Ltee	Residential	IPv4	12
AS24482	SG.GS	Hosting	IPv4	6
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	6

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS21813	Trillium Health Partners	Unclassified	IPv4	264

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS6939	Hurricane Electric LLC	Transit	IPv4	515
AS174	Cogent Communications, LLC	Transit	IPv4	346
AS21813	Trillium Health Partners	Unclassified	IPv4	264
AS11670	Toronto Internet Exchange Community	Unclassified	IPv4	225
AS22652	Videotron Ltee	Residential	IPv4	12
AS24482	SG.GS	Hosting	IPv4	6
AS394256	Tech Futures Interactive Inc.	Unclassified	IPv4	6

Provenance

Where this comes from

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