asn.dev

Observed topology

AS328631 TWC Hosting CC - TWC Hosting CC

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328631: 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
AS37100SEACOM LimitedUnclassifiedIPv4241
AS11845Vox Telecom LtdResidentialIPv4184
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4104
AS3741Dimension DataUnclassifiedIPv439
AS37721Virtual Technologies & SolutionsResidentialIPv438

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328925VENTURE INTERNET HOLDINGSResidentialIPv4187
AS329797ISP COZA (PTY) LTDUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37100SEACOM LimitedUnclassifiedIPv4308
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4234
AS11845Vox Telecom LtdResidentialIPv4222
AS328925VENTURE INTERNET HOLDINGSResidentialIPv4187
AS329797ISP COZA (PTY) LTDUnclassifiedIPv461
AS3741Dimension DataUnclassifiedIPv447
AS37721Virtual Technologies & SolutionsResidentialIPv443

Provenance

Where this comes from

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