Network · data from 2026-11-12
AS9809 NovaNetwork
Registry name: NovaNetwork - SHENZHEN NOVA TECHNOLOGIES DEVELOPMENT.,LTD., CN · PeeringDB
28IPv4 routes
100.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
39Route objects not announced
registered with origin AS9809, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS9809, 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.
| 116.214.133.0/24 | Valid | Nonecovered by 116.214.128.0/19 | 673 100% |
| 116.214.134.0/24 | Valid | Nonecovered by 116.214.128.0/19 | 673 100% |
| 219.235.224.0/24 | Valid | Nonecovered by 219.235.224.0/21 | 673 100% |
| 219.235.225.0/24 | Valid | Nonecovered by 219.235.224.0/21 | 673 100% |
| 219.235.226.0/24 | Valid | Nonecovered by 219.235.224.0/21 | 673 100% |
| 219.235.227.0/24 | Valid | Nonecovered by 219.235.224.0/21 | 673 100% |
| 219.235.228.0/24 | Valid | Nonecovered by 219.235.224.0/21 | 673 100% |
| 219.235.229.0/24 | Valid | Nonecovered by 219.235.224.0/21 | 673 100% |
| 219.235.233.0/24 | Valid | Nonecovered by 219.235.232.0/21 | 673 100% |
| 219.235.234.0/24 | Valid | Nonecovered by 219.235.232.0/21 | 673 100% |
| 219.235.237.0/24 | Valid | Nonecovered by 219.235.232.0/21 | 673 100% |
| 219.235.251.0/24 | Valid | Nonecovered by 219.235.248.0/22 | 673 100% |
| 219.235.252.0/24 | Valid | Nonecovered by 219.235.248.0/21 | 673 100% |
| 219.235.255.0/24 | Valid | Nonecovered by 219.235.248.0/21 | 673 100% |
| 116.214.32.0/19 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.32.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.36.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.40.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.44.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.48.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.52.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.56.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.60.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 116.214.128.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 116.214.129.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 116.214.130.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 116.214.131.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 116.214.132.0/24 | Valid | Other IRR onlyRADB | 70 10% |
AS-SET
AS9809'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 67 are in fix.csv.
- Route object: none14
- Route object: RIR14
- Route object: not announced39
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 116.214.133.0/24 | No route object for it. A route object for 116.214.128.0/19 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 116.214.134.0/24 | No route object for it. A route object for 116.214.128.0/19 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.224.0/24 | No route object for it. A route object for 219.235.224.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.225.0/24 | No route object for it. A route object for 219.235.224.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.226.0/24 | No route object for it. A route object for 219.235.224.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.227.0/24 | No route object for it. A route object for 219.235.224.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.228.0/24 | No route object for it. A route object for 219.235.224.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.229.0/24 | No route object for it. A route object for 219.235.224.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.233.0/24 | No route object for it. A route object for 219.235.232.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.234.0/24 | No route object for it. A route object for 219.235.232.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.237.0/24 | No route object for it. A route object for 219.235.232.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.251.0/24 | No route object for it. A route object for 219.235.248.0/22 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.252.0/24 | No route object for it. A route object for 219.235.248.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: none | 219.235.255.0/24 | No route object for it. A route object for 219.235.248.0/21 with origin AS9809 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9809 in the RIR database for the space. |
| Route object: RIR | 116.214.32.0/19 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.32.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.36.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.40.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.44.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.48.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.52.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.56.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.60.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.129.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.130.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.131.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 116.214.132.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS9809 whose prefix no peer sees AS9809 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 116.214.32.0/24 | RADB | Valid |
| 116.214.33.0/24 | RADB | Valid |
| 116.214.34.0/24 | RADB | Valid |
| 116.214.35.0/24 | RADB | Valid |
| 116.214.36.0/24 | RADB | Valid |
| 116.214.37.0/24 | RADB | Valid |
| 116.214.38.0/24 | RADB | Valid |
| 116.214.39.0/24 | RADB | Valid |
| 116.214.40.0/24 | RADB | Valid |
| 116.214.41.0/24 | RADB | Valid |
| 116.214.42.0/24 | RADB | Valid |
| 116.214.43.0/24 | RADB | Valid |
| 116.214.44.0/24 | RADB | Valid |
| 116.214.45.0/24 | RADB | Valid |
| 116.214.46.0/24 | RADB | Valid |
| 116.214.47.0/24 | RADB | Valid |
| 116.214.48.0/24 | RADB | Valid |
| 116.214.49.0/24 | RADB | Valid |
| 116.214.50.0/24 | RADB | Valid |
| 116.214.51.0/24 | RADB | Valid |
| 116.214.52.0/24 | RADB | Valid |
| 116.214.53.0/24 | RADB | Valid |
| 116.214.54.0/24 | RADB | Valid |
| 116.214.55.0/24 | RADB | Valid |
| 116.214.56.0/24 | RADB | Valid |
| 116.214.57.0/24 | RADB | Valid |
| 116.214.58.0/24 | RADB | Valid |
| 116.214.59.0/24 | RADB | Valid |
| 116.214.60.0/24 | RADB | Valid |
| 116.214.61.0/24 | RADB | Valid |
| 116.214.62.0/24 | RADB | Valid |
| 116.214.63.0/24 | RADB | Valid |
| 116.214.128.0/19 | RADB | Valid |
| 219.235.224.0/19 | RADB | Valid |
| 219.235.224.0/21 | RADB | Valid |
| 219.235.232.0/21 | RADB | Valid |
| 219.235.240.0/21 | RADB | Valid |
| 219.235.248.0/21 | APNIC, RADB | Valid |
| 219.235.248.0/22 | APNIC, RADB | 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.