Network · data from 2026-11-12
AS135450 Berkah Solusi Teknologi Informasi
Registry name: IDNIC-BSTI-AS-ID - PT Berkah Solusi Teknologi Informasi, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135450, 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.65.237.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.77.106.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.77.107.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.65.236.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS135450'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 8 are in fix.csv.
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.65.237.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.106.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.77.107.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.65.236.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 AS135450 whose prefix no peer sees AS135450 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.65.236.0/22 | NTTCOM | No ROA |
| 103.65.236.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.65.238.0/23 | NTTCOM | No ROA |
| 103.77.106.0/23 | APNIC, NTTCOM, 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.