bgpreport

Network · data from 2026-11-12

AS46032 Fastel Sarana Indonesia ISP GLOBENET

Registry name: CENTRIN-ID - PT Centrin Online Prima, ID · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
3Route objects not announced registered with origin AS46032, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS46032, 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.
118.151.223.0/24 Valid Other IRR onlyNTTCOM, RADB 10 1%low visibility 10
103.148.110.0/24 Valid RIR databaseAPNIC, RADB 10 1%low visibility 10
103.148.111.0/24 Valid RIR databaseAPNIC 10 1%low visibility 10
118.151.220.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 10 1%low visibility 10
118.151.221.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 10 1%low visibility 10
118.151.222.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 10 1%low visibility 10

AS-SET

AS46032'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 4 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: RIR118.151.223.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.10 of 673

Route objects not announced

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

118.151.220.0/22APNICInvalid: origin
202.72.192.0/20APNICNo ROA
2404:d340:8000::/33APNICNo 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.