asn.dev

Observed topology

AS3175 CITYTELECOM-MSK

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3175: 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
AS29076Citytelecom LLCHostingIPv4 IPv62,669
AS1299Arelion Sweden ABTransitIPv65

Transit

Downstream networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS33842Citytelecom LLCUnclassifiedIPv41,299
AS12616Citytelecom LLCHostingIPv4 IPv61,176
AS210079EuroByte LLCUnclassifiedIPv4 IPv6744
AS50516Maxiplace Ltd.UnclassifiedIPv4248
AS50214QWARTA LLCUnclassifiedIPv4 IPv6184
AS43307LLC Basalt Svobodnoe Programnoe ObespechenieUnclassifiedIPv4124
AS60561ITSystem LLCUnclassifiedIPv4100
AS31240Citytelecom LLCHostingIPv462
AS208207LLC The Insurance Company GeliosUnclassifiedIPv462
AS47577Pravilnyy khosting LtdUnclassifiedIPv460

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS29076Citytelecom LLCHostingIPv4 IPv66,748
AS33842Citytelecom LLCUnclassifiedIPv41,299
AS12616Citytelecom LLCHostingIPv4 IPv61,176
AS210079EuroByte LLCUnclassifiedIPv4 IPv6744
AS50516Maxiplace Ltd.UnclassifiedIPv4248
AS50214QWARTA LLCUnclassifiedIPv4 IPv6184
AS43307LLC Basalt Svobodnoe Programnoe ObespechenieUnclassifiedIPv4124
AS60561ITSystem LLCUnclassifiedIPv4100
AS31240Citytelecom LLCHostingIPv462
AS208207LLC The Insurance Company GeliosUnclassifiedIPv462

Provenance

Where this comes from

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