Network · data from 2026-11-12
AS142267 HKBEE-AS-AP - Hong Kong Beecloud System Technology Services Limited
Registry name: HKBEE-AS-AP - Hong Kong Beecloud System Technology Services Limited, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142267, 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.
| 38.150.72.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 103.129.55.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.230.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 154.91.4.0/24 | Valid | RIR databaseAFRINIC, NTTCOM, RADB | 672 100% |
AS-SET
AS142267 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 35 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced33
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.150.72.0/24 | No ROA covers it. Add a ROA for AS142267, maxLength 24. |
| Route object: RIR | 38.150.72.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS142267 whose prefix no peer sees AS142267 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.47.48.0/22 | RADB | No ROA |
| 38.47.48.0/24 | RADB | No ROA |
| 38.47.49.0/24 | RADB | No ROA |
| 38.47.50.0/24 | RADB | No ROA |
| 38.47.51.0/24 | RADB | No ROA |
| 38.47.60.0/22 | RADB | No ROA |
| 38.47.60.0/24 | RADB | No ROA |
| 38.47.61.0/24 | RADB | No ROA |
| 38.47.62.0/24 | RADB | No ROA |
| 38.47.63.0/24 | RADB | No ROA |
| 203.168.224.0/23 | APNIC | Valid |
| 203.168.224.0/24 | APNIC | Valid |
| 203.168.225.0/24 | APNIC | Valid |
| 203.168.226.0/23 | APNIC | Valid |
| 203.168.226.0/24 | APNIC | Valid |
| 203.168.227.0/24 | APNIC | Valid |
| 203.168.228.0/22 | APNIC | Valid |
| 203.168.228.0/23 | APNIC | Valid |
| 203.168.228.0/24 | APNIC | Valid |
| 203.168.229.0/24 | APNIC | Valid |
| 203.168.230.0/23 | APNIC | Valid |
| 203.168.231.0/24 | APNIC | Valid |
| 203.168.232.0/23 | APNIC | Valid |
| 203.168.232.0/24 | APNIC | Valid |
| 203.168.233.0/24 | APNIC | Valid |
| 203.168.234.0/23 | APNIC | Valid |
| 203.168.234.0/24 | APNIC | Valid |
| 203.168.235.0/24 | APNIC | Valid |
| 205.198.108.0/22 | RADB | No ROA |
| 205.198.108.0/23 | NTTCOM | No ROA |
| 205.198.108.0/24 | NTTCOM | No ROA |
| 205.198.109.0/24 | NTTCOM | No ROA |
| 205.198.110.0/24 | NTTCOM | 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.