bgpreport

Network · data from 2026-11-12

AS24528 KTPNET

Registry name: KTP-AS-ID - PT. Khasanah Teknologi Persada, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24528, 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.
202.91.26.0/24 Invalid: origin Nonecovered by 202.91.26.0/23 2 0%low visibility 2
202.91.27.0/24 Invalid: origin Nonecovered by 202.91.26.0/23 2 0%low visibility 2

AS-SET

AS24528'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 37 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: origin202.91.26.0/24ROAs covering it name AS45306, not AS24528. If AS24528 should announce it, add a ROA for AS24528.2 of 673
Route object: none202.91.26.0/24No route object for it. A route object for 202.91.26.0/23 with origin AS24528 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24528 in the RIR database for the space.2 of 673
ROA: origin202.91.27.0/24ROAs covering it name AS45306, not AS24528. If AS24528 should announce it, add a ROA for AS24528.2 of 673
Route object: none202.91.27.0/24No route object for it. A route object for 202.91.26.0/23 with origin AS24528 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24528 in the RIR database for the space.2 of 673

Route objects not announced

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

119.15.128.0/21NTTCOMNo ROA
119.15.128.0/22NTTCOMNo ROA
119.15.128.0/23NTTCOMNo ROA
119.15.130.0/23NTTCOMNo ROA
119.15.132.0/22NTTCOMNo ROA
119.15.132.0/23NTTCOMNo ROA
119.15.134.0/23NTTCOMNo ROA
202.91.24.0/21APNIC, NTTCOM, RADBNo ROA
202.91.24.0/22NTTCOM, RADBNo ROA
202.91.24.0/23NTTCOMNo ROA
202.91.24.0/24NTTCOM, RADBValid
202.91.25.0/24NTTCOM, RADBValid
202.91.26.0/23NTTCOMNo ROA
202.91.28.0/22NTTCOMNo ROA
202.91.28.0/23NTTCOMNo ROA
202.91.28.0/24NTTCOM, RADBValid
202.91.29.0/24NTTCOM, RADBValid
202.91.30.0/23NTTCOMNo ROA
202.93.128.0/20NTTCOMNo ROA
202.93.128.0/21NTTCOMNo ROA
202.93.128.0/22NTTCOMNo ROA
202.93.128.0/23NTTCOMNo ROA
202.93.130.0/23NTTCOMNo ROA
202.93.132.0/22NTTCOMNo ROA
202.93.132.0/23NTTCOMNo ROA
202.93.134.0/23NTTCOMNo ROA
202.93.136.0/21NTTCOMNo ROA
202.93.136.0/22NTTCOMNo ROA
202.93.136.0/23NTTCOMNo ROA
202.93.138.0/23NTTCOMNo ROA
202.93.140.0/22NTTCOMNo ROA
202.93.140.0/23NTTCOMNo ROA
202.93.142.0/23NTTCOMNo 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.