asn.dev

Observed topology

AS328114 Comsol Networks (PTY) Ltd - Comsol Networks (PTY) Ltd

Unclassified AFRINIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328114: 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
AS6939Hurricane Electric LLCTransitIPv4870
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6454
AS37721Virtual Technologies & SolutionsResidentialIPv466
AS3741Dimension DataUnclassifiedIPv4 IPv635
AS22355Frogfoot NetworksResidentialIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328346AirtelecomResidentialIPv4112

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4930
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6503
AS328346AirtelecomResidentialIPv4112
AS37721Virtual Technologies & SolutionsResidentialIPv466
AS3741Dimension DataUnclassifiedIPv4 IPv635
AS22355Frogfoot NetworksResidentialIPv410

Provenance

Where this comes from

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