bgpreport

Network · data from 2026-11-12

AS25151 CYSO

Registry name: CYSO-AS Cyso Group B.V., NL · PeeringDB

16IPv4 routes 75.0% RPKI valid · 93.8% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS25151, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25151, 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.
37.72.138.0/24 No ROA RIR databaseRIPE 673 100% 67
62.129.139.0/24 No ROA RIR databaseRIPE 673 100% 67
62.129.149.0/24 No ROA RIR databaseRIPE 673 100% 67
185.123.55.0/24 No ROA RIR databaseRIPE 673 100% 67
85.158.206.0/24 Valid Nonecovered by 85.158.200.0/21 1 0%low visibility 2
2.57.56.0/24 Valid RIR databaseRIPE 673 100% 67
37.46.136.0/21 Valid RIR databaseRIPE 673 100% 67
80.85.160.0/23 Valid RIR databaseRIPE 673 100% 67
81.24.0.0/20 Valid RIR databaseRIPE 673 100% 67
85.158.200.0/21 Valid RIR databaseRIPE 673 100% 67
93.94.224.0/21 Valid RIR databaseRIPE 673 100% 67
109.235.72.0/21 Valid RIR databaseRIPE 673 100% 67
130.193.5.0/24 Valid RIR databaseRIPE 673 100% 67
185.54.112.0/22 Valid RIR databaseRIPE 673 100% 67
193.33.220.0/24 Valid RIR databaseRIPE 673 100% 67
45.134.223.0/24 Valid RIR databaseRIPE 672 100% 67
2001:678:c50::/48 Valid RIR databaseRIPE 636 100% 67
2a01:518::/32 Valid RIR databaseRIPE 636 100% 67
2a05:6cc0::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS25151's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 11 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none37.72.138.0/24No ROA covers it. Add a ROA for AS25151, maxLength 24.673 of 673
ROA: none62.129.139.0/24No ROA covers it. Add a ROA for AS25151, maxLength 24.673 of 673
ROA: none62.129.149.0/24No ROA covers it. Add a ROA for AS25151, maxLength 24.673 of 673
ROA: none185.123.55.0/24No ROA covers it. Add a ROA for AS25151, maxLength 24.673 of 673
Route object: none85.158.206.0/24No route object for it. A route object for 85.158.200.0/21 with origin AS25151 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25151 in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS25151 whose prefix no peer sees AS25151 announce. Many are kept on purpose (backup routes, space announced only in some places).

46.253.137.0/24RIPEValid
62.129.128.0/21RIPENo ROA
81.24.0.0/22RIPEValid
81.24.4.0/22RIPEValid
81.24.8.0/22RIPEValid
185.78.196.0/22RIPEValid

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.