Network · data from 2026-11-12
AS56245 FAJAR-AS-ID - PT Fajar Techno System
Registry name: FAJAR-AS-ID - PT Fajar Techno System, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56245, 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.
| 45.121.40.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.121.41.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.121.42.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.121.43.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.10.80.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.10.81.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.61.118.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.61.119.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
AS56245 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 18 are in fix.csv.
- ROA: none4
- Route object: RIR8
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.121.40.0/24 | No ROA covers it. Add a ROA for AS56245, maxLength 24. |
| Route object: RIR | 45.121.40.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.121.41.0/24 | No ROA covers it. Add a ROA for AS56245, maxLength 24. |
| Route object: RIR | 45.121.41.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.121.42.0/24 | No ROA covers it. Add a ROA for AS56245, maxLength 24. |
| Route object: RIR | 45.121.42.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 45.121.43.0/24 | No ROA covers it. Add a ROA for AS56245, maxLength 24. |
| Route object: RIR | 45.121.43.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.10.80.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.10.81.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.61.118.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.61.119.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56245 whose prefix no peer sees AS56245 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.121.40.0/23 | RADB | No ROA |
| 45.121.42.0/23 | RADB | No ROA |
| 103.10.80.0/23 | RADB | No ROA |
| 103.225.184.0/23 | NTTCOM | No ROA |
| 103.225.184.0/24 | NTTCOM | No ROA |
| 103.225.185.0/24 | NTTCOM | 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.