bgpreport

Network · data from 2026-11-12

AS136038 HDTIDCCLOUD-AS-AP - HDTIDC LIMITED

Registry name: HDTIDCCLOUD-AS-AP - HDTIDC LIMITED, HK · not in PeeringDB

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

Announced routes

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

45.142.154.0/24 Valid Nonecovered by 45.142.152.0/22 586 87% 67
45.142.155.0/24 Valid Other origin onlycovered by 45.142.152.0/22 552 82% 67
2.59.152.0/22 Valid RIR databaseRIPE 673 100% 67
45.91.224.0/22 Valid RIR databaseRIPE 673 100% 67
103.254.72.0/22 Valid RIR databaseAPNIC 673 100% 67
193.239.150.0/23 Valid RIR databaseRIPE 672 100% 67
103.254.72.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.254.74.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.254.75.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
192.197.113.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
193.239.150.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 671 100% 67
194.126.202.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 671 100% 67
199.212.57.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
2.59.155.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 670 100% 67
45.91.226.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
45.142.152.0/22 Valid RIR databaseRIPE 666 99% 67
193.239.154.0/23 Valid RIR databaseRIPE 666 99% 67
45.142.152.0/24 Valid RIR databaseRADB, RIPE 664 99% 67
2.59.154.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 561 83% 67
193.239.154.0/24 Valid RIR databaseRIPE 556 83% 67
2.59.152.0/24 Valid RIR databaseNTTCOM, RADB, RIPE 553 82% 67
103.99.208.0/23 Valid RIR databaseAPNIC 506 75% 66
185.202.100.0/22 Valid RIR databaseRIPE 506 75% 66
91.204.224.0/22 Valid RIR databaseRIPE 504 75% 67
103.80.132.0/22 Valid RIR databaseAPNIC 498 74% 66
103.80.135.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

AS136038 isn't in PeeringDB, where networks name their 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 35 are in fix.csv.

  • Route object: none2
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
Route object: none45.142.154.0/24No route object for it. A route object for 45.142.152.0/22 with origin AS136038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136038 in the RIR database for the space.586 of 673
Route object: none45.142.155.0/24Route objects for it name AS136526, AS212921. A route object for 45.142.152.0/22 with origin AS136038 covers it (filters allowing more-specifics accept it). Add a route object with origin AS136038 in the RIR database for the space.552 of 673

Route objects not announced

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

2.59.153.0/24RIPEInvalid: maxLength
45.91.225.0/24RIPEInvalid: maxLength
45.91.227.0/24RADB, RIPEValid
45.142.153.0/24RADBValid
45.158.20.0/22NTTCOMNo ROA
91.204.225.0/24RADB, RIPEValid
103.64.12.0/23APNICValid
103.78.242.0/23APNICValid
103.80.132.0/24APNIC, RADBValid
103.80.133.0/24APNIC, RADBValid
103.80.134.0/24APNIC, RADBValid
103.91.217.0/24APNIC, RADBValid
103.99.208.0/24APNIC, RADBValid
103.99.209.0/24APNIC, RADBValid
103.99.210.0/24APNIC, RADBValid
103.137.64.0/23RADBNo ROA
103.137.166.0/23RADBNo ROA
103.137.166.0/24NTTCOM, RADBNo ROA
103.137.167.0/24NTTCOM, RADBNo ROA
103.151.172.0/23APNICValid
103.151.172.0/24APNIC, RADBValid
103.151.173.0/24APNICValid
103.254.73.0/24APNIC, RADBValid
109.66.88.0/23RADB, RIPEValid
182.161.66.0/24APNIC, RADBValid
185.202.103.0/24RIPEValid
192.51.188.0/24APNIC, NTTCOM, RADBValid
194.126.215.0/24RIPEValid
194.126.219.0/24RIPEValid
204.52.191.0/24APNICValid
2001:df3:cd80::/48RADBNo ROA
2404:ab40::/32RADBNo ROA
2404:b540::/32RADBNo ROA

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.