asn.dev

Observed topology

AS23154 SANMINA-SCI - Sanmina-SCI Corporation

Unclassified ARIN

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

Transit

Upstream networks

All 36

Networks observed carrying traffic for AS23154: 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
AS7018AT&T Enterprises, LLCResidentialIPv4461
AS8151UNINETMobileIPv4336
AS45820Tata Teleservices ISP ASResidentialIPv4324
AS701Verizon BusinessResidentialIPv4317
AS2914NTT America, Inc.TransitIPv4234
AS11172Alestra, S. de R.L. de C.V.UnclassifiedIPv4222
AS55836Reliance Jio Infocomm LimitedMobileIPv4212
AS132280Symphony Communication (Thailand) PCL.ResidentialIPv4128
AS9534Binariang BerhadMobileIPv4124
AS1299Arelion Sweden ABTransitIPv4116

All 36 upstreams →

Transit

Downstream networks

inferred

Networks for which AS23154 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 36

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

ASNetworkTypeFamiliesPaths seen
AS7018AT&T Enterprises, LLCResidentialIPv4461
AS8151UNINETMobileIPv4336
AS45820Tata Teleservices ISP ASResidentialIPv4324
AS701Verizon BusinessResidentialIPv4317
AS2914NTT America, Inc.TransitIPv4234
AS11172Alestra, S. de R.L. de C.V.UnclassifiedIPv4222
AS55836Reliance Jio Infocomm LimitedMobileIPv4212
AS132280Symphony Communication (Thailand) PCL.ResidentialIPv4128
AS9534Binariang BerhadMobileIPv4124
AS1299Arelion Sweden ABTransitIPv4116

All 36 adjacent →

Provenance

Where this comes from

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