Observed topology
AS2602 RESTENA Reseau Teleinformatique de lEducation Nationale
Education RIPE Educational/Research
Transit
Upstream networks
Networks observed carrying traffic for AS2602: 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 |
|---|---|---|---|---|
| AS56665 | Proximus Luxembourg S.A. | Residential | IPv4 IPv6 | 157 |
| AS6661 | POST Luxembourg | Residential | IPv4 IPv6 | 145 |
| AS21320 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 113 |
| AS20965 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 41 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS45049 | Mohamed El Bouddunti | Residential | IPv4 IPv6 | 8 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 8 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 8 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 7 |
Transit
Downstream networks
Networks for which AS2602 was observed as the last hop before the origin, meaning it appears to provide them transit.
Adjacency
Adjacent networks
Every AS seen directly next to AS2602 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS56665 | Proximus Luxembourg S.A. | Residential | IPv4 IPv6 | 165 |
| AS6661 | POST Luxembourg | Residential | IPv4 IPv6 | 145 |
| AS21320 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 115 |
| AS20965 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 66 |
| AS42909 | Community DNS Limited | Hosting | IPv4 | 37 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 24 |
| AS45049 | Mohamed El Bouddunti | Residential | IPv4 IPv6 | 14 |
| AS50628 | Leonix Telecom SAS | Unclassified | IPv4 IPv6 | 14 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 12 |
| AS211018 | Administration Communale Luxemberg | Unclassified | IPv4 IPv6 | 10 |
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.