Network · data from 2026-11-12
AS198731 Prisco Electronica
Registry name: PRISCO-AS Prisco Electronica S.L., ES · PeeringDB
22IPv4 routes
100.0% RPKI valid · 0.0% with a route object
12IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
22 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS198731, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS198731, 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.
| 5.1.32.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 672 100% |
| 5.1.35.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 672 100% |
| 5.1.36.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 672 100% |
| 5.1.37.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 672 100% |
| 5.1.39.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 672 100% |
| 85.184.225.0/24 | Valid | Nonecovered by 85.184.224.0/22 | 672 100% |
| 85.184.226.0/24 | Valid | Nonecovered by 85.184.224.0/22 | 672 100% |
| 85.184.227.0/24 | Valid | Nonecovered by 85.184.224.0/22 | 672 100% |
| 185.45.28.0/24 | Valid | Nonecovered by 185.45.28.0/22 | 672 100% |
| 185.45.29.0/24 | Valid | Nonecovered by 185.45.28.0/22 | 672 100% |
| 185.45.30.0/24 | Valid | Nonecovered by 185.45.28.0/22 | 672 100% |
| 185.45.31.0/24 | Valid | Nonecovered by 185.45.28.0/22 | 672 100% |
| 185.64.232.0/24 | Valid | Nonecovered by 185.64.232.0/22 | 672 100% |
| 185.64.233.0/24 | Valid | Nonecovered by 185.64.232.0/22 | 672 100% |
| 185.64.234.0/24 | Valid | Nonecovered by 185.64.232.0/22 | 672 100% |
| 185.64.235.0/24 | Valid | Nonecovered by 185.64.232.0/22 | 672 100% |
| 81.173.41.0/24 | Valid | Nonecovered by 81.173.40.0/23 | 671 100% |
| 5.1.33.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 670 100% |
| 5.1.34.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 670 100% |
| 5.1.38.0/24 | Valid | Nonecovered by 5.1.32.0/21 | 670 100% |
| 85.184.224.0/24 | Valid | Nonecovered by 85.184.224.0/22 | 670 100% |
| 81.173.40.0/24 | Valid | Nonecovered by 81.173.40.0/23 | 669 99% |
| 2a00:bc40::/40 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:f01::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:f02::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:f03::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:f04::/48 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:1000::/36 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:2000::/36 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:3000::/36 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:4000::/36 | Valid | RIR databaseRIPE | 633 100% |
| 2a00:bc40:b00::/40 | Valid | RIR databaseRIPE | 632 99% |
| 2a00:bc40:f0e::/48 | Valid | RIR databaseRIPE | 632 99% |
| 2a00:bc40:e000::/36 | Valid | RIR databaseRIPE | 632 99% |
AS-SET
AS198731'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 29 are in fix.csv.
- Route object: none22
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.1.32.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.35.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.36.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.37.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.39.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 85.184.225.0/24 | No route object for it. A route object for 85.184.224.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 85.184.226.0/24 | No route object for it. A route object for 85.184.224.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 85.184.227.0/24 | No route object for it. A route object for 85.184.224.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.45.28.0/24 | No route object for it. A route object for 185.45.28.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.45.29.0/24 | No route object for it. A route object for 185.45.28.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.45.30.0/24 | No route object for it. A route object for 185.45.28.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.45.31.0/24 | No route object for it. A route object for 185.45.28.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.64.232.0/24 | No route object for it. A route object for 185.64.232.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.64.233.0/24 | No route object for it. A route object for 185.64.232.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.64.234.0/24 | No route object for it. A route object for 185.64.232.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 185.64.235.0/24 | No route object for it. A route object for 185.64.232.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 81.173.41.0/24 | No route object for it. A route object for 81.173.40.0/23 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.33.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.34.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 5.1.38.0/24 | No route object for it. A route object for 5.1.32.0/21 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 85.184.224.0/24 | No route object for it. A route object for 85.184.224.0/22 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
| Route object: none | 81.173.40.0/24 | No route object for it. A route object for 81.173.40.0/23 with origin AS198731 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198731 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198731 whose prefix no peer sees AS198731 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.1.32.0/21 | RIPE | No ROA |
| 81.173.40.0/23 | RIPE | No ROA |
| 85.184.224.0/22 | RIPE | No ROA |
| 185.45.28.0/22 | RIPE | No ROA |
| 185.64.232.0/22 | RIPE | No ROA |
| 2a00:bc40::/29 | RIPE | No ROA |
| 2a00:bc40:c00::/40 | RIPE | Valid |
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.