Observed topology

AS32524 GRUPO-SMS - Grupo-SMS USA, LLC

Unclassified ARIN

Upstreams 3 carry this network

Downstreams 4 this network carries

Adjacent (IPv4) 6

Adjacent (IPv6) 6

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32524: 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
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	2,578
AS7018	AT&T Enterprises, LLC	Residential	IPv4 IPv6	731
AS22773	Cox Communications Inc.	Residential	IPv4 IPv6	678

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS16865	Skyline Security	Unclassified	IPv4 IPv6	92
AS36598	Radiant Solution Providers	Unclassified	IPv4 IPv6	91
AS397287	AutoCrib, Inc.	Unclassified	IPv4	59
AS53779	Bomgar Corporation	Unclassified	IPv6	32

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS174	Cogent Communications, LLC	Transit	IPv4 IPv6	2,727
AS7018	AT&T Enterprises, LLC	Residential	IPv4 IPv6	819
AS22773	Cox Communications Inc.	Residential	IPv4 IPv6	715
AS16865	Skyline Security	Unclassified	IPv4 IPv6	92
AS36598	Radiant Solution Providers	Unclassified	IPv4 IPv6	91
AS397287	AutoCrib, Inc.	Unclassified	IPv4	59
AS53779	Bomgar Corporation	Unclassified	IPv6	32

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.