Observed topology
AS58002 SINFORM JSC Svyazinform
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS58002: 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 | 206 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 141 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 38 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 30 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 17 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 8 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 7 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 7 |
Transit
Downstream networks
Networks for which AS58002 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS45055 | Dontechsvyaz LLC | Unclassified | IPv4 | 800 |
| AS57214 | Vidikon-K, CJSC | Unclassified | IPv4 | 600 |
| AS49311 | Regional TeleSystems Ltd. | Unclassified | IPv4 | 280 |
| AS42916 | IT Ltd. | Unclassified | IPv4 | 264 |
| AS51200 | LLC Digital Dialogue-Nets | Unclassified | IPv4 | 220 |
| AS47196 | Garant-Park-Internet LLC | Unclassified | IPv4 | 113 |
| AS43465 | ReInfoCom Ltd. | Unclassified | IPv4 | 104 |
| AS43264 | RTO-DON LLC | Unclassified | IPv4 | 98 |
| AS210240 | New Communication Technologies LLC | Unclassified | IPv4 | 93 |
| AS43521 | Recom LLC | Unclassified | IPv4 | 80 |
Adjacency
Adjacent networks
Every AS seen directly next to AS58002 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 1,543 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,269 |
| AS45055 | Dontechsvyaz LLC | Unclassified | IPv4 | 800 |
| AS57214 | Vidikon-K, CJSC | Unclassified | IPv4 | 626 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 479 |
| AS49311 | Regional TeleSystems Ltd. | Unclassified | IPv4 | 280 |
| AS51200 | LLC Digital Dialogue-Nets | Unclassified | IPv4 | 266 |
| AS42916 | IT Ltd. | Unclassified | IPv4 | 264 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 145 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 137 |
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.