Network · data from 2026-11-12
AS198144 RONDA COMUNICACIONES RONDA, S.L.
Registry name: RONDA COMUNICACIONES RONDA, S.L., ES · not in PeeringDB
31IPv4 routes
100.0% RPKI valid · 67.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
10 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS198144, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS198144, 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.
| 128.65.152.0/24 | Valid | Nonecovered by 128.65.152.0/23 | 673 100% |
| 128.65.153.0/24 | Valid | Nonecovered by 128.65.152.0/23 | 673 100% |
| 128.65.154.0/23 | Valid | Nonecovered by 128.65.152.0/21 | 673 100% |
| 128.65.156.0/22 | Valid | Nonecovered by 128.65.152.0/21 | 673 100% |
| 185.78.215.0/24 | Valid | Nonecovered by 185.78.214.0/23 | 673 100% |
| 176.97.231.0/24 | Valid | Nonecovered by 176.97.230.0/23 | 672 100% |
| 212.85.239.0/24 | Valid | Nonecovered by 212.85.238.0/23 | 672 100% |
| 176.97.228.0/24 | Valid | Nonecovered by 176.97.228.0/23 | 37 5%low visibility |
| 176.97.229.0/24 | Valid | Nonecovered by 176.97.228.0/23 | 37 5%low visibility |
| 176.97.230.0/24 | Valid | Nonecovered by 176.97.230.0/23 | 37 5%low visibility |
| 93.113.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.117.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.97.206.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.65.159.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.97.228.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.97.228.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 176.97.230.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.212.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.214.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.208.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.211.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.85.236.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 212.85.236.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.85.238.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS198144 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 14 are in fix.csv.
- Route object: none10
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 128.65.152.0/24 | No route object for it. A route object for 128.65.152.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 128.65.153.0/24 | No route object for it. A route object for 128.65.152.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 128.65.154.0/23 | No route object for it. A route object for 128.65.152.0/21 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 128.65.156.0/22 | No route object for it. A route object for 128.65.152.0/21 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 185.78.215.0/24 | No route object for it. A route object for 185.78.214.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 176.97.231.0/24 | No route object for it. A route object for 176.97.230.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 212.85.239.0/24 | No route object for it. A route object for 212.85.238.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 176.97.228.0/24 | No route object for it. A route object for 176.97.228.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 176.97.229.0/24 | No route object for it. A route object for 176.97.228.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
| Route object: none | 176.97.230.0/24 | No route object for it. A route object for 176.97.230.0/23 with origin AS198144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198144 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS198144 whose prefix no peer sees AS198144 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 128.65.152.0/23 | RIPE | Valid |
| 128.65.156.0/23 | RIPE | Invalid: maxLength |
| 193.42.4.0/23 | RIPE | Invalid: origin |
| 193.42.6.0/23 | RIPE | Invalid: origin |
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.