Observed topology
AS5631 LUMINET
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS5631: 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 | 495 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 467 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 288 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 98 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 60 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 60 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 34 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 34 |
| AS29075 | IELO-LIAZO SERVICES SAS | Unclassified | IPv4 IPv6 | 34 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 34 |
Transit
Downstream networks
Networks for which AS5631 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS30938 | ahbr company limited | Unclassified | IPv4 | 296 |
| AS201536 | SANDYX SYSTEMS LIMITED | Unclassified | IPv4 IPv6 | 202 |
| AS51707 | Medway Towns Council | Unclassified | IPv4 | 177 |
| AS205080 | Societe Internationale de Telecommunications Aeronautiques | Unclassified | IPv4 IPv6 | 92 |
| AS215497 | Tivarri Limited | Unclassified | IPv4 | 59 |
| AS41099 | Global Reach Networks Limited | Unclassified | IPv4 | 32 |
| AS51553 | Telecom Plus PLC | Unclassified | IPv4 | 24 |
| AS50108 | Electronic Arts Limited | Unclassified | IPv4 | 9 |
| AS203159 | Aramco Overseas Company BV | Unclassified | IPv4 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5631 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 697 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 693 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 397 |
| AS30938 | ahbr company limited | Unclassified | IPv4 | 296 |
| AS201536 | SANDYX SYSTEMS LIMITED | Unclassified | IPv4 IPv6 | 202 |
| AS51707 | Medway Towns Council | Unclassified | IPv4 | 177 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 175 |
| AS205080 | Societe Internationale de Telecommunications Aeronautiques | Unclassified | IPv4 IPv6 | 92 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 87 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 86 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.