Observed topology
AS8359 MTS
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,930 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,619 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 866 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 492 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 492 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 489 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 485 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 482 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 450 |
| AS1764 | Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbH | Unclassified | IPv4 IPv6 | 436 |
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,653 |
| AS60490 | MTS PJSC | Unclassified | IPv4 IPv6 | 3,929 |
| AS48096 | Enterprise Cloud Ltd. | Unclassified | IPv4 | 3,256 |
| AS25513 | PJSC Moscow city telephone network | Residential | IPv4 IPv6 | 3,244 |
| AS29194 | MTS PJSC | Unclassified | IPv4 | 3,088 |
| AS12695 | LLC Digital Network | Hosting | IPv4 IPv6 | 2,860 |
| AS209024 | MTS PJSC | Unclassified | IPv4 IPv6 | 2,734 |
| AS61400 | Start2 LLC | Unclassified | IPv4 IPv6 | 2,601 |
| AS39001 | MTS PJSC | Unclassified | IPv4 | 2,342 |
| AS29190 | MTS PJSC | Unclassified | IPv4 | 2,046 |
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,642 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 15,051 |
| AS55720 | Gigabit Hosting Sdn Bhd | Hosting | IPv4 | 8,538 |
| AS15640 | MTS PJSC | Unclassified | IPv4 IPv6 | 6,827 |
| AS12695 | LLC Digital Network | Hosting | IPv4 IPv6 | 4,472 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 4,344 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 4,196 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 4,179 |
| AS25513 | PJSC Moscow city telephone network | Residential | IPv4 IPv6 | 4,028 |
| AS60490 | MTS PJSC | Unclassified | IPv4 IPv6 | 4,019 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.