Observed topology
AS37451 CONGO TELECOM - CONGO TELECOM
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS37451: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 1,496 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 316 |
| AS33763 | Paratus Telecommunications Limited | Unclassified | IPv4 | 130 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 71 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 33 |
| AS56584 | InterEdge B.V. | Unclassified | IPv4 | 5 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 | 3 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 | 3 |
| AS25091 | IP-Max SA | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS37451 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS37447 | ORANGE RDC | Unclassified | IPv4 | 202 |
| AS328500 | A.M.C Telecom | Unclassified | IPv4 | 174 |
| AS37414 | Microcom Sprl | Unclassified | IPv4 | 110 |
| AS37677 | Societe Congolaise des Postes et Telecommunications (SCPT) | Unclassified | IPv4 | 103 |
| AS43256 | Global Broadband Solution Inc | Residential | IPv4 | 72 |
| AS37020 | CELTEL DRC | Unclassified | IPv4 | 67 |
| AS37463 | MTN CONGO | Unclassified | IPv4 | 59 |
| AS37548 | ARPCE | Unclassified | IPv4 | 58 |
| AS329632 | TELECOMMUNICATION DU CONGO | Unclassified | IPv4 | 58 |
| AS328329 | ARPCE | Hosting | IPv4 | 57 |
Adjacency
Adjacent networks
Every AS seen directly next to AS37451 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 2,205 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 610 |
| AS37447 | ORANGE RDC | Unclassified | IPv4 | 221 |
| AS33763 | Paratus Telecommunications Limited | Unclassified | IPv4 | 195 |
| AS328500 | A.M.C Telecom | Unclassified | IPv4 | 174 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 119 |
| AS37414 | Microcom Sprl | Unclassified | IPv4 | 110 |
| AS37677 | Societe Congolaise des Postes et Telecommunications (SCPT) | Unclassified | IPv4 | 103 |
| AS43256 | Global Broadband Solution Inc | Residential | IPv4 | 72 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 71 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.