bgpreport

Network · data from 2026-11-12

AS135074 DREAM CLOUD INNOVATION AS135074

Registry name: DCIPL-AS-AP - DREAM CLOUD INNOVATION PTE. LTD., SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135074, 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.135.208.0/23 Invalid: maxLength Other origin onlycovered by 103.135.208.0/22 5 1%low visibility 5
91.192.107.0/24 Valid None 47 7%low visibility 29
82.110.108.0/22 Valid Other IRR onlyRADB 9 1%low visibility 4
156.239.237.0/24 Valid RIR databaseAFRINIC, RADB 379 56% 60
103.42.29.0/24 Valid RIR databaseAPNIC, RADB 47 7%low visibility 29
203.168.128.0/24 Valid RIR databaseAPNIC 47 7%low visibility 29
203.168.129.0/24 Valid RIR databaseAPNIC 25 4%low visibility 22
203.168.131.0/24 Valid RIR databaseAPNIC 25 4%low visibility 22
23.145.232.0/24 Valid RIR databaseARIN 12 2%low visibility 15
23.179.248.0/24 Valid RIR databaseARIN 12 2%low visibility 15
103.204.13.0/24 Valid RIR databaseAPNIC 12 2%low visibility 15
203.168.128.0/22 Valid RIR databaseAPNIC 12 2%low visibility 15
222.167.32.0/22 Valid RIR databaseAPNIC 11 2%low visibility 14

AS-SET

AS135074'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 49 are in fix.csv.

  • ROA: maxLength1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced45
ChangePrefix or setDetailFull-table peers
ROA: maxLength103.135.208.0/23ROA 103.135.208.0/22 AS135074 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 103.135.208.0/23.5 of 673
Route object: none103.135.208.0/23Route objects for it name AS59117, AS401160. A route object for 103.135.208.0/22 with origin AS135074 covers it (filters allowing more-specifics accept it). Add a route object with origin AS135074 in the RIR database for the space.5 of 673
Route object: none91.192.107.0/24No route object for it. Add a route object with origin AS135074 in the RIR database for the space.47 of 673
Route object: RIR82.110.108.0/22Route object only in RADB. Add it in the RIR database for the space.9 of 673

Route objects not announced

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

23.145.136.0/24ARINValid
23.145.152.0/24ARINValid
23.145.248.0/24ARINValid
23.167.152.0/24ARINValid
23.170.56.0/24ARINValid
23.180.136.0/24ARINValid
103.42.28.0/22APNIC, RADBValid
103.42.28.0/23APNICValid
103.42.28.0/24APNICValid
103.42.30.0/23APNICValid
103.42.30.0/24APNIC, RADBValid
103.42.31.0/24APNICValid
103.135.208.0/22APNIC, RADBValid
103.135.208.0/24APNICValid
103.135.209.0/24APNICValid
103.135.210.0/24APNICValid
103.135.211.0/24APNICValid
103.172.110.0/23APNICValid
103.172.110.0/24APNIC, RADBValid
103.172.111.0/24APNICValid
169.40.150.0/24RADB, RIPEValid
202.134.233.0/24APNIC, RADBValid
203.168.130.0/24APNICValid
203.168.192.0/24APNICValid
203.168.193.0/24APNICValid
203.168.194.0/24APNICValid
203.168.195.0/24APNICValid
203.168.196.0/24APNICValid
203.168.197.0/24APNICValid
203.168.198.0/24APNICValid
203.168.199.0/24APNICValid
203.168.200.0/24APNICValid
203.168.201.0/24APNICValid
203.168.202.0/24APNICValid
203.168.203.0/24APNICValid
203.168.204.0/24APNICValid
203.168.205.0/24APNICValid
203.168.206.0/24APNICValid
203.168.207.0/24APNICValid
222.167.32.0/23APNICValid
222.167.32.0/24APNICValid
222.167.33.0/24APNICValid
222.167.34.0/23APNICValid
222.167.34.0/24APNICValid
222.167.35.0/24APNICValid

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.