bgpreport

Network · data from 2026-11-12

AS56252 Kreatif Pasific

Registry name: INAP-AS-ID - PT. Kreatif Pasific, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56252, 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.4.243.0/24 No ROA Other IRR onlyNTTCOM 673 100% 68

AS-SET

AS56252'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 31 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none103.4.243.0/24No ROA covers it. Add a ROA for AS56252, maxLength 24.673 of 673
Route object: RIR103.4.243.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

103.4.240.0/22APNIC, NTTCOM, RADBNo ROA
103.4.240.0/23NTTCOMNo ROA
103.4.241.0/24NTTCOMNo ROA
103.4.242.0/23NTTCOMNo ROA
103.4.242.0/24NTTCOMNo ROA
103.9.183.0/24NTTCOMNo ROA
103.30.84.0/22NTTCOMNo ROA
103.30.84.0/23NTTCOMNo ROA
103.30.84.0/24NTTCOMNo ROA
103.30.85.0/24NTTCOMNo ROA
103.30.86.0/23NTTCOMNo ROA
103.30.86.0/24NTTCOMNo ROA
103.30.87.0/24NTTCOMNo ROA
103.30.88.0/22NTTCOMNo ROA
103.30.88.0/23NTTCOMNo ROA
103.30.88.0/24NTTCOMNo ROA
103.30.89.0/24NTTCOMNo ROA
103.30.90.0/23NTTCOMNo ROA
103.30.90.0/24NTTCOMNo ROA
103.30.91.0/24NTTCOMNo ROA
103.30.92.0/22NTTCOMNo ROA
103.30.92.0/23NTTCOMNo ROA
103.30.92.0/24NTTCOMNo ROA
103.30.93.0/24NTTCOMNo ROA
103.30.94.0/23NTTCOMNo ROA
103.30.94.0/24NTTCOMNo ROA
103.30.95.0/24NTTCOMNo ROA
203.201.48.0/22NTTCOMNo ROA
203.201.48.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.