bgpreport

Network · data from 2026-11-12

AS38769 Bit Technology Nusantara

Registry name: BITEK-AS-ID - PT. Bit Technology Nusantara, ID · PeeringDB

13IPv4 routes 100.0% RPKI valid · 92.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS38769, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38769, 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.
43.230.28.0/24 Valid Nonecovered by 43.230.28.0/22 673 100% 69
43.230.29.0/24 Valid Other IRR onlyRADB 673 100% 69
103.17.52.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.17.53.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.17.54.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.17.55.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
114.110.16.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
114.110.17.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
114.110.18.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
114.110.19.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
114.110.21.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
114.110.22.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69
114.110.23.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 69

AS-SET

AS38769'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 19 are in fix.csv.

  • Route object: none1
  • Route object: RIR5
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
Route object: none43.230.28.0/24No route object for it. A route object for 43.230.28.0/22 with origin AS38769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38769 in the RIR database for the space.673 of 673
Route object: RIR43.230.29.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.17.52.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.17.53.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.17.54.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.17.55.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS38769 whose prefix no peer sees AS38769 announce. Many are kept on purpose (backup routes, space announced only in some places).

43.230.28.0/22APNICNo ROA
43.241.148.0/22APNICValid
103.17.52.0/22NTTCOM, RADBNo ROA
103.17.52.0/23NTTCOM, RADBNo ROA
103.17.54.0/23NTTCOMNo ROA
114.110.16.0/21NTTCOMNo ROA
114.110.16.0/22NTTCOMNo ROA
114.110.16.0/23NTTCOMNo ROA
114.110.18.0/23NTTCOMNo ROA
114.110.20.0/22NTTCOMNo ROA
114.110.20.0/23NTTCOMNo ROA
114.110.20.0/24APNIC, NTTCOMNo ROA
114.110.22.0/23NTTCOMNo 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.