Observed topology

AS19351 TECK-AS-01

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS19351: 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
AS852	TELUS Communications Inc.	Residential	IPv4	182
AS6471	ENTEL CHILE S.A.	Residential	IPv4	134
AS7782	Alaska Communications Systems Group, Inc.	Residential	IPv4	116
AS812	Rogers Communications Canada Inc.	Mobile	IPv4	54
AS6327	Shaw Communications	Residential	IPv4	52
AS7004	TELEFONICA CHILE S.A.	Unclassified	IPv4	40

Transit

Downstream networks

inferred

Networks for which AS19351 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

observed

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

AS	Network	Type	Families	Paths seen
AS852	TELUS Communications Inc.	Residential	IPv4	182
AS6471	ENTEL CHILE S.A.	Residential	IPv4	134
AS7782	Alaska Communications Systems Group, Inc.	Residential	IPv4	116
AS812	Rogers Communications Canada Inc.	Mobile	IPv4	54
AS6327	Shaw Communications	Residential	IPv4	52
AS7004	TELEFONICA CHILE S.A.	Unclassified	IPv4	40

Provenance

Where this comes from

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