Network · data from 2026-11-12
AS140499 Khan Telecommunications
Registry name: KTPL-AS-AP - Khan Telecom, PK · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140499, 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.
| 144.79.150.0/23 | No ROA | None | 53 8%low visibility |
| 103.57.225.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.67.55.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.115.196.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.149.240.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.169.64.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 163.128.56.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.149.241.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 163.128.57.0/24 | Valid | RIR databaseAPNIC | 670 100% |
| 2001:df6:d340::/48 | Valid | RIR databaseAPNIC | 627 99% |
| 103.130.239.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
| 103.153.116.0/24 | Valid | RIR databaseAPNIC, RADB | 0 0%low visibility |
AS-SET
AS140499'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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 144.79.150.0/23 | No ROA covers it. Add a ROA for AS140499, maxLength 23. |
| Route object: none | 144.79.150.0/23 | No route object for it. Add a route object with origin AS140499 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140499 whose prefix no peer sees AS140499 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 119.152.126.0/24 | APNIC | Valid |
| 2001:df3:4980::/48 | APNIC | Valid |
| 2001:df6:ec80::/48 | 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.