Observed topology
AS47377 Orange_Belgium_SA Orange Belgium SA
Mobile RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS47377: 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 | 3,547 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 790 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 523 |
| AS6696 | VERIXI SA | Unclassified | IPv4 | 172 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 89 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 88 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 40 |
| AS29169 | GANDI SAS | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS47377 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12763 | Motor Europe Logistics NV | Unclassified | IPv4 | 174 |
| AS207467 | Orange Belgium SA | Unclassified | IPv4 | 174 |
| AS207232 | CHIREC asbl | Unclassified | IPv4 | 89 |
| AS56369 | Orange Belgium SA | Unclassified | IPv4 | 60 |
| AS34769 | Orange Communications Luxembourg S.A | Unclassified | IPv4 | 59 |
| AS201189 | IRC Engineering NV | Unclassified | IPv4 | 48 |
| AS57933 | IRISnet SCRL | Unclassified | IPv4 IPv6 | 19 |
| AS204182 | Ministeries van de Vlaamse Gemeenschap | Unclassified | IPv4 | 18 |
| AS39855 | Mod Mission Critical LLC | Hosting | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS47377 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,675 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 1,187 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 596 |
| AS6696 | VERIXI SA | Unclassified | IPv4 | 186 |
| AS12763 | Motor Europe Logistics NV | Unclassified | IPv4 | 174 |
| AS207467 | Orange Belgium SA | Unclassified | IPv4 | 174 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 104 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 100 |
| AS207232 | CHIREC asbl | Unclassified | IPv4 | 89 |
| AS56369 | Orange Belgium SA | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.