bgpreport

Network · data from 2026-11-12

AS57335 AS-CLUE Predicted Paths BV

Registry name: AS-CLUE Predicted Paths BV, NL · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS57335, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57335, 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.203.204.0/23 No ROA Other origin onlycovered by 185.203.204.0/22 673 100% 67
185.203.206.0/24 No ROA Other origin onlycovered by 185.203.204.0/22 673 100% 67

AS-SET

AS57335 isn't in PeeringDB, where networks name their 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 15 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none185.203.204.0/23No ROA covers it. Add a ROA for AS57335, maxLength 23.673 of 673
Route object: none185.203.204.0/23Route objects for it name AS199524. A route object for 185.203.204.0/22 with origin AS57335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57335 in the RIR database for the space.673 of 673
ROA: none185.203.206.0/24No ROA covers it. Add a ROA for AS57335, maxLength 24.673 of 673
Route object: none185.203.206.0/24Route objects for it name AS199524. A route object for 185.203.204.0/22 with origin AS57335 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57335 in the RIR database for the space.673 of 673

Route objects not announced

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

45.146.20.0/22RADBNo ROA
45.154.216.0/22RADBNo ROA
185.203.204.0/22RADBNo ROA
2a0c:d2c0::/29RADBNo ROA
2a0c:d2c0::/32RIPENo ROA
2a0c:d2c1::/48RIPENo ROA
2a0c:d2c1:1::/48RIPENo ROA
2a0c:d2c1:2::/48RIPENo ROA
2a0c:d2c1:3::/48RIPENo ROA
2a0c:d2c2::/32RIPENo ROA
2a0c:d2c4::/32RIPENo ROA

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.