Network · data from 2026-11-12
AS140202 FICCL-AS - Fullerton India Credit Co. Ltd.
Registry name: FICCL-AS - Fullerton India Credit Co. Ltd., IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140202, 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.
| 1.7.205.0/24 | Invalid: origin | Other origin only | 16 2%low visibility |
| 103.155.188.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.155.189.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS140202 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 1.7.205.0/24 | ROAs covering it name AS9583, not AS140202. If AS140202 should announce it, add a ROA for AS140202. |
| Route object: none | 1.7.205.0/24 | Route objects for it name AS9583. Add a route object with origin AS140202 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140202 whose prefix no peer sees AS140202 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.155.188.0/23 | 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.