Observed topology
AS39927 ELIGHT-AS
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS39927: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 365 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 318 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 178 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 140 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 72 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 34 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 9 |
| AS50384 | iHome LLC | Unclassified | IPv4 | 5 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 2 |
| AS13094 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS39927 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS203493 | Egor Timoshenko | Hosting | IPv4 | 64 |
| AS200697 | T.F.Gorbachev Kuzbass State Technical University | Unclassified | IPv4 | 54 |
| AS35835 | Public Budget-Funded Health Care Institution "Kemerovo Regional Health Care Research and Information Center" | Unclassified | IPv4 | 22 |
| AS56390 | Kuzbassa | Unclassified | IPv4 | 13 |
| AS205682 | INVESTREGIONPROM LLC | Unclassified | IPv4 | 9 |
Adjacency
Adjacent networks
Every AS seen directly next to AS39927 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 483 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 318 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 212 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 140 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 78 |
| AS203493 | Egor Timoshenko | Hosting | IPv4 | 64 |
| AS200697 | T.F.Gorbachev Kuzbass State Technical University | Unclassified | IPv4 | 54 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 34 |
| AS35835 | Public Budget-Funded Health Care Institution "Kemerovo Regional Health Care Research and Information Center" | Unclassified | IPv4 | 22 |
| AS56390 | Kuzbassa | Unclassified | IPv4 | 13 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.