Observed topology
AS6789 CRELCOM-NET
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS6789: 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 |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,547 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 744 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 592 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 474 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 269 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 267 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 68 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 68 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 68 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 67 |
Transit
Downstream networks
Networks for which AS6789 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48330 | Sinev Maksim Viktorovich | Unclassified | IPv4 | 4,800 |
| AS51522 | ONLINE LLC | Unclassified | IPv4 | 1,020 |
| AS44533 | Davydov Vladimir Dmitrievich | Unclassified | IPv4 | 1,013 |
| AS197175 | Albina Anatoljevna Kolesnik, PE | Unclassified | IPv4 | 826 |
| AS197628 | Sudak-Net LLC | Unclassified | IPv4 | 549 |
| AS204161 | KRYMSVYAZ LTD | Unclassified | IPv4 | 540 |
| AS8654 | Crimeainfocom Ltd | Unclassified | IPv4 | 472 |
| AS203451 | K-telekom LLC | Unclassified | IPv4 | 427 |
| AS57093 | Yalta-TV KOM Ltd. | Unclassified | IPv4 | 339 |
| AS12403 | Telecommunication company FEONET+ LLC | Unclassified | IPv4 | 327 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6789 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 9,042 |
| AS48330 | Sinev Maksim Viktorovich | Unclassified | IPv4 | 4,800 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 3,674 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,953 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 IPv6 | 1,789 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 1,633 |
| AS51522 | ONLINE LLC | Unclassified | IPv4 | 1,020 |
| AS44533 | Davydov Vladimir Dmitrievich | Unclassified | IPv4 | 1,013 |
| AS197175 | Albina Anatoljevna Kolesnik, PE | Unclassified | IPv4 | 826 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 605 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.