Network · data from 2026-11-12
AS206702 cliko 7P SERVICIOS INTEGRADOS SLU
Registry name: cliko 7P SERVICIOS INTEGRADOS SLU, ES · not in PeeringDB
15IPv4 routes
100.0% RPKI valid · 0.0% with a route object
1IPv6 routes
100.0% RPKI valid · 0.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
16 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS206702, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS206702, 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.160.148.0/24 | Valid | None | 673 100% |
| 185.160.149.0/24 | Valid | None | 673 100% |
| 185.160.150.0/24 | Valid | None | 673 100% |
| 185.160.151.0/24 | Valid | None | 673 100% |
| 185.178.160.0/24 | Valid | Nonecovered by 185.178.160.0/22 | 673 100% |
| 185.178.161.0/24 | Valid | Nonecovered by 185.178.160.0/22 | 673 100% |
| 185.178.163.0/24 | Valid | Nonecovered by 185.178.160.0/22 | 673 100% |
| 185.194.192.0/24 | Valid | Nonecovered by 185.194.192.0/22 | 673 100% |
| 185.194.193.0/24 | Valid | Nonecovered by 185.194.192.0/22 | 673 100% |
| 185.194.195.0/24 | Valid | Nonecovered by 185.194.192.0/22 | 673 100% |
| 193.148.84.0/24 | Valid | Nonecovered by 193.148.84.0/22 | 673 100% |
| 193.148.85.0/24 | Valid | Nonecovered by 193.148.84.0/22 | 673 100% |
| 193.148.87.0/24 | Valid | Nonecovered by 193.148.84.0/22 | 673 100% |
| 2a0a:1141:4000::/34 | Valid | Nonecovered by 2a0a:1140::/29 | 635 100% |
| 185.178.162.0/24 | Valid | Nonecovered by 185.178.160.0/22 | 523 78% |
| 193.148.86.0/24 | Valid | Nonecovered by 193.148.84.0/22 | 523 78% |
AS-SET
AS206702 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 20 are in fix.csv.
- Route object: none16
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.160.148.0/24 | No route object for it. Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.160.149.0/24 | No route object for it. Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.160.150.0/24 | No route object for it. Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.160.151.0/24 | No route object for it. Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.178.160.0/24 | No route object for it. A route object for 185.178.160.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.178.161.0/24 | No route object for it. A route object for 185.178.160.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.178.163.0/24 | No route object for it. A route object for 185.178.160.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.194.192.0/24 | No route object for it. A route object for 185.194.192.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.194.193.0/24 | No route object for it. A route object for 185.194.192.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.194.195.0/24 | No route object for it. A route object for 185.194.192.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 193.148.84.0/24 | No route object for it. A route object for 193.148.84.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 193.148.85.0/24 | No route object for it. A route object for 193.148.84.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 193.148.87.0/24 | No route object for it. A route object for 193.148.84.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 2a0a:1141:4000::/34 | No route object for it. A route object for 2a0a:1140::/29 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 185.178.162.0/24 | No route object for it. A route object for 185.178.160.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
| Route object: none | 193.148.86.0/24 | No route object for it. A route object for 193.148.84.0/22 with origin AS206702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS206702 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206702 whose prefix no peer sees AS206702 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.178.160.0/22 | RIPE | No ROA |
| 185.194.192.0/22 | RIPE | No ROA |
| 193.148.84.0/22 | RIPE | No ROA |
| 2a0a:1140::/29 | RIPE | No 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.