Observed topology
AS52055 NetIX Communications JSC
Unclassified RIPE
Transit
Upstream networks
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
Networks for which AS52055 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24492 | WiCAM Corporation Ltd. | Residential | IPv4 | 93 |
| AS9658 | Eastern Telecoms Phils., Inc. | Unclassified | IPv4 | 37 |
| AS29687 | Geodim Ltd. | Residential | IPv4 | 33 |
| AS208389 | Focus IT Solutions | Unclassified | IPv4 | 4 |
| AS47524 | Turksat Uydu Haberlesme Kablo TV ve Isletme A.S. | Mobile | IPv4 | 3 |
| AS262355 | VSX Networks | Unclassified | IPv4 | 3 |
| AS50869 | IPng Networks GmbH | Unclassified | IPv6 | 2 |
| AS60230 | Neterra Ltd. | Unclassified | IPv4 | 2 |
| AS199996 | AY TI VI NET LTD | Unclassified | IPv4 | 2 |
| AS42 | WoodyNet, Inc. | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS52055 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216285 | MYIP NETWORKS G.P. | Hosting | IPv4 IPv6 | 214 |
| AS24492 | WiCAM Corporation Ltd. | Residential | IPv4 | 93 |
| AS9658 | Eastern Telecoms Phils., Inc. | Unclassified | IPv4 | 37 |
| AS29687 | Geodim Ltd. | Residential | IPv4 | 33 |
| AS13004 | Serbian Open Exchange DOO | Unclassified | IPv4 | 12 |
| AS55818 | MC-IX Matrix Internet Exchange RS-1 | Residential | IPv4 | 12 |
| AS43380 | Digital Telecom IX LLC | Unclassified | IPv4 | 8 |
| AS208389 | Focus IT Solutions | Unclassified | IPv4 | 4 |
| AS47524 | Turksat Uydu Haberlesme Kablo TV ve Isletme A.S. | Mobile | IPv4 | 3 |
| AS50869 | IPng Networks GmbH | Unclassified | IPv6 | 3 |
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.