Observed topology
AS2611 BELNET
Education RIPE Educational/Research
Transit
Upstream networks
Networks observed carrying traffic for AS2611: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 474 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 318 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 314 |
| AS21320 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 218 |
| AS20965 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 177 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 171 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 145 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 44 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 44 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 43 |
Transit
Downstream networks
Networks for which AS2611 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16326 | SmalS vzw | Unclassified | IPv4 IPv6 | 194 |
| AS213331 | Belgian Ministry of Defence | Unclassified | IPv4 | 124 |
| AS210227 | Jessa Ziekenhuis vzw | Unclassified | IPv4 | 118 |
| AS62058 | ETSPUBLI RADIO-TELEVISION BELGE DE LA COMMUNAUTE FRANCAISE | Unclassified | IPv4 | 115 |
| AS210358 | IMEC (Interuniversitair Micro-Electronica Centrum) VZW | Unclassified | IPv4 | 108 |
| AS15383 | Avenue des Arts - Kunstlaan 21 | Unclassified | IPv4 IPv6 | 102 |
| AS209226 | Institut medical des Mutualites socialistes | Unclassified | IPv4 | 100 |
| AS211602 | Ziekenhuis aan de Stroom vzw | Unclassified | IPv4 IPv6 | 93 |
| AS198559 | BELNET | Unclassified | IPv4 IPv6 | 69 |
| AS25344 | Technofutur TIC ASBL | Unclassified | IPv4 | 62 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2611 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 753 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 478 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 468 |
| AS21320 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 407 |
| AS20965 | GEANT Vereniging | Unclassified | IPv4 IPv6 | 290 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 258 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 218 |
| AS16326 | SmalS vzw | Unclassified | IPv4 IPv6 | 194 |
| AS213331 | Belgian Ministry of Defence | Unclassified | IPv4 | 124 |
| AS210227 | Jessa Ziekenhuis vzw | Unclassified | IPv4 | 118 |
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.