bgpreport

Network · data from 2026-11-12

AS59117 DREAM CLOUD INNOVATION AS59117

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS59117, 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.172.110.0/24 Invalid: origin Other origin only 2 0%low visibility 1
203.168.128.0/24 Invalid: origin Other origin only 2 0%low visibility 1
222.167.32.0/24 Invalid: maxLength Other origin onlycovered by 222.167.32.0/22 2 0%low visibility 1

AS-SET

AS59117'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 46 are in fix.csv.

  • ROA: origin2
  • ROA: maxLength1
  • Route object: none3
  • Route object: not announced40
ChangePrefix or setDetailFull-table peers
ROA: origin103.172.110.0/24ROAs covering it name AS13335, AS135074, AS209242, AS211392, AS401160, not AS59117. If AS59117 should announce it, add a ROA for AS59117.2 of 673
Route object: none103.172.110.0/24Route objects for it name AS135074, AS211392, AS401160. Add a route object with origin AS59117 in the RIR database for the space.2 of 673
ROA: origin203.168.128.0/24ROAs covering it name AS13335, AS135074, AS146806, AS209242, AS211392, AS401160, not AS59117. If AS59117 should announce it, add a ROA for AS59117.2 of 673
Route object: none203.168.128.0/24Route objects for it name AS135074, AS146806, AS211392, AS401160. Add a route object with origin AS59117 in the RIR database for the space.2 of 673
ROA: maxLength222.167.32.0/24ROA 222.167.32.0/22 AS59117 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 222.167.32.0/24.2 of 673
Route object: none222.167.32.0/24Route objects for it name AS135074, AS211392, AS401160. A route object for 222.167.32.0/22 with origin AS59117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59117 in the RIR database for the space.2 of 673

Route objects not announced

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

66.235.104.0/22ARINValid
82.110.108.0/22RADBValid
91.192.106.0/24RIPEInvalid: origin
103.42.28.0/22APNIC, RADBValid
103.42.28.0/23APNICValid
103.42.28.0/24APNICValid
103.42.29.0/24APNIC, RADBValid
103.42.30.0/23APNICValid
103.42.30.0/24APNIC, RADBValid
103.42.31.0/24APNICValid
103.135.208.0/22APNICValid
103.135.208.0/23APNICValid
103.135.208.0/24APNICValid
103.135.209.0/24APNICValid
103.135.210.0/23APNICValid
103.135.210.0/24APNICValid
103.135.211.0/24APNICValid
103.204.13.0/24APNIC, NTTCOMValid
125.3.192.0/21APNICValid
154.83.22.0/24NTTCOM, RADBNo ROA
154.83.23.0/24NTTCOM, RADBNo ROA
154.84.14.0/24NTTCOM, RADBNo ROA
154.84.15.0/24NTTCOM, RADBNo ROA
154.84.16.0/24NTTCOM, RADBNo ROA
154.84.17.0/24NTTCOM, RADBNo ROA
154.84.18.0/24NTTCOM, RADBNo ROA
154.84.19.0/24NTTCOM, RADBNo ROA
154.84.20.0/24NTTCOM, RADBNo ROA
154.84.21.0/24NTTCOM, RADBNo ROA
154.84.22.0/24NTTCOM, RADBNo ROA
154.84.23.0/24NTTCOM, RADBNo ROA
154.84.24.0/24NTTCOM, RADBNo ROA
154.84.25.0/24NTTCOM, RADBNo ROA
154.84.26.0/24NTTCOM, RADBNo ROA
154.84.27.0/24NTTCOM, RADBNo ROA
156.238.18.0/24NTTCOMNo ROA
156.239.237.0/24AFRINIC, RADBValid
169.40.150.0/24RADB, RIPEValid
202.134.233.0/24APNIC, RADBValid
222.167.32.0/22APNICValid

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.