Observed topology
AS8492 OBIT-AS OBIT Ltd.
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS8492: 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 IPv6 | 3,556 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 1,367 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 1,316 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 725 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 468 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 344 |
| AS210756 | EdgeCenter LLC | Hosting | IPv4 | 186 |
| AS201706 | SERVICEPIPE LLC | Unclassified | IPv4 | 150 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 145 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 140 |
Transit
Downstream networks
Networks for which AS8492 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 | 1,612 |
| AS200483 | "Eneva" Ltd | Unclassified | IPv4 IPv6 | 1,212 |
| AS51478 | "OBIT" Ltd. | Unclassified | IPv4 | 310 |
| AS51376 | AO Mobi.Dengi | Unclassified | IPv4 | 124 |
| AS199072 | "Center of Computor Research" JSC | Unclassified | IPv4 | 118 |
| AS207822 | "NPK Morsvyazavtomatica" LLC | Unclassified | IPv4 IPv6 | 113 |
| AS204891 | LLC Crystal Service Integration | Unclassified | IPv4 | 99 |
| AS200643 | Osinovaya Roshcha JSC | Unclassified | IPv4 IPv6 | 96 |
| AS41512 | "NPO-Design" LLC | Unclassified | IPv4 | 62 |
| AS48986 | DiState Ltd. | Unclassified | IPv4 | 62 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8492 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 5,520 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 1,966 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 1,847 |
| AS197695 | "Domain names registrar REG.RU", Ltd | Hosting | IPv4 | 1,612 |
| AS200483 | "Eneva" Ltd | Unclassified | IPv4 IPv6 | 1,212 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 1,031 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 722 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 529 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 380 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 329 |
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.