Observed topology
AS51601 IPTP
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS51601: 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 |
|---|---|---|---|---|
| AS41095 | IPTP LTD | Hosting | IPv4 IPv6 | 72 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 42 |
| AS200612 | Gulf Bridge International Inc. | Unclassified | IPv4 | 25 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 7 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 3 |
| AS25091 | IP-Max SA | Unclassified | IPv6 | 2 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS51601 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42072 | Positive Systems LLC | Unclassified | IPv4 IPv6 | 93 |
| AS17561 | LARUS Limited | Unclassified | IPv4 | 66 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 46 |
| AS50113 | FIRST SERVER LIMITED | Unclassified | IPv4 IPv6 | 39 |
| AS197969 | Federal State Unitary Enterprise "Morsviazsputnik" | Unclassified | IPv4 | 12 |
| AS47243 | ONEXIM Group Ltd. | Unclassified | IPv4 | 11 |
| AS49106 | Opticom Group AO | Unclassified | IPv4 | 11 |
| AS59883 | Global Telecom LLC | Unclassified | IPv4 | 9 |
| AS51408 | OOO Sirius-Project | Unclassified | IPv4 IPv6 | 8 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51601 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41095 | IPTP LTD | Hosting | IPv4 IPv6 | 428 |
| AS50113 | FIRST SERVER LIMITED | Unclassified | IPv4 IPv6 | 160 |
| AS42072 | Positive Systems LLC | Unclassified | IPv4 IPv6 | 93 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 80 |
| AS17561 | LARUS Limited | Unclassified | IPv4 | 66 |
| AS57463 | NetIX Communications JSC | Unclassified | IPv4 | 46 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 32 |
| AS200612 | Gulf Bridge International Inc. | Unclassified | IPv4 | 25 |
| AS51408 | OOO Sirius-Project | Unclassified | IPv4 IPv6 | 22 |
| AS197969 | Federal State Unitary Enterprise "Morsviazsputnik" | Unclassified | IPv4 | 12 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.