bgpreport

Network · data from 2026-11-12

AS136744 DREAM POWER TECHNOLOGY LIMITED

Registry name: DPTL-AS-AP - DREAM POWER TECHNOLOGY LIMITED, HK · PeeringDB

54IPv4 routes 87.0% RPKI valid · 92.6% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
7No ROA 4 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
28Route objects not announced registered with origin AS136744, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136744, 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.

38.92.36.0/23 No ROA Other IRR onlyRADB 672 100% 67
38.92.36.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.92.37.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.96.253.0/24 No ROA Other IRR onlyRADB 672 100% 70
38.97.41.0/24 No ROA Other IRR onlyRADB 672 100% 70
38.146.217.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.97.42.0/24 No ROA Other IRR onlyRADB 669 99% 67
103.35.56.0/24 Valid Nonecovered by 103.35.56.0/22 673 100% 67
103.35.57.0/24 Valid Nonecovered by 103.35.56.0/22 673 100% 67
103.35.58.0/24 Valid Nonecovered by 103.35.56.0/22 673 100% 67
103.35.59.0/24 Valid Nonecovered by 103.35.56.0/22 673 100% 67
102.215.227.0/24 Valid Other IRR onlyRADB 673 100% 70
150.116.13.0/24 Valid Other IRR onlyRADB 673 100% 70
154.206.15.0/24 Valid Other IRR onlyRADB 672 100% 70
154.206.14.0/24 Valid Other IRR onlyRADB 669 99% 67
43.230.12.0/24 Valid RIR databaseAPNIC, RADB 673 100% 70
43.230.13.0/24 Valid RIR databaseAPNIC, RADB 673 100% 70
43.230.14.0/24 Valid RIR databaseAPNIC, RADB 673 100% 70
43.230.15.0/24 Valid RIR databaseAPNIC, RADB 673 100% 70
85.208.72.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
89.106.25.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
103.247.30.0/24 Valid RIR databaseAPNIC 673 100% 70
103.247.31.0/24 Valid RIR databaseAPNIC 673 100% 70
148.135.206.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
154.16.11.0/24 Valid RIR databaseAFRINIC, RADB 673 100% 70
155.117.32.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
155.117.52.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
155.117.54.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
185.104.12.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
192.101.64.0/24 Valid RIR databaseARIN, RADB 673 100% 70
193.58.106.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
212.30.61.0/24 Valid RIR databaseRADB, RIPE 673 100% 70
43.230.12.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
103.140.156.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
103.248.252.0/22 Valid RIR databaseAPNIC, RADB 672 100% 67
156.226.3.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
156.235.28.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
156.235.29.0/24 Valid RIR databaseAFRINIC, RADB 672 100% 67
213.209.151.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
156.235.28.0/23 Valid RIR databaseAFRINIC, RADB 671 100% 67
82.22.8.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
84.32.66.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
91.227.137.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 670 100% 66
103.140.156.0/24 Valid RIR databaseAPNIC 670 100% 67
103.140.157.0/24 Valid RIR databaseAPNIC 670 100% 67
103.248.252.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.248.253.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.248.254.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.248.255.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
155.117.61.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
181.214.237.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
45.89.31.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
45.74.49.0/24 Valid RIR databaseARIN, RADB 668 99% 66
181.215.210.0/24 Valid RIR databaseRADB, RIPE 4 1%low visibility 3

AS-SET

AS136744'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 50 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR11
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
ROA: none38.92.36.0/23No ROA covers it. Add a ROA for AS136744, maxLength 23.672 of 673
Route object: RIR38.92.36.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.92.36.0/24No ROA covers it. Add a ROA for AS136744, maxLength 24.672 of 673
Route object: RIR38.92.36.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.92.37.0/24No ROA covers it. Add a ROA for AS136744, maxLength 24.672 of 673
Route object: RIR38.92.37.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.96.253.0/24No ROA covers it. Add a ROA for AS136744, maxLength 24.672 of 673
Route object: RIR38.96.253.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.97.41.0/24No ROA covers it. Add a ROA for AS136744, maxLength 24.672 of 673
Route object: RIR38.97.41.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.146.217.0/24No ROA covers it. Add a ROA for AS136744, maxLength 24.672 of 673
Route object: RIR38.146.217.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.97.42.0/24No ROA covers it. Add a ROA for AS136744, maxLength 24.669 of 673
Route object: RIR38.97.42.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: none103.35.56.0/24No route object for it. A route object for 103.35.56.0/22 with origin AS136744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136744 in the RIR database for the space.673 of 673
Route object: none103.35.57.0/24No route object for it. A route object for 103.35.56.0/22 with origin AS136744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136744 in the RIR database for the space.673 of 673
Route object: none103.35.58.0/24No route object for it. A route object for 103.35.56.0/22 with origin AS136744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136744 in the RIR database for the space.673 of 673
Route object: none103.35.59.0/24No route object for it. A route object for 103.35.56.0/22 with origin AS136744 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136744 in the RIR database for the space.673 of 673
Route object: RIR102.215.227.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR150.116.13.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR154.206.15.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR154.206.14.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

38.45.162.0/24RADBNo ROA
38.102.14.0/24RADBNo ROA
43.230.12.0/23APNICValid
43.230.14.0/23APNICValid
45.195.193.0/24AFRINICInvalid: origin
45.196.192.0/24AFRINICInvalid: origin
45.196.196.0/24AFRINICInvalid: origin
45.200.134.0/23RADBNo ROA
45.206.60.0/24AFRINICValid
103.20.236.0/22RADBNo ROA
103.35.56.0/22RADB, RIPEValid
103.166.120.0/23RADBNo ROA
103.247.30.0/23APNICValid
103.248.252.0/23APNICValid
103.248.254.0/23APNICValid
113.31.16.0/22RADBNo ROA
147.125.208.0/24RADB, RIPEValid
154.206.14.0/23RADBValid
154.211.210.0/24AFRINICInvalid: origin
154.215.12.0/23RADBNo ROA
156.226.0.0/22RADBNo ROA
156.235.30.0/23RADBNo ROA
161.123.0.0/24AFRINICInvalid: origin
161.123.1.0/24AFRINICInvalid: origin
185.192.22.0/23RADBNo ROA
209.209.49.0/24ARINInvalid: origin
209.209.51.0/24ARINInvalid: origin
2405:40::/32APNICValid

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.