Network · data from 2026-11-12
AS218780 KINGNIU-LIMITED KINGNIU LIMITED
Registry name: KINGNIU-LIMITED KINGNIU LIMITED, HK · not in PeeringDB
44IPv4 routes
95.5% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
2No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
31Route objects not announced
registered with origin AS218780, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS218780, 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.
| 103.232.38.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.232.36.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 154.16.124.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.127.186.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 40.27.170.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 61.15.228.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 61.15.229.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 82.47.184.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 82.47.206.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 147.90.47.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.163.218.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 194.163.222.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.180.128.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 40.27.172.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 40.27.173.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 61.15.219.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 61.15.231.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 104.245.236.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 147.90.65.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 147.125.132.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 147.125.159.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 147.125.161.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 147.125.229.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 162.141.27.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 167.148.220.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.95.216.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 194.163.220.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 51.241.42.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 79.176.106.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 82.139.216.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 91.124.211.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 104.140.120.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 143.14.87.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 162.141.25.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 162.141.147.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 167.148.249.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 46.202.222.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 46.203.208.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 51.241.43.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 80.93.201.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 82.40.54.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 95.135.6.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 167.148.185.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 178.94.1.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
AS-SET
AS218780 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 37 are in fix.csv.
- ROA: none2
- Route object: RIR4
- Route object: not announced31
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.232.38.0/24 | No ROA covers it. Add a ROA for AS218780, maxLength 24. |
| Route object: RIR | 103.232.38.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.232.36.0/24 | No ROA covers it. Add a ROA for AS218780, maxLength 24. |
| Route object: RIR | 103.232.36.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 154.16.124.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.127.186.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218780 whose prefix no peer sees AS218780 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 40.27.168.0/24 | ARIN, RADB | Valid |
| 40.27.171.0/24 | ARIN, RADB | Valid |
| 46.233.55.0/24 | RADB | Valid |
| 61.15.195.0/24 | APNIC | Invalid: origin |
| 61.15.197.0/24 | APNIC | Invalid: origin |
| 61.15.199.0/24 | APNIC | Invalid: origin |
| 61.15.202.0/24 | APNIC | Invalid: origin |
| 61.15.204.0/24 | APNIC | Invalid: origin |
| 61.15.224.0/24 | APNIC, RADB | Valid |
| 61.15.230.0/24 | APNIC, RADB | Valid |
| 61.15.234.0/24 | APNIC, RADB | Valid |
| 61.18.160.0/24 | APNIC | Invalid: origin |
| 61.18.162.0/24 | APNIC | Invalid: origin |
| 61.18.164.0/24 | APNIC | Invalid: origin |
| 61.18.172.0/24 | APNIC | Invalid: origin |
| 61.18.174.0/24 | APNIC | Invalid: origin |
| 65.86.221.0/24 | ARIN, RADB | Valid |
| 77.216.38.0/24 | RADB, RIPE | Valid |
| 77.216.40.0/24 | RADB, RIPE | Valid |
| 77.216.42.0/24 | RADB, RIPE | Valid |
| 82.40.52.0/24 | RADB, RIPE | Valid |
| 82.40.53.0/24 | RADB, RIPE | Valid |
| 91.124.210.0/24 | RADB, RIPE | Valid |
| 96.62.204.0/24 | RADB, RIPE | Valid |
| 96.62.206.0/24 | RADB, RIPE | Valid |
| 109.64.247.0/24 | RADB, RIPE | Valid |
| 147.125.195.0/24 | RADB, RIPE | Valid |
| 147.125.231.0/24 | RADB, RIPE | Valid |
| 154.16.141.0/24 | RADB | Valid |
| 178.95.191.0/24 | RADB, RIPE | Valid |
| 194.163.216.0/24 | RADB, RIPE | 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.