asn.dev

Observed topology

AS37457 Telkom SA Ltd. - Telkom SA Ltd.

Unclassified AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37457: 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 LLCTransitIPv4 IPv66,421
AS3741Dimension DataUnclassifiedIPv41,650
AS5713Telkom SA Ltd.UnclassifiedIPv4 IPv6781
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6509
AS37100SEACOM LimitedUnclassifiedIPv4456

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS327839Woolworths(Proprietary) LtdUnclassifiedIPv4460
AS37167Telkom SA Ltd.UnclassifiedIPv434
AS65656AS65656UnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv66,497
AS3741Dimension DataUnclassifiedIPv41,659
AS5713Telkom SA Ltd.UnclassifiedIPv4 IPv61,174
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6518
AS37100SEACOM LimitedUnclassifiedIPv4467
AS327839Woolworths(Proprietary) LtdUnclassifiedIPv4460
AS37167Telkom SA Ltd.UnclassifiedIPv434
AS65656AS65656UnclassifiedIPv44

Provenance

Where this comes from

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