Observed topology
AS8932 UCOMINT
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS8932: 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 IPv6 | 239 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 158 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 135 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 71 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 15 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 15 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 15 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 15 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 15 |
Transit
Downstream networks
Networks for which AS8932 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44395 | Ucom CJSC | Unclassified | IPv4 IPv6 | 16,982 |
| AS48008 | Harmony Information Technologies and Education Development Fund | Unclassified | IPv4 | 708 |
| AS197834 | Ucom CJSC | Unclassified | IPv4 | 649 |
| AS47623 | Institute for Informatics and Automation Problems | Unclassified | IPv4 | 375 |
| AS205368 | Fnet LLC | Unclassified | IPv4 IPv6 | 358 |
| AS216058 | Proitlab LLC | Unclassified | IPv4 | 343 |
| AS39216 | Pulk Company for General Trading, Communications & Investment, Ltd. | Unclassified | IPv4 IPv6 | 299 |
| AS215421 | LikeNet LLC | Residential | IPv4 | 298 |
| AS43733 | Viva Armenia CJSC | Unclassified | IPv4 IPv6 | 219 |
| AS42991 | BioNet LLC | Unclassified | IPv4 | 214 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8932 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44395 | Ucom CJSC | Unclassified | IPv4 IPv6 | 16,982 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 7,595 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,869 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,979 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,295 |
| AS43733 | Viva Armenia CJSC | Unclassified | IPv4 IPv6 | 1,135 |
| AS48008 | Harmony Information Technologies and Education Development Fund | Unclassified | IPv4 | 708 |
| AS39216 | Pulk Company for General Trading, Communications & Investment, Ltd. | Unclassified | IPv4 IPv6 | 697 |
| AS197834 | Ucom CJSC | Unclassified | IPv4 | 649 |
| AS201986 | Arpinet LLC | Unclassified | IPv4 IPv6 | 585 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.