Network · data from 2026-11-12
AS140570 Hong Kong Beecloud
Registry name: HKBCS-AS-AP - Hong Kong Beecloud System Technology Services Limited, HK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140570, 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.
| 79.109.236.0/22 | Invalid: origin | Other origin only | 1 0%low visibility |
| 103.155.90.20/32 | Invalid: origin | None | 1 0%low visibility |
| 49.52.48.48/32 | Invalid: origin | None | 0 0%low visibility |
| 103.147.13.55/32 | Invalid: origin | None | 0 0%low visibility |
| 103.147.13.77/32 | Invalid: origin | None | 0 0%low visibility |
| 103.27.108.191/32 | No ROA | None | 0 0%low visibility |
| 103.27.108.218/32 | No ROA | None | 0 0%low visibility |
| 205.198.108.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 205.198.109.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 205.198.110.0/24 | No ROA | Other IRR onlyNTTCOM | 673 100% |
| 205.198.111.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 209.146.15.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 38.47.49.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 38.47.62.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.150.78.0/24 | No ROA | Other IRR onlyNTTCOM | 672 100% |
| 209.146.4.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 103.150.118.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.224.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.226.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.227.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.231.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.232.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.233.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.168.234.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 154.91.5.0/24 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.91.7.0/24 | Valid | RIR databaseAFRINIC, NTTCOM, RADB | 672 100% |
| 2001:df3:7580::/48 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS140570: APNIC::AS140570:AS-HKBEECLOUD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS140570 isn't in the set, or no route object for AS140570 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS140570 in it | Not covered |
|---|---|---|---|---|---|
| APNIC::AS140570:AS-HKBEECLOUD | APNIC | 105 | 2 | Yes | 7 |
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.
- ROA: origin5
- ROA: none11
- Route object: none7
- Route object: RIR9
- Route object: not announced35
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 79.109.236.0/22 | ROAs covering it name AS137551, not AS140570. If AS140570 should announce it, add a ROA for AS140570. |
| Route object: none | 79.109.236.0/22 | Route objects for it name AS137551. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: origin | 103.155.90.20/32 | ROAs covering it name AS141153, AS153952, not AS140570. If AS140570 should announce it, add a ROA for AS140570. |
| Route object: none | 103.155.90.20/32 | No route object for it. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: origin | 49.52.48.48/32 | ROAs covering it name AS4538, not AS140570. If AS140570 should announce it, add a ROA for AS140570. |
| Route object: none | 49.52.48.48/32 | No route object for it. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: origin | 103.147.13.55/32 | ROAs covering it name AS38186, AS132883, not AS140570. If AS140570 should announce it, add a ROA for AS140570. |
| Route object: none | 103.147.13.55/32 | No route object for it. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: origin | 103.147.13.77/32 | ROAs covering it name AS38186, AS132883, not AS140570. If AS140570 should announce it, add a ROA for AS140570. |
| Route object: none | 103.147.13.77/32 | No route object for it. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: none | 103.27.108.191/32 | No ROA covers it. Add a ROA for AS140570, maxLength 32. |
| Route object: none | 103.27.108.191/32 | No route object for it. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: none | 103.27.108.218/32 | No ROA covers it. Add a ROA for AS140570, maxLength 32. |
| Route object: none | 103.27.108.218/32 | No route object for it. Add a route object with origin AS140570 in the RIR database for the space. |
| ROA: none | 205.198.108.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 205.198.108.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 205.198.109.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 205.198.109.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 205.198.110.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 205.198.110.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 205.198.111.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 205.198.111.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.146.15.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 209.146.15.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.47.49.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 38.47.49.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 38.47.62.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 38.47.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.150.78.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 38.150.78.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 209.146.4.0/24 | No ROA covers it. Add a ROA for AS140570, maxLength 24. |
| Route object: RIR | 209.146.4.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140570 whose prefix no peer sees AS140570 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.47.48.0/22 | NTTCOM, RADB | No ROA |
| 38.47.48.0/23 | NTTCOM | No ROA |
| 38.47.48.0/24 | NTTCOM, RADB | No ROA |
| 38.47.50.0/23 | NTTCOM | No ROA |
| 38.47.50.0/24 | NTTCOM, RADB | No ROA |
| 38.47.51.0/24 | NTTCOM, 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.63.0/24 | RADB | No ROA |
| 38.150.72.0/22 | NTTCOM | No ROA |
| 38.150.72.0/24 | NTTCOM | No ROA |
| 38.150.73.0/24 | NTTCOM | No ROA |
| 38.150.74.0/24 | NTTCOM | No ROA |
| 38.150.75.0/24 | NTTCOM | No ROA |
| 38.150.76.0/24 | RADB | No ROA |
| 38.150.77.0/24 | NTTCOM | No ROA |
| 38.150.78.0/23 | NTTCOM | No ROA |
| 45.146.162.0/23 | RADB | No ROA |
| 103.150.118.0/23 | APNIC, NTTCOM | Valid |
| 103.150.119.0/24 | APNIC | Valid |
| 203.168.224.0/23 | APNIC | Valid |
| 203.168.225.0/24 | APNIC | Valid |
| 203.168.226.0/23 | 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.230.0/24 | APNIC | Valid |
| 203.168.232.0/23 | APNIC | Valid |
| 203.168.234.0/23 | APNIC | Valid |
| 203.168.235.0/24 | APNIC | Valid |
| 205.198.108.0/22 | NTTCOM, RADB | No ROA |
| 205.198.108.0/23 | 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.