Observed topology
AS8359 MTS MTS PJSC
Mobile RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS8359: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 13,896 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,820 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 864 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 491 |
| AS42708 | Glesys Sweden AB | Unclassified | IPv4 IPv6 | 491 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 488 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 485 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 483 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 449 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 434 |
Transit
Downstream networks
Networks for which AS8359 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15640 | MTS PJSC | Unclassified | IPv4 IPv6 | 6,644 |
| AS60490 | MTS PJSC | Unclassified | IPv4 IPv6 | 3,911 |
| AS48096 | Enterprise Cloud Ltd. | Unclassified | IPv4 | 3,272 |
| AS25513 | PJSC Moscow city telephone network | Residential | IPv4 IPv6 | 3,203 |
| AS29194 | MTS PJSC | Unclassified | IPv4 | 3,053 |
| AS12695 | LLC Digital Network | Hosting | IPv4 IPv6 | 2,718 |
| AS209024 | MTS PJSC | Unclassified | IPv4 IPv6 | 2,712 |
| AS61400 | Start2 LLC | Unclassified | IPv4 IPv6 | 2,511 |
| AS39001 | MTS PJSC | Unclassified | IPv4 | 2,336 |
| AS29190 | MTS PJSC | Unclassified | IPv4 | 2,030 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8359 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 62,422 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 16,404 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 8,524 |
| AS15640 | MTS PJSC | Unclassified | IPv4 IPv6 | 6,818 |
| AS12695 | LLC Digital Network | Hosting | IPv4 IPv6 | 4,366 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 4,224 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 4,175 |
| AS60490 | MTS PJSC | Unclassified | IPv4 IPv6 | 4,000 |
| AS25513 | PJSC Moscow city telephone network | Residential | IPv4 IPv6 | 3,974 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 3,897 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.