bgpreport

Network · data from 2026-11-12

AS24526 BINUS - Bina Nusantara University

Registry name: BINUS - Bina Nusantara University, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24526, 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.58.161.0/24 Valid Other IRR onlyNTTCOM 673 100% 68
202.58.163.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.166.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.58.170.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.58.171.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.172.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.173.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.58.174.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.177.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.58.178.0/24 Valid Other IRR onlyNTTCOM 673 100% 68
202.58.179.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.180.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.58.181.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.182.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
202.58.183.0/24 Valid Other IRR onlyNTTCOM 673 100% 69

AS-SET

AS24526 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 60 are in fix.csv.

  • Route object: RIR15
  • Route object: not announced45
ChangePrefix or setDetailFull-table peers
Route object: RIR202.58.161.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.163.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.166.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.170.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.171.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.172.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.173.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.174.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.177.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.178.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.179.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.180.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.181.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.182.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.58.183.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 AS24526 whose prefix no peer sees AS24526 announce. Many are kept on purpose (backup routes, space announced only in some places).

202.58.160.0/19NTTCOMNo ROA
202.58.160.0/20APNIC, NTTCOM, RADBValid
202.58.160.0/21NTTCOM, RADBValid
202.58.160.0/22NTTCOM, RADBValid
202.58.160.0/23NTTCOMValid
202.58.160.0/24NTTCOM, RADBValid
202.58.162.0/23NTTCOMValid
202.58.162.0/24NTTCOMValid
202.58.164.0/22NTTCOMValid
202.58.164.0/23NTTCOMValid
202.58.164.0/24NTTCOMValid
202.58.165.0/24NTTCOMValid
202.58.166.0/23NTTCOMValid
202.58.167.0/24NTTCOMValid
202.58.168.0/21NTTCOMValid
202.58.168.0/22NTTCOMValid
202.58.168.0/23NTTCOMValid
202.58.168.0/24NTTCOMValid
202.58.169.0/24NTTCOMValid
202.58.170.0/23NTTCOMValid
202.58.172.0/22NTTCOMValid
202.58.172.0/23NTTCOMValid
202.58.174.0/23NTTCOMValid
202.58.175.0/24NTTCOMValid
202.58.176.0/20NTTCOMNo ROA
202.58.176.0/21APNIC, NTTCOM, RADBValid
202.58.176.0/24NTTCOM, RADBValid
202.58.184.0/21NTTCOMNo ROA
202.58.184.0/22NTTCOMNo ROA
202.58.184.0/23NTTCOMNo ROA
202.58.184.0/24NTTCOMNo ROA
202.58.185.0/24NTTCOMNo ROA
202.58.186.0/23NTTCOMNo ROA
202.58.186.0/24NTTCOMNo ROA
202.58.187.0/24NTTCOMNo ROA
202.58.188.0/22NTTCOMNo ROA
202.58.188.0/23NTTCOMNo ROA
202.58.188.0/24NTTCOMNo ROA
202.58.189.0/24NTTCOMNo ROA
202.58.190.0/23NTTCOMNo ROA
202.58.190.0/24NTTCOMNo ROA
202.58.191.0/24NTTCOMNo ROA
202.93.128.0/20NTTCOMNo ROA
2402:da00::/32RADBValid
2404:da00::/32RADBNo 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.