Observed topology
AS17660 DRUKNET-AS DrukNet ISP
Unclassified APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS17660: 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 |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 496 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 110 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 85 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 15 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 15 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 14 |
| AS132132 | MyRepublic Ltd. | Residential | IPv4 | 13 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 | 1 |
| AS35280 | F5 Networks SARL | Hosting | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS17660 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS134715 | Government Technology Agency | Unclassified | IPv4 IPv6 | 872 |
| AS152317 | Wangdue Phodrang Dzongkhag Administration | Unclassified | IPv4 IPv6 | 371 |
| AS135666 | Government Data Center (DITT/MoIC) | Unclassified | IPv4 IPv6 | 210 |
| AS18024 | Bhutan Telecom Ltd | Residential | IPv4 IPv6 | 206 |
| AS18025 | Bhutan Telecom Ltd | Unclassified | IPv4 | 118 |
| AS132894 | Sigma Internet Service | Residential | IPv4 IPv6 | 114 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 92 |
| AS152480 | NETVISION INFOCOMM LTD | Unclassified | IPv4 IPv6 | 76 |
| AS138558 | Gelephu Digital Network | Residential | IPv4 IPv6 | 62 |
| AS153779 | Nilo FiberNet | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS17660 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,126 |
| AS134715 | Government Technology Agency | Unclassified | IPv4 IPv6 | 872 |
| AS18024 | Bhutan Telecom Ltd | Residential | IPv4 IPv6 | 526 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 510 |
| AS152317 | Wangdue Phodrang Dzongkhag Administration | Unclassified | IPv4 IPv6 | 371 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 335 |
| AS135666 | Government Data Center (DITT/MoIC) | Unclassified | IPv4 IPv6 | 210 |
| AS18025 | Bhutan Telecom Ltd | Unclassified | IPv4 | 118 |
| AS132894 | Sigma Internet Service | Residential | IPv4 IPv6 | 114 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 92 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.