bgpreport

Network · data from 2026-11-12

AS133811 Inti Bangun Sejahtera

Registry name: IBST-AS-ID - PT Inti Bangun Sejahtera, tbk, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133811, 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.52.16.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 68
103.52.17.0/24 Valid Other IRR onlyRADB 673 100% 69
103.52.18.0/24 Valid Other IRR onlyRADB 673 100% 69
2406:ef40::/48 Valid Other IRR onlyRADB 1 0%low visibility 2
2406:ef40:1::/48 Valid Other IRR onlyRADB 1 0%low visibility 2
2406:ef40:2::/48 Valid Other IRR onlyRADB 1 0%low visibility 2
2406:ef40:5::/48 Valid Other IRR onlyRADB 1 0%low visibility 2
2406:ef40:6::/48 Valid Other IRR onlyRADB 1 0%low visibility 2
2406:ef40:8::/48 Valid Other IRR onlyRADB 1 0%low visibility 2

AS-SET

AS133811'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 14 are in fix.csv.

  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR103.52.16.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.52.17.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.52.18.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2406:ef40::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR2406:ef40:1::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR2406:ef40:2::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR2406:ef40:5::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR2406:ef40:6::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636
Route object: RIR2406:ef40:8::/48Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

103.52.16.0/23RADBValid
103.52.19.0/24NTTCOM, RADBValid
2406:ef40:3::/48RADBValid
2406:ef40:4::/48RADBValid
2406:ef40:7::/48RADBValid

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.