asn.dev

Observed topology

AS15805 SKYNET-CY-AS

Unclassified RIPE

Upstreams 1 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 4
Upstream graph Who carries AS15805, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS15805 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS6758Monaco Telecom S.A.ResidentialIPv4 IPv66,525

Transit

Downstream networks

inferred

Networks for which AS15805 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS199631REDMAX TECHNOLOGIES LTDUnclassifiedIPv4 IPv6151
AS50996AMDOCS DEVELOPMENT LIMITEDUnclassifiedIPv4124
AS209617University of CyprusUnclassifiedIPv4 IPv6122
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv693
AS35758Rachamim Aviel TwitoUnclassifiedIPv459
AS213793Open University of CyprusUnclassifiedIPv459
AS208495Bolton Technologies LTDUnclassifiedIPv410

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS15805 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6758Monaco Telecom S.A.ResidentialIPv4 IPv67,497
AS199631REDMAX TECHNOLOGIES LTDUnclassifiedIPv4 IPv6505
AS50996AMDOCS DEVELOPMENT LIMITEDUnclassifiedIPv4124
AS209617University of CyprusUnclassifiedIPv4 IPv6122
AS136258BrainStorm Network, IncUnclassifiedIPv4 IPv693
AS35758Rachamim Aviel TwitoUnclassifiedIPv459
AS213793Open University of CyprusUnclassifiedIPv459
AS208495Bolton Technologies LTDUnclassifiedIPv410

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.