asn.dev

Observed topology

AS31370 MOSLINE-AS

Unclassified RIPE

Upstreams 11 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 14
Adjacent (IPv6) 6
Upstream graph Who carries AS31370, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS31370 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS31370: 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
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6211
AS1299Arelion Sweden ABTransitIPv4 IPv648
AS20764CJSC RASCOMUnclassifiedIPv4 IPv641
AS29076Citytelecom LLCHostingIPv4 IPv636
AS31500Global Network Management IncUnclassifiedIPv4 IPv631
AS24482SG.GSHostingIPv4 IPv67
AS8595OOO WestCall Ltd.UnclassifiedIPv45
AS35598INETCOM CARRIER LLCUnclassifiedIPv45
AS37721Virtual Technologies & SolutionsResidentialIPv45
AS49673Truenetwork LLCUnclassifiedIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198481LLC SistemaUnclassifiedIPv486
AS12841Veltrade LLCUnclassifiedIPv412
AS204357AGR LLCUnclassifiedIPv44

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS50509Transroute Telecom LTDUnclassifiedIPv4 IPv6274
AS198481LLC SistemaUnclassifiedIPv486
AS1299Arelion Sweden ABTransitIPv4 IPv648
AS20764CJSC RASCOMUnclassifiedIPv4 IPv647
AS31500Global Network Management IncUnclassifiedIPv4 IPv646
AS29076Citytelecom LLCHostingIPv4 IPv641
AS12841Veltrade LLCUnclassifiedIPv412
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv49
AS35598INETCOM CARRIER LLCUnclassifiedIPv48
AS8595OOO WestCall Ltd.UnclassifiedIPv47

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.