Network · data from 2026-11-12
AS141718 HHXYTC-AS-AP - haoxiangyun
Registry name: HHXYTC-AS-AP - haoxiangyun, HK · not in PeeringDB
36IPv4 routes
63.9% RPKI valid · 72.2% with a route object
0IPv6 routes
5RPKI invalid
5 origin · 0 maxLength
8No ROA
10 with no route object for this origin
5Low visibility
seen by under 10% of full-table peers
6Route objects not announced
registered with origin AS141718, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS141718, 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.
| 154.194.45.0/24 | Invalid: origin | Other origin only | 33 5%low visibility |
| 176.102.169.0/24 | Invalid: origin | None | 33 5%low visibility |
| 107.151.236.0/24 | Invalid: origin | Other origin only | 29 4%low visibility |
| 141.11.63.0/24 | Invalid: origin | Other origin only | 22 3%low visibility |
| 156.237.1.0/24 | Invalid: origin | None | 10 1%low visibility |
| 154.6.18.0/24 | No ROA | None | 673 100% |
| 154.6.143.0/24 | No ROA | None | 673 100% |
| 154.6.145.0/24 | No ROA | None | 673 100% |
| 154.6.189.0/24 | No ROA | None | 673 100% |
| 154.6.190.0/24 | No ROA | None | 673 100% |
| 154.6.191.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 185.223.214.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.190.25.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 43.250.124.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.250.125.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 43.250.127.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 102.177.180.0/24 | Valid | RIR databaseAFRINIC, RADB | 673 100% |
| 103.100.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.163.132.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.209.129.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 172.110.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 172.110.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 172.110.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 172.110.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.216.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.217.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.233.17.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.147.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 202.71.10.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.155.90.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.155.226.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.156.222.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.156.223.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.194.86.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 103.211.103.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 156.225.68.0/24 | Valid | RIR databaseAFRINIC, RADB | 668 99% |
AS-SET
AS141718 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 30 are in fix.csv.
- ROA: origin5
- ROA: none8
- Route object: none10
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.194.45.0/24 | ROAs covering it name AS11404, AS17561, not AS141718. If AS141718 should announce it, add a ROA for AS141718. |
| Route object: none | 154.194.45.0/24 | Route objects for it name AS6079, AS17561. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: origin | 176.102.169.0/24 | ROAs covering it name AS834, not AS141718. If AS141718 should announce it, add a ROA for AS141718. |
| Route object: none | 176.102.169.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: origin | 107.151.236.0/24 | ROAs covering it name AS62468, AS211392, not AS141718. If AS141718 should announce it, add a ROA for AS141718. |
| Route object: none | 107.151.236.0/24 | Route objects for it name AS62468, AS139285, AS211392. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: origin | 141.11.63.0/24 | ROAs covering it name AS197858, not AS141718. If AS141718 should announce it, add a ROA for AS141718. |
| Route object: none | 141.11.63.0/24 | Route objects for it name AS197858. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: origin | 156.237.1.0/24 | ROAs covering it name AS17561, AS22516, not AS141718. If AS141718 should announce it, add a ROA for AS141718. |
| Route object: none | 156.237.1.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: none | 154.6.18.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| Route object: none | 154.6.18.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: none | 154.6.143.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| Route object: none | 154.6.143.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: none | 154.6.145.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| Route object: none | 154.6.145.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: none | 154.6.189.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| Route object: none | 154.6.189.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: none | 154.6.190.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| Route object: none | 154.6.190.0/24 | No route object for it. Add a route object with origin AS141718 in the RIR database for the space. |
| ROA: none | 154.6.191.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| Route object: RIR | 154.6.191.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 185.223.214.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
| ROA: none | 185.190.25.0/24 | No ROA covers it. Add a ROA for AS141718, maxLength 24. |
Route objects not announced
Route objects with origin AS141718 whose prefix no peer sees AS141718 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 102.212.5.0/24 | RADB | Valid |
| 154.6.152.0/22 | RADB | No ROA |
| 172.110.208.0/24 | RIPE | Valid |
| 185.142.30.0/24 | RIPE | Valid |
| 185.142.31.0/24 | RIPE | Valid |
| 199.178.81.0/24 | ALTDB | 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.