Observed topology
AS328888 ORCA-TECHNOLOGIES-AS
Residential AFRINIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS328888: 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.
Transit
Downstream networks
Networks for which AS328888 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS328719 | Wired Tech Pty Ltd | Unclassified | IPv4 | 418 |
| AS328257 | ASK Internet Technologies CC | Unclassified | IPv4 IPv6 | 169 |
| AS327805 | Bundu NetworX (Pty) Ltd | Residential | IPv4 IPv6 | 168 |
| AS329462 | V Dot Net Pty Ltd | Unclassified | IPv4 IPv6 | 103 |
| AS329608 | NetClick | Unclassified | IPv4 IPv6 | 103 |
| AS37368 | Bluedust Wireless | Residential | IPv4 IPv6 | 102 |
| AS328714 | Lucert Technologies Pty Ltd. | Unclassified | IPv4 IPv6 | 102 |
| AS329046 | CFM WIRELESS (PTY) LTD | Unclassified | IPv4 | 65 |
| AS328538 | OCTOPI SMART SOLUTIONS (PTY) LTD | Residential | IPv4 IPv6 | 45 |
Adjacency
Adjacent networks
Every AS seen directly next to AS328888 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS60171 | AFR-IX TELECOM S.A. | Unclassified | IPv4 IPv6 | 1,200 |
| AS328719 | Wired Tech Pty Ltd | Unclassified | IPv4 | 418 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 347 |
| AS328257 | ASK Internet Technologies CC | Unclassified | IPv4 IPv6 | 169 |
| AS327805 | Bundu NetworX (Pty) Ltd | Residential | IPv4 IPv6 | 168 |
| AS329462 | V Dot Net Pty Ltd | Unclassified | IPv4 IPv6 | 103 |
| AS329608 | NetClick | Unclassified | IPv4 IPv6 | 103 |
| AS37368 | Bluedust Wireless | Residential | IPv4 IPv6 | 102 |
| AS328714 | Lucert Technologies Pty Ltd. | Unclassified | IPv4 IPv6 | 102 |
| AS329046 | CFM WIRELESS (PTY) LTD | Unclassified | IPv4 | 65 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-30 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.49M 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.