Network · data from 2026-11-12
AS59261 TRIJITNET-DC-IN - TRIJIT TECHNOLOGIES PVT LTD
Registry name: TRIJITNET-DC-IN - TRIJIT TECHNOLOGIES PVT LTD, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59261, 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.
| 2404:5c80::/32 | No ROA | None | 631 99% |
| 2404:5c80:1::/48 | No ROA | None | 631 99% |
| 103.228.83.0/24 | No ROA | RIR databaseAPNIC | 670 100% |
AS-SET
AS59261 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 15 are in fix.csv.
- ROA: none3
- Route object: none2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2404:5c80::/32 | No ROA covers it. Add a ROA for AS59261, maxLength 32. |
| Route object: none | 2404:5c80::/32 | No route object for it. Add a route object with origin AS59261 in the RIR database for the space. |
| ROA: none | 2404:5c80:1::/48 | No ROA covers it. Add a ROA for AS59261, maxLength 48. |
| Route object: none | 2404:5c80:1::/48 | No route object for it. Add a route object with origin AS59261 in the RIR database for the space. |
| ROA: none | 103.228.83.0/24 | No ROA covers it. Add a ROA for AS59261, maxLength 24. |
Route objects not announced
Route objects with origin AS59261 whose prefix no peer sees AS59261 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2404:5c80:11::/48 | APNIC | No ROA |
| 2404:5c80:12::/48 | APNIC | No ROA |
| 2404:5c80:13::/48 | APNIC | No ROA |
| 2404:5c80:14::/48 | APNIC | No ROA |
| 2404:5c80:15::/48 | APNIC | No ROA |
| 2404:5c80:16::/48 | APNIC | No ROA |
| 2404:5c80:17::/48 | APNIC | No ROA |
| 2404:5c80:18::/48 | APNIC | No ROA |
| 2404:5c80:19::/48 | APNIC | No ROA |
| 2404:5c80:20::/48 | 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.