Network · data from 2026-11-12
AS139750 IDCSERVICESNETINC-AS-AP - IDCServices.net Inc
Registry name: IDCSERVICESNETINC-AS-AP - IDCServices.net Inc, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139750, 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.
| 150.116.14.0/24 | Valid | Nonecovered by 150.116.14.0/23 | 673 100% |
| 150.116.15.0/24 | Valid | Nonecovered by 150.116.14.0/23 | 673 100% |
| 150.116.53.0/24 | Valid | None | 673 100% |
| 150.116.10.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.144.140.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 49.128.68.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.144.141.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 138.99.216.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 138.99.217.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 138.99.219.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.253.248.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.249.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.250.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.251.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.252.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.254.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.255.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 138.99.218.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 45.253.253.0/24 | Valid | RIR databaseAPNIC, RADB | 670 100% |
AS-SET
AS139750 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 30 are in fix.csv.
- Route object: none3
- Route object: RIR1
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 150.116.14.0/24 | No route object for it. A route object for 150.116.14.0/23 with origin AS139750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139750 in the RIR database for the space. |
| Route object: none | 150.116.15.0/24 | No route object for it. A route object for 150.116.14.0/23 with origin AS139750 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139750 in the RIR database for the space. |
| Route object: none | 150.116.53.0/24 | No route object for it. Add a route object with origin AS139750 in the RIR database for the space. |
| Route object: RIR | 150.116.10.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139750 whose prefix no peer sees AS139750 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.253.248.0/21 | NTTCOM, RADB | No ROA |
| 45.253.248.0/22 | APNIC | Valid |
| 45.253.252.0/22 | APNIC | Valid |
| 49.128.64.0/24 | APNIC | Valid |
| 49.128.66.0/24 | APNIC | Valid |
| 49.128.81.0/24 | APNIC, RADB | Valid |
| 49.128.91.0/24 | APNIC, RADB | Valid |
| 103.144.140.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.254.36.0/24 | RADB | No ROA |
| 103.254.37.0/24 | RADB | No ROA |
| 103.254.38.0/24 | RADB | No ROA |
| 103.254.39.0/24 | RADB | No ROA |
| 138.99.216.0/22 | APNIC | Valid |
| 146.88.88.0/24 | RADB | No ROA |
| 146.88.89.0/24 | RADB | No ROA |
| 146.88.90.0/24 | RADB | No ROA |
| 146.88.91.0/24 | RADB | No ROA |
| 146.88.92.0/24 | RADB | No ROA |
| 146.88.93.0/24 | RADB | No ROA |
| 146.88.94.0/24 | RADB | No ROA |
| 146.88.95.0/24 | RADB | No ROA |
| 150.116.14.0/23 | RADB | Valid |
| 159.117.40.0/21 | RADB | No ROA |
| 159.117.40.0/24 | RADB | No ROA |
| 159.117.96.0/21 | RADB | No ROA |
| 2405:6e40::/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.