Observed topology
AS8595 WESTCALL-AS OOO WestCall Ltd.
Unclassified DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8595: 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 | 1,513 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 838 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 511 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 233 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 104 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 48 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 46 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 46 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 21 |
Transit
Downstream networks
Networks for which AS8595 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213220 | Delta Ltd | Unclassified | IPv4 | 436 |
| AS51705 | Moskovia Telecom OOO | Unclassified | IPv4 | 320 |
| AS33987 | Netway ltd | Unclassified | IPv4 | 140 |
| AS199502 | OOO WestCall Ltd. | Unclassified | IPv4 | 128 |
| AS49825 | Lantek LLC | Unclassified | IPv4 | 82 |
| AS50283 | Buisiness Kvartal Nov Ltd. | Unclassified | IPv4 | 80 |
| AS200662 | LLC "Beta Voip" | Unclassified | IPv4 | 67 |
| AS47925 | OOO WestCall Ltd. | Unclassified | IPv4 | 65 |
| AS51884 | OOO WestCall Ltd. | Unclassified | IPv4 | 65 |
| AS56477 | OOO WestCall Ltd. | Unclassified | IPv4 | 65 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8595 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 3,057 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 1,333 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 944 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 559 |
| AS213220 | Delta Ltd | Unclassified | IPv4 | 436 |
| AS51705 | Moskovia Telecom OOO | Unclassified | IPv4 | 320 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 223 |
| AS207457 | OOO WestCall Ltd. | Unclassified | IPv4 | 214 |
| AS33987 | Netway ltd | Unclassified | IPv4 | 140 |
| AS199502 | OOO WestCall Ltd. | Unclassified | IPv4 | 128 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.