Network · data from 2026-11-12

AS205362 SKY WISP

Registry name: skywisp SKY WISP SERVICES LTD, CY · PeeringDB

11IPv4 routes 100.0% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS205362, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS205362, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


185.216.7.0/24	Valid	RIR databaseRIPE	673 100%	66
128.0.42.0/24	Valid	RIR databaseRIPE	672 100%	66
185.216.4.0/22	Valid	RIR databaseRIPE	671 100%	67
185.216.4.0/24	Valid	RIR databaseRIPE	671 100%	67
185.216.5.0/24	Valid	RIR databaseRIPE	671 100%	67
185.216.6.0/24	Valid	RIR databaseRIPE	671 100%	67
188.212.251.0/24	Valid	RIR databaseRIPE	671 100%	67
188.215.32.0/24	Valid	RIR databaseRIPE	671 100%	67
80.240.106.0/24	Valid	RIR databaseRIPE	670 100%	67
128.0.42.0/23	Valid	RIR databaseRIPE	670 100%	67
128.0.43.0/24	Valid	RIR databaseRIPE	670 100%	67

AS-SET

AS205362's PeeringDB record names no AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS205362 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.