Network · data from 2026-11-12
AS63631 Cloudbase
Registry name: Cloudbase - Guangdong Cloudbase Technology Co., Ltd., CN · PeeringDB
29IPv4 routes
100.0% RPKI valid · 82.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
5 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS63631, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS63631, 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.
| 119.161.138.0/24 | Valid | Nonecovered by 119.161.136.0/21 | 673 100% |
| 119.161.152.0/24 | Valid | Nonecovered by 119.161.152.0/21 | 673 100% |
| 119.161.153.0/24 | Valid | Nonecovered by 119.161.152.0/21 | 673 100% |
| 119.161.154.0/24 | Valid | Nonecovered by 119.161.152.0/21 | 673 100% |
| 119.161.155.0/24 | Valid | Nonecovered by 119.161.152.0/21 | 673 100% |
| 103.77.72.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.77.73.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.77.92.0/22 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.77.92.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.77.94.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 119.161.139.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 119.161.140.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.161.141.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.161.142.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.161.143.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.161.156.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 119.161.157.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 119.161.158.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.77.74.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.77.75.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 103.77.93.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 119.161.136.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 119.161.137.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 119.161.144.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 671 100% |
| 103.117.248.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.117.249.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.117.250.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.117.251.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.145.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
AS-SET
AS63631's PeeringDB record names no 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 42 are in fix.csv.
- Route object: none5
- Route object: RIR19
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 119.161.138.0/24 | No route object for it. A route object for 119.161.136.0/21 with origin AS63631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63631 in the RIR database for the space. |
| Route object: none | 119.161.152.0/24 | No route object for it. A route object for 119.161.152.0/21 with origin AS63631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63631 in the RIR database for the space. |
| Route object: none | 119.161.153.0/24 | No route object for it. A route object for 119.161.152.0/21 with origin AS63631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63631 in the RIR database for the space. |
| Route object: none | 119.161.154.0/24 | No route object for it. A route object for 119.161.152.0/21 with origin AS63631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63631 in the RIR database for the space. |
| Route object: none | 119.161.155.0/24 | No route object for it. A route object for 119.161.152.0/21 with origin AS63631 covers it (filters allowing more-specifics accept it). Add a route object with origin AS63631 in the RIR database for the space. |
| Route object: RIR | 103.77.72.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.73.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.92.0/22 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.92.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.94.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.139.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.140.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.141.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.142.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.143.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.156.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.74.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.75.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.93.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.136.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.137.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.161.144.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 AS63631 whose prefix no peer sees AS63631 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.77.72.0/22 | NTTCOM, RADB | Valid |
| 103.77.95.0/24 | NTTCOM | Valid |
| 103.117.248.0/22 | RADB | No ROA |
| 103.145.90.0/23 | RADB | No ROA |
| 103.145.91.0/24 | APNIC, NTTCOM | Valid |
| 119.161.136.0/21 | RADB | No ROA |
| 119.161.144.0/21 | RADB | No ROA |
| 119.161.145.0/24 | NTTCOM, RADB | Valid |
| 119.161.146.0/24 | NTTCOM, RADB | Valid |
| 119.161.147.0/24 | NTTCOM, RADB | Valid |
| 119.161.148.0/24 | NTTCOM, RADB | Valid |
| 119.161.149.0/24 | NTTCOM, RADB | Valid |
| 119.161.151.0/24 | NTTCOM, RADB | Valid |
| 119.161.152.0/21 | RADB | No ROA |
| 119.161.156.0/24 | RADB | Valid |
| 119.161.159.0/24 | RADB | Valid |
| 2403:22c0::/32 | APNIC | Valid |
| 2405:7ec0::/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.