Network · data from 2026-11-12
AS14709 Cable Onda AS14709
Registry name: AS14709 - Cable Onda, PA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14709, 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.
| 148.177.120.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 181.197.52.0/24 | Valid | Nonecovered by 181.197.52.0/22 | 671 100% |
| 181.197.53.0/24 | Valid | Nonecovered by 181.197.52.0/22 | 671 100% |
| 181.197.54.0/24 | Valid | Nonecovered by 181.197.52.0/22 | 671 100% |
| 181.197.55.0/24 | Valid | Nonecovered by 181.197.52.0/22 | 671 100% |
| 181.197.124.0/24 | Valid | Nonecovered by 181.197.124.0/22 | 671 100% |
| 181.197.125.0/24 | Valid | Nonecovered by 181.197.124.0/22 | 671 100% |
| 181.197.126.0/24 | Valid | Nonecovered by 181.197.124.0/22 | 671 100% |
| 181.197.127.0/24 | Valid | Nonecovered by 181.197.124.0/22 | 671 100% |
| 190.57.32.0/23 | Valid | Nonecovered by 190.57.32.0/20 | 670 100% |
| 190.57.40.0/22 | Valid | Nonecovered by 190.57.32.0/20 | 670 100% |
| 190.57.44.0/22 | Valid | Nonecovered by 190.57.32.0/20 | 670 100% |
| 200.108.43.0/24 | Valid | Nonecovered by 200.108.40.0/22 | 670 100% |
| 200.108.52.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 670 100% |
| 200.108.54.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 670 100% |
| 200.108.56.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 670 100% |
| 200.108.58.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 670 100% |
| 200.108.62.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 670 100% |
| 200.108.34.0/24 | Valid | Nonecovered by 200.108.32.0/20 | 667 99% |
| 200.108.42.0/24 | Valid | Nonecovered by 200.108.40.0/22 | 666 99% |
| 200.108.32.0/24 | Valid | Nonecovered by 200.108.32.0/20 | 3 0%low visibility |
| 200.108.38.0/24 | Valid | Nonecovered by 200.108.36.0/22 | 3 0%low visibility |
| 200.108.39.0/24 | Valid | Nonecovered by 200.108.36.0/22 | 3 0%low visibility |
| 200.108.40.0/24 | Valid | Nonecovered by 200.108.40.0/22 | 3 0%low visibility |
| 200.108.41.0/24 | Valid | Nonecovered by 200.108.40.0/22 | 3 0%low visibility |
| 200.108.48.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 3 0%low visibility |
| 200.108.50.0/23 | Valid | Nonecovered by 200.108.48.0/20 | 3 0%low visibility |
| 200.108.32.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 200.108.48.0/20 | Valid | Other IRR onlyRADB | 672 100% |
| 138.186.88.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 138.186.90.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 138.186.91.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 200.108.35.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 200.108.36.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 138.186.89.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 200.108.33.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.108.46.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 200.108.47.0/24 | Valid | Other IRR onlyRADB | 3 0%low visibility |
| 138.186.88.0/22 | Valid | RIR databaseLACNIC, RADB | 671 100% |
| 190.140.250.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 190.141.31.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 190.141.172.0/24 | Valid | RIR databaseLACNIC | 670 100% |
| 200.46.1.0/24 | Valid | RIR databaseLACNIC | 666 99% |
AS-SET
AS14709'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 46 are in fix.csv.
- ROA: none1
- Route object: none26
- Route object: RIR12
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 148.177.120.0/24 | No ROA covers it. Add a ROA for AS14709, maxLength 24. |
| Route object: RIR | 148.177.120.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 181.197.52.0/24 | No route object for it. A route object for 181.197.52.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.53.0/24 | No route object for it. A route object for 181.197.52.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.54.0/24 | No route object for it. A route object for 181.197.52.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.55.0/24 | No route object for it. A route object for 181.197.52.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.124.0/24 | No route object for it. A route object for 181.197.124.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.125.0/24 | No route object for it. A route object for 181.197.124.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.126.0/24 | No route object for it. A route object for 181.197.124.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 181.197.127.0/24 | No route object for it. A route object for 181.197.124.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 190.57.32.0/23 | No route object for it. A route object for 190.57.32.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 190.57.40.0/22 | No route object for it. A route object for 190.57.32.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 190.57.44.0/22 | No route object for it. A route object for 190.57.32.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.43.0/24 | No route object for it. A route object for 200.108.40.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.52.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.54.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.56.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.58.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.62.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.34.0/24 | No route object for it. A route object for 200.108.32.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.42.0/24 | No route object for it. A route object for 200.108.40.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.32.0/24 | No route object for it. A route object for 200.108.32.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.38.0/24 | No route object for it. A route object for 200.108.36.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.39.0/24 | No route object for it. A route object for 200.108.36.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.40.0/24 | No route object for it. A route object for 200.108.40.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.41.0/24 | No route object for it. A route object for 200.108.40.0/22 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.48.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: none | 200.108.50.0/23 | No route object for it. A route object for 200.108.48.0/20 with origin AS14709 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14709 in the RIR database for the space. |
| Route object: RIR | 200.108.32.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.48.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.186.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.186.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.186.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.35.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 138.186.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.33.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.108.47.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14709 whose prefix no peer sees AS14709 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 181.197.52.0/22 | LACNIC | Valid |
| 181.197.124.0/22 | LACNIC | Valid |
| 190.57.32.0/20 | LACNIC, RADB | Valid |
| 200.108.32.0/19 | LACNIC | Valid |
| 200.108.40.0/22 | RADB | Valid |
| 200.108.44.0/23 | RADB | Valid |
| 2800:ce0::/32 | LACNIC | 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.