Observed topology

AS31923 THE-AUTO-CLUB-GROUP-ASN-1 - The Auto Club Group

Unclassified ARIN

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31923: 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	161
AS23005	SWITCH, LTD	Unclassified	IPv4	120
AS12129	123.Net, Inc.	Hosting	IPv4	65
AS33668	Comcast Cable Communications, LLC	Residential	IPv4	12
AS6939	Hurricane Electric LLC	Transit	IPv4	8
AS20205	Amplex Electric, Inc.	Residential	IPv4	3

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS20090	-Reserved AS-	Unclassified	IPv4	61

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3356	Level 3 Parent, LLC	Transit	IPv4	195
AS23005	SWITCH, LTD	Unclassified	IPv4	120
AS12129	123.Net, Inc.	Hosting	IPv4	91
AS20090	-Reserved AS-	Unclassified	IPv4	61
AS33668	Comcast Cable Communications, LLC	Residential	IPv4	12
AS6939	Hurricane Electric LLC	Transit	IPv4	8
AS20205	Amplex Electric, Inc.	Residential	IPv4	4

Provenance

Where this comes from

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