Observed topology
AS8732 COMCOR-AS JSC Comcor
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8732: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 357 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 196 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 158 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 119 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 18 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 IPv6 | 18 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 18 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 18 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 17 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 | 17 |
Transit
Downstream networks
Networks for which AS8732 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15672 | OOO Telecom TZ | Unclassified | IPv4 | 1,596 |
| AS15582 | JSC Comcor | Unclassified | IPv4 IPv6 | 813 |
| AS50126 | OOO "Teleservis" | Unclassified | IPv4 | 468 |
| AS57818 | SKTV Ltd. | Unclassified | IPv4 | 456 |
| AS8901 | "Mosgortelecom" | Unclassified | IPv4 | 434 |
| AS199809 | Maxtel LLC | Unclassified | IPv4 | 367 |
| AS2895 | OOO FREEnet Group | Education | IPv4 IPv6 | 269 |
| AS203498 | JSC Intellin | Unclassified | IPv4 IPv6 | 237 |
| AS44555 | KONEKT Ltd. | Unclassified | IPv4 | 236 |
| AS15850 | Cyberplat OOO | Unclassified | IPv4 | 180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8732 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 4,061 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 2,655 |
| AS15672 | OOO Telecom TZ | Unclassified | IPv4 | 1,633 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 885 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 876 |
| AS15582 | JSC Comcor | Unclassified | IPv4 IPv6 | 813 |
| AS42861 | Foton Telecom CJSC | Unclassified | IPv4 | 711 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 545 |
| AS50126 | OOO "Teleservis" | Unclassified | IPv4 | 468 |
| AS57818 | SKTV Ltd. | Unclassified | IPv4 | 456 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.