Observed topology
AS42708 GLESYS glesys.com
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS42708: 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 | 6,012 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,902 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 578 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 388 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 379 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 222 |
| AS57381 | Daniel Husand | Unclassified | IPv4 IPv6 | 216 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 214 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 214 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 213 |
Transit
Downstream networks
Networks for which AS42708 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 5,986 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 4,602 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 IPv6 | 2,472 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 IPv6 | 2,117 |
| AS41745 | Baykov Ilya Sergeevich | Unclassified | IPv4 | 1,710 |
| AS714 | Apple Inc. | Hosting | IPv4 IPv6 | 1,701 |
| AS201216 | Lolo Company AB | Unclassified | IPv4 IPv6 | 1,624 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,315 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 1,276 |
| AS51747 | Internet Vikings International AB | Unclassified | IPv4 | 1,131 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42708 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57381 | Daniel Husand | Unclassified | IPv4 IPv6 | 582,210 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 232,699 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 81,131 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 IPv6 | 48,899 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 27,052 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 IPv6 | 21,058 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 IPv6 | 14,257 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 12,665 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 7,641 |
| AS3786 | LG DACOM Corporation | Unclassified | IPv4 IPv6 | 6,743 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10: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.