bgpreport

Network · data from 2026-11-12

AS150935 IDNIC-PONOROGO-ID - Dinas Komunikasi Informatika dan Statistik Kab. Ponorogo

Registry name: IDNIC-PONOROGO-ID - Dinas Komunikasi Informatika dan Statistik Kab. Ponorogo, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150935, 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.109.206.0/23 No ROA Other IRR onlyRADB 673 100% 69
103.109.207.0/24 Valid Nonecovered by 103.109.206.0/23 672 100% 69
103.109.206.0/24 Valid Other IRR onlyRADB 672 100% 69

AS-SET

AS150935 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none103.109.206.0/23No ROA covers it. Add a ROA for AS150935, maxLength 23.673 of 673
Route object: RIR103.109.206.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none103.109.207.0/24No route object for it. A route object for 103.109.206.0/23 with origin AS150935 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150935 in the RIR database for the space.672 of 673
Route object: RIR103.109.206.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS150935 is announced.

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.