Observed topology
AS28761 CrimeaCom-LLC CrimeaCom South LLC
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS28761: 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 |
|---|---|---|---|---|
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 1,467 |
| AS31133 | PJSC MegaFon | Mobile | IPv6 | 62 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 52 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 26 |
| AS24482 | SG.GS | Hosting | IPv4 | 25 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 25 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 25 |
| AS50629 | LWLcom GmbH | Unclassified | IPv4 | 25 |
| AS12389 | PJSC Rostelecom | Residential | IPv6 | 10 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS28761 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS196705 | Ardinvest LTD | Unclassified | IPv4 IPv6 | 773 |
| AS205515 | Telecommunication Systems LLC | Unclassified | IPv4 | 655 |
| AS47939 | TDV "Teleradio company "Yalta" LLC | Unclassified | IPv4 | 486 |
| AS50949 | Agronet LLC | Unclassified | IPv4 | 437 |
| AS57093 | Yalta-TV KOM Ltd. | Unclassified | IPv4 | 426 |
| AS44341 | Nikita Sergienko | Unclassified | IPv4 | 315 |
| AS200420 | "MEGA-NET" LLC | Unclassified | IPv4 | 315 |
| AS208397 | INFOSTROY LLC | Unclassified | IPv4 | 253 |
| AS43822 | HOMEOPTIC LLC | Unclassified | IPv4 | 252 |
| AS204144 | Comfort XXI Century Ltd. | Unclassified | IPv4 | 236 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28761 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 4,807 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,179 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,086 |
| AS196705 | Ardinvest LTD | Unclassified | IPv4 IPv6 | 801 |
| AS205515 | Telecommunication Systems LLC | Unclassified | IPv4 | 655 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 575 |
| AS50949 | Agronet LLC | Unclassified | IPv4 | 500 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 493 |
| AS47939 | TDV "Teleradio company "Yalta" LLC | Unclassified | IPv4 | 486 |
| AS57093 | Yalta-TV KOM Ltd. | Unclassified | IPv4 | 426 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.