asn.dev

Observed topology

AS57174 SETISERVISY Nets and Services JCS

Unclassified RIPE NSP

Upstreams 7 carry this network
Downstreams 4 this network carries
Adjacent (IPv4) 13
Adjacent (IPv6) 0
Upstream graph Who carries AS57174, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS57174 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS57174: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv456
AS3216PJSC "Vimpelcom"MobileIPv420
AS1299Arelion Sweden ABTransitIPv416
AS20764CJSC RASCOMUnclassifiedIPv416
AS62255BiMajLink d.o.o.UnclassifiedIPv416
AS24482SG.GSHostingIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209759Moy Telecom LLCUnclassifiedIPv4122
AS8241Nets and Services JCSUnclassifiedIPv447
AS47333TELESTORE LtdUnclassifiedIPv438
AS202599United Telecommunications Corporation LTDUnclassifiedIPv430

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4185
AS209759Moy Telecom LLCUnclassifiedIPv4155
AS35598INETCOM CARRIER LLCUnclassifiedIPv4105
AS20764CJSC RASCOMUnclassifiedIPv452
AS8241Nets and Services JCSUnclassifiedIPv448
AS1299Arelion Sweden ABTransitIPv447
AS39156First Telecom LtdUnclassifiedIPv443
AS47333TELESTORE LtdUnclassifiedIPv438
AS202599United Telecommunications Corporation LTDUnclassifiedIPv430
AS62255BiMajLink d.o.o.UnclassifiedIPv419

All 13 adjacent →

Provenance

Where this comes from

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