Network · data from 2026-11-12
AS136038 HDTIDCCLOUD-AS-AP - HDTIDC LIMITED
Registry name: HDTIDCCLOUD-AS-AP - HDTIDC LIMITED, HK · not in PeeringDB
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% |
| 45.142.155.0/24 | Valid | Other origin onlycovered by 45.142.152.0/22 | 552 82% |
| 2.59.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.91.224.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 103.254.72.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 193.239.150.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 103.254.72.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.254.74.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 671 100% |
| 103.254.75.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 192.197.113.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 193.239.150.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 671 100% |
| 194.126.202.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 671 100% |
| 199.212.57.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 2.59.155.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 670 100% |
| 45.91.226.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 45.142.152.0/22 | Valid | RIR databaseRIPE | 666 99% |
| 193.239.154.0/23 | Valid | RIR databaseRIPE | 666 99% |
| 45.142.152.0/24 | Valid | RIR databaseRADB, RIPE | 664 99% |
| 2.59.154.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 561 83% |
| 193.239.154.0/24 | Valid | RIR databaseRIPE | 556 83% |
| 2.59.152.0/24 | Valid | RIR databaseNTTCOM, RADB, RIPE | 553 82% |
| 103.99.208.0/23 | Valid | RIR databaseAPNIC | 506 75% |
| 185.202.100.0/22 | Valid | RIR databaseRIPE | 506 75% |
| 91.204.224.0/22 | Valid | RIR databaseRIPE | 504 75% |
| 103.80.132.0/22 | Valid | RIR databaseAPNIC | 498 74% |
| 103.80.135.0/24 | Valid | RIR databaseAPNIC, RADB | 2 0%low visibility |
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
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.142.154.0/24 | No 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. |
| Route object: none | 45.142.155.0/24 | Route 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. |
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/24 | RIPE | Invalid: maxLength |
| 45.91.225.0/24 | RIPE | Invalid: maxLength |
| 45.91.227.0/24 | RADB, RIPE | Valid |
| 45.142.153.0/24 | RADB | Valid |
| 45.158.20.0/22 | NTTCOM | No ROA |
| 91.204.225.0/24 | RADB, RIPE | Valid |
| 103.64.12.0/23 | APNIC | Valid |
| 103.78.242.0/23 | APNIC | Valid |
| 103.80.132.0/24 | APNIC, RADB | Valid |
| 103.80.133.0/24 | APNIC, RADB | Valid |
| 103.80.134.0/24 | APNIC, RADB | Valid |
| 103.91.217.0/24 | APNIC, RADB | Valid |
| 103.99.208.0/24 | APNIC, RADB | Valid |
| 103.99.209.0/24 | APNIC, RADB | Valid |
| 103.99.210.0/24 | APNIC, RADB | Valid |
| 103.137.64.0/23 | RADB | No ROA |
| 103.137.166.0/23 | RADB | No ROA |
| 103.137.166.0/24 | NTTCOM, RADB | No ROA |
| 103.137.167.0/24 | NTTCOM, RADB | No ROA |
| 103.151.172.0/23 | APNIC | Valid |
| 103.151.172.0/24 | APNIC, RADB | Valid |
| 103.151.173.0/24 | APNIC | Valid |
| 103.254.73.0/24 | APNIC, RADB | Valid |
| 109.66.88.0/23 | RADB, RIPE | Valid |
| 182.161.66.0/24 | APNIC, RADB | Valid |
| 185.202.103.0/24 | RIPE | Valid |
| 192.51.188.0/24 | APNIC, NTTCOM, RADB | Valid |
| 194.126.215.0/24 | RIPE | Valid |
| 194.126.219.0/24 | RIPE | Valid |
| 204.52.191.0/24 | APNIC | Valid |
| 2001:df3:cd80::/48 | RADB | No ROA |
| 2404:ab40::/32 | RADB | No ROA |
| 2404:b540::/32 | RADB | No 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.