asn.dev

Observed topology

AS8359 MTS

Mobile RIPE Cable/DSL/ISP

Upstreams 42 carry this network
Downstreams 619 this network carries
Adjacent (IPv4) 685
Adjacent (IPv6) 96
Upstream graph Who carries AS8359, and who carries them, drawn as a map up to the transit-free core. 14 exchanges Where AS8359 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 42

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.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv613,930
AS6939Hurricane Electric LLCTransitIPv4 IPv63,619
AS33891Core-Backbone GmbHHostingIPv4866
AS1836green.ch AGResidentialIPv4 IPv6492
AS42708Glesys ABUnclassifiedIPv4 IPv6492
AS24482SG.GSHostingIPv4 IPv6489
AS50304Blix Solutions ASUnclassifiedIPv4 IPv6485
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv6482
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4450
AS1764Next Layer Telekommunikationsdienstleistungs- und Beratungs GmbHUnclassifiedIPv4 IPv6436

Transit

Downstream networks

All 619

Networks for which AS8359 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS15640MTS PJSCUnclassifiedIPv4 IPv66,653
AS60490MTS PJSCUnclassifiedIPv4 IPv63,929
AS48096Enterprise Cloud Ltd.UnclassifiedIPv43,256
AS25513PJSC Moscow city telephone networkResidentialIPv4 IPv63,244
AS29194MTS PJSCUnclassifiedIPv43,088
AS12695LLC Digital NetworkHostingIPv4 IPv62,860
AS209024MTS PJSCUnclassifiedIPv4 IPv62,734
AS61400Start2 LLCUnclassifiedIPv4 IPv62,601
AS39001MTS PJSCUnclassifiedIPv42,342
AS29190MTS PJSCUnclassifiedIPv42,046

Adjacency

Adjacent networks

All 685

Every AS seen directly next to AS8359 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv662,642
AS6939Hurricane Electric LLCTransitIPv4 IPv615,051
AS55720Gigabit Hosting Sdn BhdHostingIPv48,538
AS15640MTS PJSCUnclassifiedIPv4 IPv66,827
AS12695LLC Digital NetworkHostingIPv4 IPv64,472
AS20764CJSC RASCOMUnclassifiedIPv44,344
AS33891Core-Backbone GmbHHostingIPv44,196
AS4637Telstra GlobalUnclassifiedIPv44,179
AS25513PJSC Moscow city telephone networkResidentialIPv4 IPv64,028
AS60490MTS PJSCUnclassifiedIPv4 IPv64,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.