Observed topology
AS3741 Dimension Data - Dimension Data
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS3741: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 5,941 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,991 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,419 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 4,046 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,440 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 984 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 958 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 582 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 494 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 493 |
Transit
Downstream networks
Networks for which AS3741 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20011 | Dimension Data | Residential | IPv4 IPv6 | 43,798 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,906 |
| AS7552 | Viettel Group | Mobile | IPv4 | 3,933 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 | 3,152 |
| AS30988 | IS InternetSolutions Limited | Unclassified | IPv4 IPv6 | 3,040 |
| AS31713 | Gateway Communications | Unclassified | IPv4 | 3,010 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 2,211 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 1,910 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 1,675 |
| AS37457 | Telkom SA Ltd. | Unclassified | IPv4 | 1,650 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3741 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 227,649 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 217,062 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 189,936 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 102,884 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 101,991 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 84,126 |
| AS20011 | Dimension Data | Residential | IPv4 IPv6 | 44,952 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 26,883 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 13,080 |
| AS64049 | Reliance Jio Infocomm Pte Ltd Singapore | Unclassified | IPv4 | 8,759 |
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.