Network · data from 2026-11-12
AS58378 BTIP-AS-ID - Balai Telekomunikasi dan Informatika Perdesaan
Registry name: BTIP-AS-ID - Balai Telekomunikasi dan Informatika Perdesaan, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58378, 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.138.54.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.138.55.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.138.56.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.138.57.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.169.116.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 103.161.72.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.161.73.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.161.116.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.161.117.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.29.171.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.83.26.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.83.27.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.83.28.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 203.83.29.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 124.109.23.0/24 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS58378 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 19 are in fix.csv.
- ROA: none5
- Route object: RIR9
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.138.54.0/24 | No ROA covers it. Add a ROA for AS58378, maxLength 24. |
| Route object: RIR | 103.138.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.138.55.0/24 | No ROA covers it. Add a ROA for AS58378, maxLength 24. |
| Route object: RIR | 103.138.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.138.56.0/24 | No ROA covers it. Add a ROA for AS58378, maxLength 24. |
| Route object: RIR | 103.138.56.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.138.57.0/24 | No ROA covers it. Add a ROA for AS58378, maxLength 24. |
| Route object: RIR | 103.138.57.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.169.116.0/24 | No ROA covers it. Add a ROA for AS58378, maxLength 24. |
| Route object: RIR | 103.169.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.161.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.161.73.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.161.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.161.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58378 whose prefix no peer sees AS58378 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.138.54.0/23 | RADB | No ROA |
| 103.138.56.0/23 | RADB | No ROA |
| 103.140.66.0/23 | RADB | No ROA |
| 203.83.26.0/23 | APNIC, RADB | Valid |
| 203.83.28.0/23 | APNIC, 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.