bgpreport

Network · data from 2026-11-12

AS58377 Sentra Niaga Solusindo

Registry name: SENTRACOLO-AS-ID - Sentra Niaga Solusindo, PT., ID · PeeringDB

5IPv4 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
1Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS58377, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58377, 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.29.212.0/23 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
103.29.214.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 70
103.29.212.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 68
103.29.215.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 69
103.29.213.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 47 7%low visibility 31

AS-SET

AS58377'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 3 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR103.29.212.0/23Route 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 AS58377 whose prefix no peer sees AS58377 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.29.212.0/22NTTCOM, RADBValid
103.29.214.0/23NTTCOM, RADBValid

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.