Observed topology
AS3741 IS
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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 5,365 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 4,874 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,413 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 4,062 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,437 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 956 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 945 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 576 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 492 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 491 |
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 | 41,612 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,884 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 | 3,149 |
| AS31713 | Gateway Communications | Unclassified | IPv4 | 3,010 |
| AS30988 | IS InternetSolutions Limited | Unclassified | IPv4 IPv6 | 2,982 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 | 2,207 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 2,118 |
| AS37457 | Telkom SA Ltd. | Unclassified | IPv4 | 1,650 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 1,648 |
| AS714 | Apple Inc. | Hosting | IPv4 | 1,345 |
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 | 231,675 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 216,961 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 180,246 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 108,988 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 101,213 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 82,428 |
| AS20011 | Dimension Data | Residential | IPv4 IPv6 | 42,756 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 26,780 |
| AS7195 | EDGEUNO S.A.S | Unclassified | IPv4 | 13,122 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 9,338 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.