Network · data from 2026-11-12
AS141190 JTPL-AS-AP - Jindun Technology PTE. Ltd.
Registry name: JTPL-AS-AP - Jindun Technology PTE. Ltd., SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS141190, 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.
| 156.240.66.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 45.200.11.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 103.156.54.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 45.200.10.0/23 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 45.200.96.0/21 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 45.200.112.0/21 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 154.211.0.0/23 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 156.240.64.0/21 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 156.240.80.0/21 | Valid | RIR databaseAFRINIC, RADB | 672 100% |
| 45.200.10.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 156.240.64.0/23 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 156.240.80.0/23 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 156.240.64.0/24 | Valid | RIR databaseAFRINIC, RADB | 670 100% |
| 156.240.80.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
AS-SET
AS141190 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 58 are in fix.csv.
- Route object: RIR2
- Route object: not announced56
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 156.240.66.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.200.11.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS141190 whose prefix no peer sees AS141190 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.200.96.0/22 | RADB | Valid |
| 45.200.96.0/23 | RADB | Valid |
| 45.200.96.0/24 | RADB | Valid |
| 45.200.97.0/24 | RADB | Valid |
| 45.200.98.0/23 | RADB | Valid |
| 45.200.98.0/24 | RADB | Valid |
| 45.200.99.0/24 | RADB | Valid |
| 45.200.100.0/22 | RADB | Valid |
| 45.200.100.0/23 | RADB | Valid |
| 45.200.100.0/24 | RADB | Valid |
| 45.200.101.0/24 | RADB | Valid |
| 45.200.102.0/23 | RADB | Valid |
| 45.200.102.0/24 | RADB | Valid |
| 45.200.103.0/24 | RADB | Valid |
| 45.200.112.0/22 | RADB | Valid |
| 45.200.112.0/23 | RADB | Valid |
| 45.200.112.0/24 | RADB | Valid |
| 45.200.113.0/24 | RADB | Valid |
| 45.200.114.0/23 | RADB | Valid |
| 45.200.114.0/24 | RADB | Valid |
| 45.200.115.0/24 | RADB | Valid |
| 45.200.116.0/22 | RADB | Valid |
| 45.200.116.0/23 | RADB | Valid |
| 45.200.116.0/24 | RADB | Valid |
| 45.200.117.0/24 | RADB | Valid |
| 45.200.118.0/23 | RADB | Valid |
| 45.200.118.0/24 | RADB | Valid |
| 45.200.119.0/24 | RADB | Valid |
| 103.156.54.0/24 | APNIC | Valid |
| 103.156.55.0/24 | APNIC | Valid |
| 154.211.0.0/24 | RADB | Valid |
| 154.211.1.0/24 | RADB | Valid |
| 156.240.64.0/22 | RADB | Valid |
| 156.240.65.0/24 | RADB | Valid |
| 156.240.66.0/24 | RADB | Valid |
| 156.240.67.0/24 | RADB | Valid |
| 156.240.68.0/22 | RADB | Valid |
| 156.240.68.0/23 | RADB | Valid |
| 156.240.68.0/24 | RADB | Valid |
| 156.240.69.0/24 | RADB | Valid |
| 156.240.70.0/23 | RADB | Valid |
| 156.240.70.0/24 | RADB | Valid |
| 156.240.71.0/24 | AFRINIC, RADB | Valid |
| 156.240.80.0/22 | RADB | Valid |
| 156.240.81.0/24 | RADB | Valid |
| 156.240.82.0/23 | RADB | Valid |
| 156.240.82.0/24 | RADB | Valid |
| 156.240.83.0/24 | RADB | Valid |
| 156.240.84.0/22 | RADB | Valid |
| 156.240.84.0/23 | RADB | Valid |
| 156.240.84.0/24 | RADB | Valid |
| 156.240.85.0/24 | RADB | Valid |
| 156.240.86.0/23 | RADB | Valid |
| 156.240.86.0/24 | RADB | Valid |
| 156.240.87.0/24 | RADB | Valid |
| 2406:7e40::/32 | APNIC | Valid |
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.