asn.dev

Observed topology

AS328977 WAVEX

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328977: 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
AS16637MTN SAMobileIPv4 IPv6947
AS37100SEACOM LimitedUnclassifiedIPv4 IPv678

Transit

Downstream networks

All 114

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

ASNetworkTypeFamiliesPaths seen
AS16509Amazon.com, Inc.HostingIPv42,685
AS8075Microsoft CorporationHostingIPv41,209
AS15169Google LLCHostingIPv4953
AS15399Wananchi Group (Kenya) LimitedResidentialIPv4756
AS36914Kenya Education NetworkResidentialIPv4546
AS329659Lineserve LimitedUnclassifiedIPv4 IPv6350
AS3303Swisscom (Schweiz) AGResidentialIPv4176
AS14593Space Exploration Technologies CorporationResidentialIPv4171
AS33771Safaricom LimitedUnclassifiedIPv4103
AS139057Edgenext Legend Dynasty Pte. Ltd.UnclassifiedIPv4 IPv698

Adjacency

Adjacent networks

All 121

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

ASNetworkTypeFamiliesPaths seen
AS15169Google LLCHostingIPv44,750
AS16509Amazon.com, Inc.HostingIPv42,921
AS8075Microsoft CorporationHostingIPv41,325
AS16637MTN SAMobileIPv4 IPv61,172
AS15399Wananchi Group (Kenya) LimitedResidentialIPv4817
AS36914Kenya Education NetworkResidentialIPv4550
AS36926Airtel Networks Kenya LimitedUnclassifiedIPv4486
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6362
AS33771Safaricom LimitedUnclassifiedIPv4358
AS329659Lineserve LimitedUnclassifiedIPv4 IPv6350

Provenance

Where this comes from

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