asn.dev

Observed topology

AS52055 NetIX Communications JSC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS52055: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS24492WiCAM Corporation Ltd.ResidentialIPv493
AS9658Eastern Telecoms Phils., Inc.UnclassifiedIPv437
AS29687Geodim Ltd.ResidentialIPv433
AS208389Focus IT SolutionsUnclassifiedIPv44
AS47524Turksat Uydu Haberlesme Kablo TV ve Isletme A.S.MobileIPv43
AS262355VSX NetworksUnclassifiedIPv43
AS50869IPng Networks GmbHUnclassifiedIPv62
AS60230Neterra Ltd.UnclassifiedIPv42
AS199996AY TI VI NET LTDUnclassifiedIPv42
AS42WoodyNet, Inc.UnclassifiedIPv41

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS216285MYIP NETWORKS G.P.HostingIPv4 IPv6214
AS24492WiCAM Corporation Ltd.ResidentialIPv493
AS9658Eastern Telecoms Phils., Inc.UnclassifiedIPv437
AS29687Geodim Ltd.ResidentialIPv433
AS13004Serbian Open Exchange DOOUnclassifiedIPv412
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv412
AS43380Digital Telecom IX LLCUnclassifiedIPv48
AS208389Focus IT SolutionsUnclassifiedIPv44
AS47524Turksat Uydu Haberlesme Kablo TV ve Isletme A.S.MobileIPv43
AS50869IPng Networks GmbHUnclassifiedIPv63

Provenance

Where this comes from

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