Observed topology
AS8636 MAXNET Russia
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8636: 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 |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 792 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 401 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 108 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 21 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 21 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 21 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 17 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS8636 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202344 | LLC Basalt Svobodnoe Programnoe Obespechenie | Unclassified | IPv4 IPv6 | 102 |
| AS31344 | Physical and Energy Institute named after A.I. Leipunsky" | Unclassified | IPv4 | 65 |
| AS62264 | World Data Center" | Unclassified | IPv4 | 65 |
| AS210493 | ITS PRO Ltd. | Unclassified | IPv4 | 65 |
| AS58135 | AO Kaluga Astral | Unclassified | IPv4 | 60 |
| AS60818 | Scientific-production Association Telemetry LLC | Unclassified | IPv4 | 60 |
| AS50703 | Federal State Budgetary Institution of Science Federal Research Center "Geophysical Survey of the Russian Academy of Sciences" | Unclassified | IPv4 | 29 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8636 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 949 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 509 |
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 143 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 119 |
| AS202344 | LLC Basalt Svobodnoe Programnoe Obespechenie | Unclassified | IPv4 IPv6 | 102 |
| AS31344 | Physical and Energy Institute named after A.I. Leipunsky" | Unclassified | IPv4 | 65 |
| AS62264 | World Data Center" | Unclassified | IPv4 | 65 |
| AS210493 | ITS PRO Ltd. | Unclassified | IPv4 | 65 |
| AS58135 | AO Kaluga Astral | Unclassified | IPv4 | 60 |
| AS60818 | Scientific-production Association Telemetry LLC | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.