Observed topology

AS13825 TROYCABLE-NET

Residential ARIN Cable/DSL/ISP

Upstreams 1 carry this network

Downstreams 7 this network carries

Adjacent (IPv4) 9

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS13825: 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
AS11272	C Spire Fiber	Unclassified	IPv4	582

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS53460	Mon-Cre Telephone Cooperative, Inc.	Unclassified	IPv4	232
AS14869	Union Springs Telephone Company	Unclassified	IPv4	59
AS397976	Central Access, Inc.	Unclassified	IPv4	54
AS26511	AAA Cooper Transportation, Inc.	Unclassified	IPv4	32
AS55210	Southeast Alabama Medical Center	Unclassified	IPv4	31
AS393479	Army Aviation Center Federal Credit Union	Unclassified	IPv4	21
AS400079	IVS, Inc.	Unclassified	IPv4	21

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS11272	C Spire Fiber	Unclassified	IPv4	1,064
AS53460	Mon-Cre Telephone Cooperative, Inc.	Unclassified	IPv4	232
AS14869	Union Springs Telephone Company	Unclassified	IPv4	59
AS397976	Central Access, Inc.	Unclassified	IPv4	54
AS26029	Sparrow Technology Solutions, LLC	Unclassified	IPv4	32
AS26511	AAA Cooper Transportation, Inc.	Unclassified	IPv4	32
AS55210	Southeast Alabama Medical Center	Unclassified	IPv4	31
AS393479	Army Aviation Center Federal Credit Union	Unclassified	IPv4	21
AS400079	IVS, Inc.	Unclassified	IPv4	21

Provenance

Where this comes from

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