asn.dev

Observed topology

AS32528 ABBOTT-LABS-2

Unclassified ARIN

Upstreams 12 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 0
Upstream graph Who carries AS32528, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS32528 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS32528: 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.

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv4886
AS2914NTT America, Inc.TransitIPv4160
AS174Cogent Communications, LLCTransitIPv4140
AS33491Comcast Cable Communications, LLCUnclassifiedIPv4120
AS3257GTT Communications Inc.TransitIPv4118
AS4812China Telecom (Group)ResidentialIPv4118
AS18747IFX CorporationUnclassifiedIPv4116
AS2516KDDI CORPORATIONMobileIPv476
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv458
AS8220COLT Technology Services Group LimitedHostingIPv434

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32787Akamai Technologies, Inc.HostingIPv4886
AS2914NTT America, Inc.TransitIPv4160
AS174Cogent Communications, LLCTransitIPv4140
AS33491Comcast Cable Communications, LLCUnclassifiedIPv4120
AS3257GTT Communications Inc.TransitIPv4118
AS4812China Telecom (Group)ResidentialIPv4118
AS18747IFX CorporationUnclassifiedIPv4116
AS2516KDDI CORPORATIONMobileIPv476
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv458
AS8220COLT Technology Services Group LimitedHostingIPv434

Provenance

Where this comes from

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