asn.dev

Observed topology

AS327943 Mezobyte (Pty) LTD - Mezobyte (Pty) LTD

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS327943: 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
AS37468Angola CablesUnclassifiedIPv4284
AS174Cogent Communications, LLCTransitIPv4231
AS37100SEACOM LimitedUnclassifiedIPv4114
AS3741Dimension DataUnclassifiedIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329355Glidepath Group of Companies (Pty) LtdUnclassifiedIPv4177
AS329368CALNET FIBRE (PTY) LTDUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4395
AS37468Angola CablesUnclassifiedIPv4284
AS37100SEACOM LimitedUnclassifiedIPv4178
AS329355Glidepath Group of Companies (Pty) LtdUnclassifiedIPv4177
AS329368CALNET FIBRE (PTY) LTDUnclassifiedIPv459
AS3741Dimension DataUnclassifiedIPv415
AS37721Virtual Technologies & SolutionsResidentialIPv49

Provenance

Where this comes from

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