bgpreport

Network · data from 2026-11-12

AS149718 BINERI - SATUNOL

Registry name: BINERI-AS-ID - PT Satunol Digital Teknologi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149718, 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.
38.191.122.0/24 No ROA Nonecovered by 38.191.122.0/23 672 100% 67
38.191.123.0/24 No ROA Other IRR onlyRADB 673 100% 69
38.191.122.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.187.86.0/24 Valid Nonecovered by 103.187.86.0/23 673 100% 69
223.25.107.0/24 Valid None 672 100% 67
103.187.87.0/24 Valid Other IRR onlyRADB 673 100% 69
160.22.63.0/24 Valid Other IRR onlyRADB 673 100% 69
223.25.109.0/24 Valid Other IRR onlyRADB 672 100% 67
103.187.86.0/23 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS149718'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 13 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.191.122.0/24No ROA covers it. Add a ROA for AS149718, maxLength 24.672 of 673
Route object: none38.191.122.0/24No route object for it. A route object for 38.191.122.0/23 with origin AS149718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149718 in the RIR database for the space.672 of 673
ROA: none38.191.123.0/24No ROA covers it. Add a ROA for AS149718, maxLength 24.673 of 673
Route object: RIR38.191.123.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none38.191.122.0/23No ROA covers it. Add a ROA for AS149718, maxLength 23.2 of 673
Route object: RIR38.191.122.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none103.187.86.0/24No route object for it. A route object for 103.187.86.0/23 with origin AS149718 covers it (filters allowing more-specifics accept it). Add a route object with origin AS149718 in the RIR database for the space.673 of 673
Route object: none223.25.107.0/24No route object for it. Add a route object with origin AS149718 in the RIR database for the space.672 of 673
Route object: RIR103.187.87.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR160.22.63.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR223.25.109.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.187.86.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2001:df2:640::/48RADBNo 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.