Network · data from 2026-11-12
AS133797 Rekajasa Akses
Registry name: ACSATA-AS-ID - PT Rekajasa Akses, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133797, 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.122.56.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 103.43.128.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 103.43.128.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.43.129.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.43.130.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.43.131.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 45.122.56.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.122.57.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.122.58.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.122.59.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
AS-SET
AS133797's PeeringDB record names no 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 7 are in fix.csv.
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.122.56.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.43.128.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133797 whose prefix no peer sees AS133797 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.122.56.0/23 | RADB | Valid |
| 45.122.58.0/23 | RADB | Valid |
| 103.43.128.0/23 | RADB | Valid |
| 103.43.130.0/23 | RADB | Valid |
| 2402:3480::/48 | RADB | 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.