Observed topology
AS39735 RU-Permtelecom "Permtelecom" Ltd
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS39735: 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 |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 489 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 411 |
| AS50923 | Metroset Ltd. | Residential | IPv4 | 286 |
| AS203118 | Ezerdi LLC | Hosting | IPv4 | 171 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 121 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 53 |
| AS24482 | SG.GS | Hosting | IPv4 | 22 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 22 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 18 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS39735 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216128 | SoftM LLC | Unclassified | IPv4 | 11 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39735 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 489 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 411 |
| AS50923 | Metroset Ltd. | Residential | IPv4 | 286 |
| AS203118 | Ezerdi LLC | Hosting | IPv4 | 182 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 121 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 53 |
| AS24482 | SG.GS | Hosting | IPv4 | 22 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 22 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 18 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 18 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.49M 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.