bgpreport

Network · data from 2026-11-12

AS38523 SISNET-ID - PT. SRIWIJAYA INTERNET SERVICES

Registry name: SISNET-ID - PT. SRIWIJAYA INTERNET SERVICES, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38523, 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.
2401:2c40::/48 Valid Nonecovered by 2401:2c40::/32 636 100% 69
2401:2c40:1::/48 Valid Nonecovered by 2401:2c40::/32 636 100% 69
2401:2c40:2::/48 Valid Nonecovered by 2401:2c40::/32 636 100% 69
2401:2c40:3::/48 Valid Nonecovered by 2401:2c40::/32 636 100% 69
2401:2c40:4::/48 Valid Nonecovered by 2401:2c40::/32 636 100% 69
2401:2c40:5::/48 Valid Nonecovered by 2401:2c40::/32 636 100% 69
117.74.114.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
117.74.115.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
117.74.116.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
117.74.112.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
117.74.113.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
117.74.117.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69
117.74.118.0/24 Valid Other IRR onlyNTTCOM, RADB 672 100% 69

AS-SET

AS38523 isn't in PeeringDB, where networks name their 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 22 are in fix.csv.

  • Route object: none6
  • Route object: RIR7
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none2401:2c40::/48No route object for it. A route object for 2401:2c40::/32 with origin AS38523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38523 in the RIR database for the space.636 of 636
Route object: none2401:2c40:1::/48No route object for it. A route object for 2401:2c40::/32 with origin AS38523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38523 in the RIR database for the space.636 of 636
Route object: none2401:2c40:2::/48No route object for it. A route object for 2401:2c40::/32 with origin AS38523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38523 in the RIR database for the space.636 of 636
Route object: none2401:2c40:3::/48No route object for it. A route object for 2401:2c40::/32 with origin AS38523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38523 in the RIR database for the space.636 of 636
Route object: none2401:2c40:4::/48No route object for it. A route object for 2401:2c40::/32 with origin AS38523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38523 in the RIR database for the space.636 of 636
Route object: none2401:2c40:5::/48No route object for it. A route object for 2401:2c40::/32 with origin AS38523 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38523 in the RIR database for the space.636 of 636
Route object: RIR117.74.114.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR117.74.115.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR117.74.116.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR117.74.112.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.74.113.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.74.117.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR117.74.118.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

117.74.112.0/21NTTCOM, RADBNo ROA
117.74.112.0/22NTTCOMNo ROA
117.74.112.0/23NTTCOMNo ROA
117.74.114.0/23NTTCOMNo ROA
117.74.116.0/22NTTCOMNo ROA
117.74.116.0/23NTTCOMNo ROA
117.74.118.0/23NTTCOMNo ROA
117.74.119.0/24NTTCOM, RADBValid
2401:2c40::/32RADBNo 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.