bgpreport

Network · data from 2026-11-12

AS21119 WAN-NO KLERI 1 AS

Registry name: WAN-NO KLERI 1 AS, NO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS21119, 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.
82.117.32.0/20 Valid Nonecovered by 82.117.32.0/19 673 100% 66
5.226.160.0/21 Valid RIR databaseRIPE 673 100% 66
46.16.48.0/21 Valid RIR databaseRIPE 673 100% 66
80.86.128.0/20 Valid RIR databaseRIPE 673 100% 66
82.117.32.0/19 Valid RIR databaseRIPE 673 100% 66
89.105.32.0/20 Valid RIR databaseRIPE 673 100% 66
89.233.96.0/21 Valid RIR databaseRIPE 673 100% 66
93.187.80.0/21 Valid RIR databaseRIPE 673 100% 66
185.36.28.0/22 Valid RIR databaseRIPE 673 100% 66
193.169.42.0/23 Valid RIR databaseRIPE 673 100% 66
193.201.74.0/23 Valid RIR databaseRIPE 673 100% 66
213.179.48.0/20 Valid RIR databaseRIPE 673 100% 66
217.65.224.0/20 Valid RIR databaseRIPE 673 100% 66
2001:a90::/32 Valid RIR databaseRIPE 636 100% 69
2a01:b8c0::/32 Valid RIR databaseRIPE 636 100% 69
2a03:6240::/32 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS21119 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none82.117.32.0/20No route object for it. A route object for 82.117.32.0/19 with origin AS21119 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21119 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS21119 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.