Observed topology
AS15805 SKYNET-CY-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS15805: 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 |
|---|---|---|---|---|
| AS6758 | Monaco Telecom S.A. | Residential | IPv4 IPv6 | 6,525 |
Transit
Downstream networks
Networks for which AS15805 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS199631 | REDMAX TECHNOLOGIES LTD | Unclassified | IPv4 IPv6 | 151 |
| AS50996 | AMDOCS DEVELOPMENT LIMITED | Unclassified | IPv4 | 124 |
| AS209617 | University of Cyprus | Unclassified | IPv4 IPv6 | 122 |
| AS136258 | BrainStorm Network, Inc | Unclassified | IPv4 IPv6 | 93 |
| AS35758 | Rachamim Aviel Twito | Unclassified | IPv4 | 59 |
| AS213793 | Open University of Cyprus | Unclassified | IPv4 | 59 |
| AS208495 | Bolton Technologies LTD | Unclassified | IPv4 | 10 |
Adjacency
Adjacent networks
Every AS seen directly next to AS15805 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6758 | Monaco Telecom S.A. | Residential | IPv4 IPv6 | 7,497 |
| AS199631 | REDMAX TECHNOLOGIES LTD | Unclassified | IPv4 IPv6 | 505 |
| AS50996 | AMDOCS DEVELOPMENT LIMITED | Unclassified | IPv4 | 124 |
| AS209617 | University of Cyprus | Unclassified | IPv4 IPv6 | 122 |
| AS136258 | BrainStorm Network, Inc | Unclassified | IPv4 IPv6 | 93 |
| AS35758 | Rachamim Aviel Twito | Unclassified | IPv4 | 59 |
| AS213793 | Open University of Cyprus | Unclassified | IPv4 | 59 |
| AS208495 | Bolton Technologies LTD | Unclassified | IPv4 | 10 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.