Observed topology

AS397468 THINKON

Unclassified ARIN Enterprise

Upstreams 12 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 12

Adjacent (IPv6) 2

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS397468: 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
AS577	Bell Canada	Mobile	IPv4 IPv6	386
AS3356	Level 3 Parent, LLC	Transit	IPv4	244
AS4764	Aussie Broadband	Residential	IPv4	223
AS812	Rogers Communications Canada Inc.	Mobile	IPv4 IPv6	200
AS7474	SingTel Optus Pty Ltd	Unclassified	IPv4	112
AS49915	Megaport (UK) Limited	Unclassified	IPv4	72
AS6461	Zayo Bandwidth	Transit	IPv4	50
AS7018	AT&T Enterprises, LLC	Residential	IPv4	49
AS21949	Beanfield Technologies Inc.	Unclassified	IPv4	35
AS174	Cogent Communications, LLC	Transit	IPv4	25

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS397468 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 12

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

AS	Network	Type	Families	Paths seen
AS577	Bell Canada	Mobile	IPv4 IPv6	386
AS3356	Level 3 Parent, LLC	Transit	IPv4	244
AS4764	Aussie Broadband	Residential	IPv4	223
AS812	Rogers Communications Canada Inc.	Mobile	IPv4 IPv6	200
AS7474	SingTel Optus Pty Ltd	Unclassified	IPv4	112
AS49915	Megaport (UK) Limited	Unclassified	IPv4	72
AS6461	Zayo Bandwidth	Transit	IPv4	50
AS7018	AT&T Enterprises, LLC	Residential	IPv4	49
AS21949	Beanfield Technologies Inc.	Unclassified	IPv4	35
AS174	Cogent Communications, LLC	Transit	IPv4	25

All 12 adjacent →

Provenance

Where this comes from

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