Network · data from 2026-11-12
AS38476 GATI-AS-IN - GATI EXPRESS & SUPPLY CHAIN PRIVATE LIMITED
Registry name: GATI-AS-IN - GATI EXPRESS & SUPPLY CHAIN PRIVATE LIMITED, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38476, 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.
| 119.235.58.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 119.235.60.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 119.235.56.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 119.235.57.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 119.235.59.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 119.235.61.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS38476 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 9 are in fix.csv.
- ROA: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 119.235.58.0/24 | No ROA covers it. Add a ROA for AS38476, maxLength 24. |
| ROA: none | 119.235.60.0/24 | No ROA covers it. Add a ROA for AS38476, maxLength 24. |
| ROA: none | 119.235.56.0/24 | No ROA covers it. Add a ROA for AS38476, maxLength 24. |
| ROA: none | 119.235.57.0/24 | No ROA covers it. Add a ROA for AS38476, maxLength 24. |
| ROA: none | 119.235.59.0/24 | No ROA covers it. Add a ROA for AS38476, maxLength 24. |
| ROA: none | 119.235.61.0/24 | No ROA covers it. Add a ROA for AS38476, maxLength 24. |
Route objects not announced
Route objects with origin AS38476 whose prefix no peer sees AS38476 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 119.235.56.0/21 | APNIC | No ROA |
| 119.235.62.0/24 | APNIC, RADB | No ROA |
| 119.235.63.0/24 | APNIC, 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.