Network · data from 2026-11-12
AS138985 CITSPVTLTD-AS-AP - CITS PVT (LTD)
Registry name: CITSPVTLTD-AS-AP - CITS PVT (LTD), PK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138985, 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.
| 14.192.138.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 43.247.121.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 103.20.134.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.125.242.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.138.50.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.138.51.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 116.90.108.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.63.211.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.255.151.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 116.90.106.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.138.50.0/23 | Valid | RIR databaseAPNIC, RADB | 2 0%low visibility |
AS-SET
AS138985 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 10 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 14.192.138.0/24 | ROAs covering it name AS141711, not AS138985. If AS138985 should announce it, add a ROA for AS138985. |
| Route object: none | 14.192.138.0/24 | Route objects for it name AS141711. Add a route object with origin AS138985 in the RIR database for the space. |
| ROA: origin | 43.247.121.0/24 | ROAs covering it name AS45814, not AS138985. If AS138985 should announce it, add a ROA for AS138985. |
| Route object: none | 43.247.121.0/24 | Route objects for it name AS45814. Add a route object with origin AS138985 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138985 whose prefix no peer sees AS138985 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.199.187.0/24 | AFRINIC | Invalid: origin |
| 115.167.124.0/24 | RADB | No ROA |
| 116.90.107.0/24 | APNIC | Valid |
| 116.90.109.0/24 | APNIC | Valid |
| 156.238.81.0/24 | AFRINIC | Invalid: origin |
| 202.69.42.0/24 | 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.