Observed topology
AS29075 IELO IELO-LIAZO SERVICES SAS
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS29075: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 306 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 238 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 150 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 109 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 74 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 46 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 28 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 28 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 28 |
| AS42708 | Glesys AB | Unclassified | IPv4 IPv6 | 28 |
Transit
Downstream networks
Networks for which AS29075 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48072 | Alsatis SAS | Residential | IPv4 IPv6 | 1,910 |
| AS51083 | Association Grenode | Unclassified | IPv4 IPv6 | 1,209 |
| AS203596 | CELYA SAS | Residential | IPv4 IPv6 | 819 |
| AS198507 | IELO-LIAZO SERVICES SAS | Residential | IPv4 IPv6 | 639 |
| AS31898 | Oracle Corporation | Hosting | IPv4 IPv6 | 563 |
| AS197922 | Techcrea Solutions SAS | Unclassified | IPv4 | 432 |
| AS197696 | Evolix SARL | Unclassified | IPv4 IPv6 | 424 |
| AS202089 | Unimedia Services SAS | Unclassified | IPv4 IPv6 | 409 |
| AS57119 | NAITWAYS SAS | Unclassified | IPv4 IPv6 | 384 |
| AS42689 | Glide Student & Residential Limited | Residential | IPv4 IPv6 | 368 |
Adjacency
Adjacent networks
Every AS seen directly next to AS29075 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20766 | Association "Gitoyen" | Unclassified | IPv4 IPv6 | 19,661 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 11,071 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,183 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 3,019 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,303 |
| AS48072 | Alsatis SAS | Residential | IPv4 IPv6 | 1,910 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,326 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,315 |
| AS51083 | Association Grenode | Unclassified | IPv4 IPv6 | 1,209 |
| AS198507 | IELO-LIAZO SERVICES SAS | Residential | IPv4 IPv6 | 958 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.