Observed topology
AS58067 ASCHITATEH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS58067: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 647 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 163 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 162 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 137 |
| AS13094 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 36 |
| AS24482 | SG.GS | Hosting | IPv6 | 1 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS58067 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50477 | Svyaz-Energo Ltd. | Unclassified | IPv4 IPv6 | 379 |
| AS39178 | Optilink Ltd | Unclassified | IPv4 | 301 |
| AS56702 | JOINT-STOCK COMPANY "MOSCOW ENERGY COMMUNICATION NODE" | Unclassified | IPv4 | 186 |
| AS57371 | Mass-Net LLC | Unclassified | IPv4 | 183 |
| AS58060 | System Solutions Ltd. | Unclassified | IPv4 | 183 |
| AS42451 | Limited Company Sakha Sprint Network | Unclassified | IPv4 | 64 |
| AS200988 | Bridge Telecom LLC | Unclassified | IPv4 | 64 |
| AS204277 | Megalink LLC | Unclassified | IPv4 | 64 |
| AS60579 | AREAL. REGIONAL CENTER LIMITED LIABILITY COMPANY | Unclassified | IPv4 | 62 |
| AS214727 | Falcon LLC | Unclassified | IPv4 | 30 |
Adjacency
Adjacent networks
Every AS seen directly next to AS58067 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 1,572 |
| AS50477 | Svyaz-Energo Ltd. | Unclassified | IPv4 IPv6 | 475 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 471 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 308 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 307 |
| AS39178 | Optilink Ltd | Unclassified | IPv4 | 301 |
| AS56702 | JOINT-STOCK COMPANY "MOSCOW ENERGY COMMUNICATION NODE" | Unclassified | IPv4 | 186 |
| AS57371 | Mass-Net LLC | Unclassified | IPv4 | 183 |
| AS58060 | System Solutions Ltd. | Unclassified | IPv4 | 183 |
| AS13094 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 70 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-15 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.09M 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.