Network · data from 2026-11-12
AS24545 HKTEL-AS-AP - 8/F.,Sino Favour Centre ,1 OnYip Street , ChaiWan
Registry name: HKTEL-AS-AP - 8/F.,Sino Favour Centre ,1 OnYip Street , ChaiWan, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24545, 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.243.8.0/23 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.8.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 103.243.9.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 203.81.176.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.81.178.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.81.180.0/23 | No ROA | RIR databaseAPNIC | 672 100% |
| 203.81.180.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.81.181.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.81.182.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 203.81.183.0/24 | No ROA | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
AS-SET
AS24545 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 17 are in fix.csv.
- ROA: none10
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.243.8.0/23 | No ROA covers it. Add a ROA for AS24545, maxLength 23. |
| ROA: none | 103.243.8.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 103.243.9.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 203.81.176.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 203.81.178.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 203.81.180.0/23 | No ROA covers it. Add a ROA for AS24545, maxLength 23. |
| ROA: none | 203.81.180.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 203.81.181.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 203.81.182.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
| ROA: none | 203.81.183.0/24 | No ROA covers it. Add a ROA for AS24545, maxLength 24. |
Route objects not announced
Route objects with origin AS24545 whose prefix no peer sees AS24545 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 163.61.130.0/23 | APNIC | No ROA |
| 163.61.130.0/24 | APNIC | No ROA |
| 163.61.131.0/24 | APNIC | No ROA |
| 203.81.176.0/21 | APNIC, NTTCOM, RADB | No ROA |
| 203.81.177.0/24 | NTTCOM, RADB | No ROA |
| 203.81.179.0/24 | NTTCOM, RADB | No ROA |
| 2400:7e40::/32 | APNIC | 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.