Observed topology
AS32437 edgeconnect-legacy
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS32437: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 231 |
| AS37468 | Angola Cables | Unclassified | IPv4 IPv6 | 83 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 75 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 50 |
| AS37271 | Workonline Communications(Pty) Ltd | Unclassified | IPv4 IPv6 | 47 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 41 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 25 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 25 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 25 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 25 |
Transit
Downstream networks
Networks for which AS32437 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS21739 | MAJUBA TECHNOLOGIES(PTY) Limited t/a T-SOL | Unclassified | IPv4 | 196 |
| AS329541 | zing fibre (pty) Ltd | Residential | IPv4 IPv6 | 185 |
| AS329039 | LINK CONNECT SERVICES (PTY) LTD | Unclassified | IPv4 | 124 |
| AS328365 | Edge connect (pty) Ltd | Unclassified | IPv4 | 49 |
| AS328391 | Rocking Connect PTY (LTD) | Unclassified | IPv4 | 31 |
| AS37017 | Edge connect (pty) Ltd | Unclassified | IPv4 | 22 |
| AS328948 | NETELLIGENT CONSULTING cc | Unclassified | IPv4 | 20 |
Adjacency
Adjacent networks
Every AS seen directly next to AS32437 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 260 |
| AS37468 | Angola Cables | Unclassified | IPv4 IPv6 | 232 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 222 |
| AS21739 | MAJUBA TECHNOLOGIES(PTY) Limited t/a T-SOL | Unclassified | IPv4 | 196 |
| AS329541 | zing fibre (pty) Ltd | Residential | IPv4 IPv6 | 185 |
| AS37271 | Workonline Communications(Pty) Ltd | Unclassified | IPv4 IPv6 | 150 |
| AS329039 | LINK CONNECT SERVICES (PTY) LTD | Unclassified | IPv4 | 124 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 102 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 73 |
| AS328365 | Edge connect (pty) Ltd | Unclassified | IPv4 | 49 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.