Network · data from 2026-11-12
AS131314 CBC Tech - HKG
Registry name: CBC-AS-AP - CBC Tech International Limited, HK · PeeringDB
35IPv4 routes
77.1% RPKI valid · 85.7% with a route object
3IPv6 routes
100.0% RPKI valid · 100.0% with a route object
1RPKI invalid
1 origin · 0 maxLength
7No ROA
5 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
21Route objects not announced
registered with origin AS131314, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS131314, 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.
| 43.254.229.89/32 | Invalid: origin | None | 0 0%low visibility |
| 103.30.48.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.30.48.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.30.49.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.68.168.0/22 | No ROA | Other IRR onlyNTTCOM, RADB | 671 100% |
| 103.30.50.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.30.51.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.68.171.0/24 | No ROA | Other IRR onlyRADB | 378 56% |
| 202.57.196.0/24 | Valid | Other origin onlycovered by 202.57.196.0/22 | 444 66% |
| 113.21.233.0/24 | Valid | Other origin only | 438 65% |
| 120.136.20.0/24 | Valid | Other origin onlycovered by 120.136.20.0/22 | 412 61% |
| 113.21.232.0/24 | Valid | Other origin only | 404 60% |
| 202.57.204.0/24 | Valid | Other IRR onlyNTTCOM | 609 90% |
| 202.57.205.0/24 | Valid | Other IRR onlyNTTCOM | 609 90% |
| 2403:9b00:2000::/48 | Valid | Other IRR onlyNTTCOM | 609 96% |
| 103.200.220.0/24 | Valid | Other IRR onlyNTTCOM | 603 90% |
| 202.65.96.0/24 | Valid | Other IRR onlyNTTCOM | 597 89% |
| 202.57.199.0/24 | Valid | Other IRR onlyNTTCOM | 583 87% |
| 103.201.192.0/24 | Valid | Other IRR onlyNTTCOM | 566 84% |
| 202.57.201.0/24 | Valid | Other IRR onlyNTTCOM | 560 83% |
| 103.200.223.0/24 | Valid | Other IRR onlyNTTCOM | 545 81% |
| 120.136.22.0/24 | Valid | Other IRR onlyNTTCOM | 540 80% |
| 113.21.236.0/24 | Valid | Other IRR onlyNTTCOM | 530 79% |
| 202.47.107.0/24 | Valid | Other IRR onlyNTTCOM | 515 77% |
| 202.57.198.0/24 | Valid | Other IRR onlyNTTCOM | 507 75% |
| 202.47.111.0/24 | Valid | Other IRR onlyNTTCOM | 505 75% |
| 202.57.202.0/24 | Valid | Other IRR onlyNTTCOM | 477 71% |
| 113.21.239.0/24 | Valid | Other IRR onlyNTTCOM | 470 70% |
| 103.201.200.0/24 | Valid | Other IRR onlyNTTCOM | 463 69% |
| 120.136.18.0/24 | Valid | Other IRR onlyNTTCOM | 449 67% |
| 2403:9b00:2400::/48 | Valid | Other IRR onlyNTTCOM | 439 69% |
| 202.47.110.0/24 | Valid | Other IRR onlyNTTCOM | 295 44% |
| 202.57.200.0/24 | Valid | Other IRR onlyNTTCOM | 249 37% |
| 103.28.146.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.28.144.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 103.163.164.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 669 99% |
| 2401:a2a0:6000::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 103.28.147.0/24 | Valid | RIR databaseAPNIC | 61 9%low visibility |
AS-SET
PeeringDB's irr_as_set for AS131314: AS-CBCCOM131314. 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 (AS131314 isn't in the set, or no route object for AS131314 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 | AS131314 in it | Not covered |
|---|---|---|---|---|---|
| AS-CBCCOM131314 | APNIC | 11 | 1 | Yes | 3 |
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 62 are in fix.csv.
- ROA: origin1
- ROA: none7
- Route object: none5
- Route object: RIR28
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 43.254.229.89/32 | ROAs covering it name AS45110, not AS131314. If AS131314 should announce it, add a ROA for AS131314. |
| Route object: none | 43.254.229.89/32 | No route object for it. Add a route object with origin AS131314 in the RIR database for the space. |
| ROA: none | 103.30.48.0/22 | No ROA covers it. Add a ROA for AS131314, maxLength 22. |
| Route object: RIR | 103.30.48.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.30.48.0/24 | No ROA covers it. Add a ROA for AS131314, maxLength 24. |
| Route object: RIR | 103.30.48.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.30.49.0/24 | No ROA covers it. Add a ROA for AS131314, maxLength 24. |
| Route object: RIR | 103.30.49.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.68.168.0/22 | No ROA covers it. Add a ROA for AS131314, maxLength 22. |
| Route object: RIR | 103.68.168.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 103.30.50.0/24 | No ROA covers it. Add a ROA for AS131314, maxLength 24. |
| Route object: RIR | 103.30.50.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.30.51.0/24 | No ROA covers it. Add a ROA for AS131314, maxLength 24. |
| Route object: RIR | 103.30.51.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.68.171.0/24 | No ROA covers it. Add a ROA for AS131314, maxLength 24. |
| Route object: RIR | 103.68.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 202.57.196.0/24 | Route objects for it name AS4812, AS17621. A route object for 202.57.196.0/22 with origin AS131314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131314 in the RIR database for the space. |
| Route object: none | 113.21.233.0/24 | Route objects for it name AS134773. Add a route object with origin AS131314 in the RIR database for the space. |
| Route object: none | 120.136.20.0/24 | Route objects for it name AS4847. A route object for 120.136.20.0/22 with origin AS131314 covers it (filters allowing more-specifics accept it). Add a route object with origin AS131314 in the RIR database for the space. |
| Route object: none | 113.21.232.0/24 | Route objects for it name AS134773. Add a route object with origin AS131314 in the RIR database for the space. |
| Route object: RIR | 202.57.204.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.57.205.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2403:9b00:2000::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.200.220.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.65.96.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.57.199.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.201.192.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.57.201.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.200.223.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 120.136.22.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 113.21.236.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.47.107.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.57.198.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.47.111.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.57.202.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 113.21.239.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.201.200.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 120.136.18.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2403:9b00:2400::/48 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.47.110.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 202.57.200.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS131314 whose prefix no peer sees AS131314 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.254.232.0/21 | NTTCOM | No ROA |
| 103.28.144.0/22 | APNIC, RADB | Valid |
| 103.28.144.0/23 | APNIC | Valid |
| 103.28.145.0/24 | APNIC | Valid |
| 103.28.146.0/23 | APNIC | Valid |
| 103.29.29.0/24 | RADB | No ROA |
| 103.163.164.0/23 | NTTCOM | No ROA |
| 103.200.232.0/24 | NTTCOM | Valid |
| 113.21.237.0/24 | NTTCOM | Valid |
| 113.21.238.0/24 | NTTCOM | Valid |
| 119.161.120.0/22 | NTTCOM | Valid |
| 119.161.120.0/24 | NTTCOM | Valid |
| 120.136.16.0/22 | NTTCOM | Valid |
| 120.136.16.0/24 | NTTCOM | Valid |
| 120.136.20.0/22 | NTTCOM | Valid |
| 202.47.104.0/22 | NTTCOM | Valid |
| 202.47.106.0/24 | NTTCOM | Valid |
| 202.57.196.0/22 | NTTCOM | Valid |
| 202.57.200.0/22 | NTTCOM | No ROA |
| 202.57.204.0/22 | NTTCOM | No ROA |
| 2401:a2a0::/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.