Observed topology
AS6856 IC-VORONEZH-AS Informsvyaz - Chernozemye
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS6856: 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 IPv6 | 304 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 100 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 69 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 8 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 8 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS6856 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43521 | Recom LLC | Unclassified | IPv4 | 180 |
| AS200235 | Kniazev Ilia Igorevich | Unclassified | IPv4 IPv6 | 75 |
| AS204991 | AVS-electro LLC | Unclassified | IPv4 | 30 |
| AS61265 | Limited Liability Company "Consist software Voronezh" | Unclassified | IPv4 | 29 |
| AS212288 | AGROECO-YUG LLC | Unclassified | IPv4 | 24 |
| AS51419 | Internet Business Technologies Ltd. | Unclassified | IPv4 | 20 |
| AS57609 | Lubyatovo LLC | Unclassified | IPv4 | 16 |
| AS198076 | Lite Group Ltd. | Unclassified | IPv4 | 8 |
| AS203371 | "Trans inform" LLC | Unclassified | IPv4 | 6 |
| AS57749 | EUROMEDIA LLC | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS6856 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 492 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 213 |
| AS43521 | Recom LLC | Unclassified | IPv4 | 180 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 111 |
| AS200235 | Kniazev Ilia Igorevich | Unclassified | IPv4 IPv6 | 75 |
| AS204991 | AVS-electro LLC | Unclassified | IPv4 | 30 |
| AS61265 | Limited Liability Company "Consist software Voronezh" | Unclassified | IPv4 | 29 |
| AS212288 | AGROECO-YUG LLC | Unclassified | IPv4 | 24 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 23 |
| AS51419 | Internet Business Technologies Ltd. | Unclassified | IPv4 | 20 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.