Network · data from 2026-11-12
AS55333 TATA-2-NET-IN - EL6,TTC Industrial Area,Electronics Zone
Registry name: TATA-2-NET-IN - EL6,TTC Industrial Area,Electronics Zone, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55333, 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.
| 103.144.56.0/24 | No ROA | Nonecovered by 103.144.56.0/23 | 673 100% |
| 103.144.57.0/24 | No ROA | Nonecovered by 103.144.56.0/23 | 673 100% |
| 182.173.64.0/24 | No ROA | Nonecovered by 182.173.64.0/22 | 673 100% |
| 182.173.65.0/24 | No ROA | Nonecovered by 182.173.64.0/22 | 673 100% |
| 182.173.66.0/24 | No ROA | Nonecovered by 182.173.64.0/22 | 673 100% |
| 182.173.67.0/24 | No ROA | Nonecovered by 182.173.64.0/22 | 673 100% |
| 182.173.64.0/22 | No ROA | RIR databaseAPNIC | 673 100% |
| 202.72.98.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS55333 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 14 are in fix.csv.
- ROA: none7
- Route object: none6
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.144.56.0/24 | No ROA covers it. Add a ROA for AS55333, maxLength 24. |
| Route object: none | 103.144.56.0/24 | No route object for it. A route object for 103.144.56.0/23 with origin AS55333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55333 in the RIR database for the space. |
| ROA: none | 103.144.57.0/24 | No ROA covers it. Add a ROA for AS55333, maxLength 24. |
| Route object: none | 103.144.57.0/24 | No route object for it. A route object for 103.144.56.0/23 with origin AS55333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55333 in the RIR database for the space. |
| ROA: none | 182.173.64.0/24 | No ROA covers it. Add a ROA for AS55333, maxLength 24. |
| Route object: none | 182.173.64.0/24 | No route object for it. A route object for 182.173.64.0/22 with origin AS55333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55333 in the RIR database for the space. |
| ROA: none | 182.173.65.0/24 | No ROA covers it. Add a ROA for AS55333, maxLength 24. |
| Route object: none | 182.173.65.0/24 | No route object for it. A route object for 182.173.64.0/22 with origin AS55333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55333 in the RIR database for the space. |
| ROA: none | 182.173.66.0/24 | No ROA covers it. Add a ROA for AS55333, maxLength 24. |
| Route object: none | 182.173.66.0/24 | No route object for it. A route object for 182.173.64.0/22 with origin AS55333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55333 in the RIR database for the space. |
| ROA: none | 182.173.67.0/24 | No ROA covers it. Add a ROA for AS55333, maxLength 24. |
| Route object: none | 182.173.67.0/24 | No route object for it. A route object for 182.173.64.0/22 with origin AS55333 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55333 in the RIR database for the space. |
| ROA: none | 182.173.64.0/22 | No ROA covers it. Add a ROA for AS55333, maxLength 22. |
Route objects not announced
Route objects with origin AS55333 whose prefix no peer sees AS55333 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.144.56.0/23 | APNIC | 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.