Observed topology
AS28968 EUT-AS JSC "Evrasia Telecom Ru"
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS28968: 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 |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 497 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 176 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 98 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 65 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 51 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 47 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 25 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 15 |
Transit
Downstream networks
Networks for which AS28968 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56476 | City-Line Ltd. | Unclassified | IPv4 | 954 |
| AS8242 | Digital Solutions LLC | Unclassified | IPv4 | 501 |
| AS61121 | Gruppa Kompani GEOTEL AO | Residential | IPv4 | 284 |
| AS58048 | Bezheckaya Internet Company ltd. | Unclassified | IPv4 | 213 |
| AS60852 | Computer Service LLC | Unclassified | IPv4 | 210 |
| AS47193 | LAN-Optic, Ltd | Unclassified | IPv4 IPv6 | 176 |
| AS204276 | Eutelsat Networks LLC | Unclassified | IPv4 | 138 |
| AS205569 | REGIONSVYAZ OOO | Residential | IPv4 | 112 |
| AS204337 | OOO UK ROSNANO | Unclassified | IPv4 | 65 |
| AS206585 | Mosenergo PJSC | Unclassified | IPv4 | 65 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28968 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 2,262 |
| AS56476 | City-Line Ltd. | Unclassified | IPv4 | 954 |
| AS8242 | Digital Solutions LLC | Unclassified | IPv4 | 550 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 376 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 332 |
| AS61121 | Gruppa Kompani GEOTEL AO | Residential | IPv4 | 289 |
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 236 |
| AS47193 | LAN-Optic, Ltd | Unclassified | IPv4 IPv6 | 235 |
| AS58048 | Bezheckaya Internet Company ltd. | Unclassified | IPv4 | 213 |
| AS60852 | Computer Service LLC | Unclassified | IPv4 | 210 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.