bgpreport

Network · data from 2026-11-12

AS29029 KNPC-AS Kuwait National Petroleum Company

Registry name: KNPC-AS Kuwait National Petroleum Company, KW · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29029, 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.
193.188.49.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.51.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.52.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.55.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.57.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.59.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.61.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.63.0/24 No ROA Other IRR onlyNTTCOM 673 100% 67
193.188.48.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.50.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.53.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.54.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.56.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.58.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.60.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
193.188.62.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
45.15.229.0/24 Valid RIR databaseRIPE 671 100% 67
45.15.231.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS29029 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 49 are in fix.csv.

  • ROA: none16
  • Route object: RIR16
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none193.188.49.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.49.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.51.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.51.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.52.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.52.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.55.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.55.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.57.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.57.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.59.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.59.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.61.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.61.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.63.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.673 of 673
Route object: RIR193.188.63.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none193.188.48.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.48.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.50.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.50.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.53.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.53.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.54.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.54.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.56.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.56.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.58.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.58.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.60.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.60.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none193.188.62.0/24No ROA covers it. Add a ROA for AS29029, maxLength 24.672 of 673
Route object: RIR193.188.62.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

45.15.228.0/24RIPEValid
45.15.230.0/24RIPEValid
193.188.48.0/20NTTCOM, RADBNo ROA
193.188.48.0/21NTTCOM, RADBNo ROA
193.188.48.0/22NTTCOM, RADBNo ROA
193.188.48.0/23NTTCOM, RADBNo ROA
193.188.50.0/23NTTCOM, RADBNo ROA
193.188.52.0/22NTTCOM, RADBNo ROA
193.188.52.0/23NTTCOM, RADBNo ROA
193.188.54.0/23NTTCOM, RADBNo ROA
193.188.56.0/21NTTCOM, RADBNo ROA
193.188.56.0/22NTTCOM, RADBNo ROA
193.188.56.0/23NTTCOM, RADBNo ROA
193.188.58.0/23NTTCOM, RADBNo ROA
193.188.60.0/22NTTCOM, RADBNo ROA
193.188.60.0/23NTTCOM, RADBNo ROA
193.188.62.0/23NTTCOM, RADBNo 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.