bgpreport

Network · data from 2026-11-12

AS9462 BOLEH-NET-AP - BOLEHNET-ASN

Registry name: BOLEH-NET-AP - BOLEHNET-ASN, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9462, 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.10.32.0/23 Invalid: origin Other origin onlycovered by 202.10.32.0/22 2 0%low visibility 1

AS-SET

AS9462 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 22 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced20
ChangePrefix or setDetailFull-table peers
ROA: origin202.10.32.0/23ROAs covering it name AS137363, not AS9462. If AS9462 should announce it, add a ROA for AS9462.2 of 673
Route object: none202.10.32.0/23Route objects for it name AS137363. A route object for 202.10.32.0/22 with origin AS9462 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9462 in the RIR database for the space.2 of 673

Route objects not announced

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

202.10.32.0/19NTTCOM, RADBNo ROA
202.10.32.0/20NTTCOM, RADBNo ROA
202.10.32.0/21NTTCOM, RADBNo ROA
202.10.32.0/22NTTCOM, RADBNo ROA
202.10.36.0/22NTTCOMNo ROA
202.10.40.0/21NTTCOM, RADBNo ROA
202.10.40.0/22NTTCOM, RADBNo ROA
202.10.44.0/22NTTCOM, RADBNo ROA
202.10.48.0/20NTTCOM, RADBNo ROA
202.10.48.0/21NTTCOM, RADBNo ROA
202.10.48.0/22NTTCOM, RADBNo ROA
202.10.50.0/23NTTCOM, RADBNo ROA
202.10.52.0/22NTTCOM, RADBNo ROA
202.10.56.0/21NTTCOM, RADBNo ROA
202.10.56.0/22NTTCOM, RADBNo ROA
202.10.56.0/23NTTCOM, RADBNo ROA
202.10.58.0/23NTTCOM, RADBNo ROA
202.10.60.0/22NTTCOM, RADBNo ROA
202.10.60.0/23NTTCOM, RADBNo ROA
202.10.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.