Observed topology
AS201706 AS-SERVICEPIPE
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS201706: 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 | 346 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 227 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 176 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 175 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 158 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 150 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 135 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 33 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 26 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 25 |
Transit
Downstream networks
Networks for which AS201706 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS47723 | SOFTLINE PJSC | Unclassified | IPv4 IPv6 | 2,780 |
| AS199599 | Telecom-Birzha, LLC | Unclassified | IPv4 | 2,400 |
| AS48287 | JSC "RU-CENTER" | Hosting | IPv4 | 1,138 |
| AS43399 | "TBANK" JSC | Unclassified | IPv4 | 944 |
| AS2118 | Reliable Communications s.r.o. | Unclassified | IPv4 | 870 |
| AS39728 | Likhno Dmitriy trading as Luganet | Unclassified | IPv4 | 649 |
| AS39337 | JSC "Corp Soft" | Unclassified | IPv4 | 605 |
| AS212136 | NUBES LLC | Unclassified | IPv4 IPv6 | 565 |
| AS49729 | Open Joint Stock Company Commercial Bank "Modulbank" | Unclassified | IPv4 | 511 |
| AS48197 | UNISTREAM COMMERCIAL BANK (JSC) | Unclassified | IPv4 | 413 |
Adjacency
Adjacent networks
Every AS seen directly next to AS201706 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 5,922 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 5,540 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 3,927 |
| AS199599 | Telecom-Birzha, LLC | Unclassified | IPv4 | 3,925 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 3,816 |
| AS47723 | SOFTLINE PJSC | Unclassified | IPv4 IPv6 | 2,839 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 2,225 |
| AS48287 | JSC "RU-CENTER" | Hosting | IPv4 | 2,128 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 2,089 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,878 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M 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.