Observed topology
AS199599 CIREX
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS199599: 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 |
|---|---|---|---|---|
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 2,381 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 28 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 28 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 27 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 10 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv6 | 2 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 1 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 1 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS199599 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197695 | "Domain names registrar REG.RU", Ltd | Hosting | IPv4 | 5,896 |
| AS51219 | K2 Integration JSC | Unclassified | IPv4 IPv6 | 693 |
| AS216246 | Aeza Group LLC | Unclassified | IPv4 IPv6 | 402 |
| AS60216 | Foundation for Assistance for Internet Technologies and Infrastructure Development | Unclassified | IPv4 IPv6 | 359 |
| AS34802 | Commercial Bank "Renaissance Credit" LLC | Unclassified | IPv4 | 285 |
| AS200107 | Kaspersky Lab Switzerland GmbH | Unclassified | IPv4 IPv6 | 260 |
| AS39337 | JSC "Corp Soft" | Unclassified | IPv4 | 242 |
| AS209930 | DataSpace Partners LLC | Unclassified | IPv4 | 224 |
| AS201144 | Infosecurity Ltd | Unclassified | IPv4 IPv6 | 192 |
| AS56351 | Forais LLC | Unclassified | IPv4 | 189 |
Adjacency
Adjacent networks
Every AS seen directly next to AS199599 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 6,377 |
| AS197695 | "Domain names registrar REG.RU", Ltd | Hosting | IPv4 | 5,952 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 4,076 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 3,585 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 1,391 |
| AS51219 | K2 Integration JSC | Unclassified | IPv4 IPv6 | 889 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 821 |
| AS48757 | TrustInfo LLC | Unclassified | IPv4 | 499 |
| AS216246 | Aeza Group LLC | Unclassified | IPv4 IPv6 | 402 |
| AS48287 | JSC "RU-CENTER" | Hosting | IPv4 IPv6 | 362 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.