asn.dev

Observed topology

AS37673 Telemasters - Telemasters

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37673: 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
AS22355Frogfoot NetworksResidentialIPv4348
AS3741Dimension DataUnclassifiedIPv48
AS37721Virtual Technologies & SolutionsResidentialIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328872Sonke Telecommunications (Pty) LtdUnclassifiedIPv462
AS328371PerfectWorx Consulting (Pty) LtdUnclassifiedIPv460
AS328912Mpu Communications (Pty) LtdUnclassifiedIPv459
AS329266Intdev Internet Technologies (Pty) LtdResidentialIPv43

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS22355Frogfoot NetworksResidentialIPv4526
AS328872Sonke Telecommunications (Pty) LtdUnclassifiedIPv462
AS328371PerfectWorx Consulting (Pty) LtdUnclassifiedIPv460
AS328912Mpu Communications (Pty) LtdUnclassifiedIPv459
AS3741Dimension DataUnclassifiedIPv411
AS37721Virtual Technologies & SolutionsResidentialIPv411
AS329266Intdev Internet Technologies (Pty) LtdResidentialIPv43

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.