Observed topology
AS138322 AWCC-AS-AP - Afghan Wireless Communication Company
Mobile APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS138322: 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 |
|---|---|---|---|---|
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 IPv6 | 1,035 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 710 |
| AS38193 | Transworld Associates (Pvt.) Ltd. | Unclassified | IPv4 IPv6 | 262 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 83 |
| AS55330 | AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK | Unclassified | IPv4 IPv6 | 51 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 49 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 8 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 6 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 6 |
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS138322 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS38742 | Afghan Wireless Communication Company | Mobile | IPv4 IPv6 | 4,964 |
| AS133066 | Ariana Network Services Co | Unclassified | IPv4 | 675 |
| AS133076 | Unique Atlantic Telecommunication | Unclassified | IPv4 | 493 |
| AS132222 | Sanzar F Kakar T/A Afghanistan Holding Group | Unclassified | IPv4 | 175 |
| AS135298 | Ankabut Internet Service Provider | Residential | IPv4 | 129 |
| AS133533 | TRISTAR ISP | Unclassified | IPv4 | 121 |
| AS58469 | Ministry of Communication & IT | Unclassified | IPv4 | 63 |
Adjacency
Adjacent networks
Every AS seen directly next to AS138322 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS38742 | Afghan Wireless Communication Company | Mobile | IPv4 IPv6 | 4,964 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 3,769 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 IPv6 | 3,167 |
| AS38193 | Transworld Associates (Pvt.) Ltd. | Unclassified | IPv4 IPv6 | 885 |
| AS133066 | Ariana Network Services Co | Unclassified | IPv4 | 675 |
| AS133076 | Unique Atlantic Telecommunication | Unclassified | IPv4 | 493 |
| AS55330 | AFGHANTELECOM GOVERNMENT COMMUNICATION NETWORK | Unclassified | IPv4 IPv6 | 425 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 296 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 190 |
| AS132222 | Sanzar F Kakar T/A Afghanistan Holding Group | Unclassified | IPv4 | 175 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.