Network · data from 2026-11-12
AS207714 TECNALIA Fundacion Tecnalia Research and Innovation
Registry name: TECNALIA Fundacion Tecnalia Research and Innovation, ES · not in PeeringDB
26IPv4 routes
96.2% RPKI valid · 3.8% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
25 with no route object for this origin
10Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS207714, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS207714, 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.
| 150.241.32.0/19 | No ROA | Other origin only | 670 100% |
| 150.241.0.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.1.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.2.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.3.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.4.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.5.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.8.0/23 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.10.0/23 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.12.0/23 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.14.0/23 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.16.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.17.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.18.0/24 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.22.0/23 | Valid | Nonecovered by 150.241.0.0/19 | 672 100% |
| 150.241.0.0/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.0.16/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.0.32/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.0/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.16/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.32/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.48/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.128/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.144/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.1.160/28 | Valid | Nonecovered by 150.241.0.0/19 | 12 2%low visibility |
| 150.241.0.0/19 | Valid | RIR databaseRIPE | 670 100% |
| 2a10:1500:4::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS207714 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 26 are in fix.csv.
- ROA: none1
- Route object: none25
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 150.241.32.0/19 | No ROA covers it. Add a ROA for AS207714, maxLength 19. |
| Route object: none | 150.241.32.0/19 | Route objects for it name AS198853. Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.0.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.2.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.3.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.4.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.5.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.8.0/23 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.10.0/23 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.12.0/23 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.14.0/23 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.16.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.17.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.18.0/24 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.22.0/23 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.0.0/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.0.16/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.0.32/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.0/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.16/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.32/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.48/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.128/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.144/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
| Route object: none | 150.241.1.160/28 | No route object for it. A route object for 150.241.0.0/19 with origin AS207714 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS207714 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS207714 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.