Observed topology

AS53985 DODGE-AND-COX-FUNDS - DODGE & COX

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS53985: 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
AS3356	Level 3 Parent, LLC	Transit	IPv4	224
AS33651	Comcast Cable Communications, LLC	Unclassified	IPv4	64
AS6461	Zayo Bandwidth	Transit	IPv4	53
AS60793	TELEFONICA TECH NORTHERN IRELAND LIMITED	Residential	IPv4	36
AS174	Cogent Communications, LLC	Transit	IPv4	23
AS701	Verizon Business	Residential	IPv4	20

Transit

Downstream networks

inferred

Networks for which AS53985 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 AS53985 in a routing path, in either direction.

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	224
AS33651	Comcast Cable Communications, LLC	Unclassified	IPv4	64
AS6461	Zayo Bandwidth	Transit	IPv4	53
AS60793	TELEFONICA TECH NORTHERN IRELAND LIMITED	Residential	IPv4	36
AS174	Cogent Communications, LLC	Transit	IPv4	23
AS701	Verizon Business	Residential	IPv4	20

Provenance

Where this comes from

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