bgpreport

Network · data from 2026-11-12

AS38149 BakrieTelecom

Registry name: RATELINDONET-AS-ID - PT. Bakrie Telecom, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38149, 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.
150.129.188.0/22 Invalid: origin None 2 0%low visibility 2
103.3.212.0/24 Valid RIR databaseAPNIC, NTTCOM 625 93% 67
103.3.213.0/24 Valid RIR databaseAPNIC, NTTCOM 625 93% 67

AS-SET

AS38149'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 58 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced56
ChangePrefix or setDetailFull-table peers
ROA: origin150.129.188.0/22ROAs covering it name AS38750, not AS38149. If AS38149 should announce it, add a ROA for AS38149.2 of 673
Route object: none150.129.188.0/22No route object for it. Add a route object with origin AS38149 in the RIR database for the space.2 of 673

Route objects not announced

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

103.3.212.0/22APNIC, NTTCOMValid
103.3.214.0/24APNICInvalid: maxLength
103.3.215.0/24APNICInvalid: maxLength
103.29.120.0/22NTTCOMNo ROA
103.29.120.0/23NTTCOMNo ROA
103.29.120.0/24NTTCOMNo ROA
103.29.121.0/24NTTCOMNo ROA
103.29.122.0/23NTTCOMNo ROA
103.29.122.0/24NTTCOMNo ROA
103.29.123.0/24NTTCOMNo ROA
113.212.160.0/21REACHInvalid: origin
113.212.162.0/24REACHInvalid: origin
116.68.160.0/20REACHNo ROA
117.102.224.0/19REACHInvalid: origin
118.82.0.0/19REACHNo ROA
118.82.5.0/24REACHNo ROA
122.129.200.0/21REACHInvalid: origin
122.200.48.0/21REACHNo ROA
123.176.120.0/21REACHNo ROA
202.6.224.0/20REACHInvalid: origin
202.8.28.0/23REACHNo ROA
202.51.16.0/20REACHNo ROA
202.122.15.0/24REACHInvalid: origin
202.129.216.0/24REACHInvalid: origin
202.129.217.0/24REACHInvalid: origin
202.152.192.0/19NTTCOMNo ROA
202.152.192.0/20REACHInvalid: origin
202.152.192.0/22APNICInvalid: origin
202.152.192.0/24APNICInvalid: origin
202.152.193.0/24APNICInvalid: origin
202.152.194.0/24APNICInvalid: origin
202.152.195.0/24APNICInvalid: origin
202.152.196.0/22APNICInvalid: origin
202.152.196.0/24APNICInvalid: origin
202.152.197.0/24APNICInvalid: origin
202.152.198.0/24APNICInvalid: origin
202.152.199.0/24APNICInvalid: origin
202.152.200.0/22APNICInvalid: origin
202.152.200.0/24APNIC, REACHInvalid: origin
202.152.201.0/24APNICInvalid: origin
202.152.202.0/24APNICInvalid: origin
202.152.203.0/24APNIC, REACHInvalid: origin
202.152.204.0/22APNICInvalid: origin
202.152.204.0/24APNICInvalid: origin
202.152.205.0/24APNICInvalid: origin
202.152.206.0/24APNIC, REACHInvalid: origin
202.152.207.0/24APNICInvalid: origin
202.153.16.0/20REACHInvalid: origin
202.153.120.0/21REACHNo ROA
202.154.0.0/18REACHInvalid: origin
202.158.252.0/24REACHNo ROA
203.81.184.0/21REACHInvalid: origin
203.81.190.0/24REACHInvalid: origin
203.153.120.0/21REACHNo ROA
203.217.132.0/23REACHInvalid: origin
2407:f200::/32NTTCOMNo 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.