bgpreport

Network · data from 2026-11-12

AS138608 Cloud Host Asia

Registry name: CLOUDHOST-AS-AP - Cloud Host Pte Ltd, SG · PeeringDB

22IPv4 routes 100.0% RPKI valid · 90.9% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS138608, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138608, 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.189.234.0/24 Valid None 670 100% 67
103.189.235.0/24 Valid None 670 100% 67
103.187.146.0/24 Valid Other IRR onlyRADB 670 100% 67
103.187.147.0/24 Valid Other IRR onlyRADB 670 100% 67
103.210.54.0/24 Valid Other IRR onlyRADB 670 100% 67
103.210.55.0/24 Valid Other IRR onlyRADB 670 100% 67
103.250.10.0/24 Valid Other IRR onlyRADB 670 100% 67
103.250.11.0/24 Valid Other IRR onlyRADB 670 100% 67
103.13.206.0/24 Valid RIR databaseAPNIC 670 100% 67
103.13.207.0/24 Valid RIR databaseAPNIC 670 100% 67
103.30.194.0/24 Valid RIR databaseAPNIC 670 100% 67
103.30.195.0/24 Valid RIR databaseAPNIC 670 100% 67
103.37.124.0/24 Valid RIR databaseAPNIC 670 100% 67
103.37.125.0/24 Valid RIR databaseAPNIC 670 100% 67
103.56.82.0/24 Valid RIR databaseAPNIC 670 100% 67
103.56.83.0/24 Valid RIR databaseAPNIC 670 100% 67
103.67.186.0/24 Valid RIR databaseAPNIC 670 100% 67
103.67.187.0/24 Valid RIR databaseAPNIC 670 100% 67
103.134.152.0/24 Valid RIR databaseAPNIC 670 100% 67
103.134.153.0/24 Valid RIR databaseAPNIC 670 100% 67
103.134.154.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.171.19.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
2404:6740:3::/48 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS138608'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 21 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none103.189.234.0/24No route object for it. Add a route object with origin AS138608 in the RIR database for the space.670 of 673
Route object: none103.189.235.0/24No route object for it. Add a route object with origin AS138608 in the RIR database for the space.670 of 673
Route object: RIR103.187.146.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.187.147.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.210.54.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.210.55.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.250.10.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR103.250.11.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS138608 whose prefix no peer sees AS138608 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.13.206.0/23APNICValid
103.30.194.0/23APNICValid
103.37.124.0/23APNICValid
103.56.82.0/23APNICValid
103.67.186.0/23APNICValid
103.129.220.0/22RADBNo ROA
103.134.152.0/22RADBNo ROA
103.187.146.0/23RADBValid
103.210.54.0/23APNICValid
103.250.10.0/23RADBValid
2404:6740::/32RADBValid
2404:6740:1000::/48APNICValid
2404:6740:2000::/48APNICValid

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.