Network · data from 2026-11-12
AS17450 PT Bank Central Asia
Registry name: IDNIC-BCA-ID - PT Bank Central Asia, Tbk, ID · PeeringDB
29IPv4 routes
100.0% RPKI valid · 82.8% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
5 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
18Route objects not announced
registered with origin AS17450, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS17450, 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.8.96.0/24 | Valid | Nonecovered by 103.8.96.0/22 | 673 100% |
| 103.8.97.0/24 | Valid | Nonecovered by 103.8.96.0/22 | 673 100% |
| 103.8.98.0/24 | Valid | Nonecovered by 103.8.96.0/22 | 673 100% |
| 103.8.99.0/24 | Valid | Nonecovered by 103.8.96.0/22 | 673 100% |
| 119.2.64.0/20 | Valid | None | 672 100% |
| 103.8.96.0/22 | Valid | Other IRR onlyRADB | 673 100% |
| 103.151.91.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 119.2.67.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 119.2.68.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 202.6.208.0/20 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.208.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.214.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.215.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.216.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.217.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.218.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.219.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.220.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.221.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.222.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.6.223.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 119.2.69.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 119.2.64.0/24 | Valid | Other IRR onlyRADB | 494 73% |
| 119.2.72.0/24 | Valid | Other IRR onlyRADB | 494 73% |
| 119.2.70.0/24 | Valid | Other IRR onlyRADB | 35 5%low visibility |
| 202.6.210.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.6.213.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 202.6.209.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
| 202.6.211.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 670 100% |
AS-SET
AS17450'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 43 are in fix.csv.
- Route object: none5
- Route object: RIR20
- Route object: not announced18
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.8.96.0/24 | No route object for it. A route object for 103.8.96.0/22 with origin AS17450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17450 in the RIR database for the space. |
| Route object: none | 103.8.97.0/24 | No route object for it. A route object for 103.8.96.0/22 with origin AS17450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17450 in the RIR database for the space. |
| Route object: none | 103.8.98.0/24 | No route object for it. A route object for 103.8.96.0/22 with origin AS17450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17450 in the RIR database for the space. |
| Route object: none | 103.8.99.0/24 | No route object for it. A route object for 103.8.96.0/22 with origin AS17450 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17450 in the RIR database for the space. |
| Route object: none | 119.2.64.0/20 | No route object for it. Add a route object with origin AS17450 in the RIR database for the space. |
| Route object: RIR | 103.8.96.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.151.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.67.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.68.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.208.0/20 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.208.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.214.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.215.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.216.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.217.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.218.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.219.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.220.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.221.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.222.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.6.223.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.69.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.64.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 119.2.70.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17450 whose prefix no peer sees AS17450 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 119.2.65.0/24 | RADB | Valid |
| 119.2.66.0/24 | RADB | Valid |
| 119.2.71.0/24 | RADB | Valid |
| 202.6.208.0/21 | NTTCOM, RADB | Valid |
| 202.6.208.0/22 | NTTCOM, RADB | Valid |
| 202.6.208.0/23 | NTTCOM, RADB | Valid |
| 202.6.210.0/23 | NTTCOM, RADB | Valid |
| 202.6.212.0/22 | NTTCOM, RADB | Valid |
| 202.6.212.0/23 | NTTCOM, RADB | Valid |
| 202.6.212.0/24 | APNIC, NTTCOM, RADB | Valid |
| 202.6.214.0/23 | NTTCOM, RADB | Valid |
| 202.6.216.0/21 | NTTCOM, RADB | Valid |
| 202.6.216.0/22 | NTTCOM, RADB | Valid |
| 202.6.216.0/23 | NTTCOM, RADB | Valid |
| 202.6.218.0/23 | NTTCOM, RADB | Valid |
| 202.6.220.0/22 | NTTCOM, RADB | Valid |
| 202.6.220.0/23 | NTTCOM, RADB | Valid |
| 202.6.222.0/23 | 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.