bgpreport

Network · data from 2026-11-12

AS38144 JALAWAVE-AS-ID - PT Jalawave Cakrawala

Registry name: JALAWAVE-AS-ID - PT Jalawave Cakrawala, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38144, 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.
60.253.106.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 69
60.253.96.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.97.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.99.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.100.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.101.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.102.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.103.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.104.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.105.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.107.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.108.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.109.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.110.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.111.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.112.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.113.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.114.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.115.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.116.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.117.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.118.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.119.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.121.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.122.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.123.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.124.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.125.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.224.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.225.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.226.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.227.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.228.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.230.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.232.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.233.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.234.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.235.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.236.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.237.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
202.51.238.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 69
60.253.98.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
60.253.126.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
202.51.239.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
60.253.127.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 3 0%low visibility 4
202.51.229.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 3 0%low visibility 4
202.51.231.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 3 0%low visibility 4

AS-SET

AS38144 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 48 are in fix.csv.

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

60.253.96.0/19NTTCOM, RADBValid
60.253.96.0/20NTTCOM, RADBValid
60.253.96.0/21NTTCOM, RADBValid
60.253.96.0/22NTTCOM, RADBValid
60.253.96.0/23NTTCOM, RADBValid
60.253.98.0/23NTTCOM, RADBValid
60.253.100.0/22NTTCOM, RADBValid
60.253.100.0/23NTTCOM, RADBValid
60.253.102.0/23NTTCOM, RADBValid
60.253.104.0/21NTTCOM, RADBValid
60.253.104.0/22NTTCOM, RADBValid
60.253.104.0/23NTTCOM, RADBValid
60.253.106.0/23NTTCOM, RADBValid
60.253.108.0/22NTTCOM, RADBValid
60.253.108.0/23NTTCOM, RADBValid
60.253.110.0/23NTTCOM, RADBValid
60.253.112.0/20NTTCOM, RADBValid
60.253.112.0/21NTTCOM, RADBValid
60.253.112.0/22NTTCOM, RADBValid
60.253.112.0/23NTTCOM, RADBValid
60.253.114.0/23NTTCOM, RADBValid
60.253.116.0/22NTTCOM, RADBValid
60.253.116.0/23NTTCOM, RADBValid
60.253.118.0/23NTTCOM, RADBValid
60.253.120.0/21NTTCOM, RADBValid
60.253.120.0/22NTTCOM, RADBValid
60.253.120.0/23NTTCOM, RADBValid
60.253.120.0/24APNIC, NTTCOM, RADBValid
60.253.122.0/23NTTCOM, RADBValid
60.253.124.0/22NTTCOM, RADBValid
60.253.124.0/23NTTCOM, RADBValid
60.253.126.0/23NTTCOM, RADBValid
202.51.224.0/20NTTCOM, RADBValid
202.51.224.0/21NTTCOM, RADBValid
202.51.224.0/22NTTCOM, RADBValid
202.51.224.0/23NTTCOM, RADBValid
202.51.226.0/23NTTCOM, RADBValid
202.51.228.0/22NTTCOM, RADBValid
202.51.228.0/23NTTCOM, RADBValid
202.51.230.0/23NTTCOM, RADBValid
202.51.232.0/21NTTCOM, RADBValid
202.51.232.0/22NTTCOM, RADBValid
202.51.232.0/23NTTCOM, RADBValid
202.51.234.0/23NTTCOM, RADBValid
202.51.236.0/22NTTCOM, RADBValid
202.51.236.0/23NTTCOM, RADBValid
202.51.238.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.