bgpreport

Network · data from 2026-11-12

AS12942 NRB-AS Network Research Belgium S.A.

Registry name: NRB-AS Network Research Belgium S.A., BE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12942, 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.

217.117.32.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.34.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.37.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.38.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.39.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.50.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.56.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
217.117.63.0/24 No ROA RIR databaseRIPE 40 6%low visibility 24
2a02:7100::/32 No ROA RIR databaseRIPE 20 3%low visibility 15
217.117.32.0/19 No ROA RIR databaseRIPE 16 2%low visibility 12
217.117.32.0/20 No ROA RIR databaseRIPE 15 2%low visibility 11
217.117.48.0/20 No ROA RIR databaseRIPE 15 2%low visibility 11
217.117.36.0/24 No ROA RIR databaseRIPE 0 0%low visibility 1

AS-SET

AS12942 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: none13
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none217.117.32.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.34.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.37.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.38.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.39.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.50.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.56.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none217.117.63.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.40 of 673
ROA: none2a02:7100::/32No ROA covers it. Add a ROA for AS12942, maxLength 32.20 of 636
ROA: none217.117.32.0/19No ROA covers it. Add a ROA for AS12942, maxLength 19.16 of 673
ROA: none217.117.32.0/20No ROA covers it. Add a ROA for AS12942, maxLength 20.15 of 673
ROA: none217.117.48.0/20No ROA covers it. Add a ROA for AS12942, maxLength 20.15 of 673
ROA: none217.117.36.0/24No ROA covers it. Add a ROA for AS12942, maxLength 24.0 of 673

Route objects not announced

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

193.53.128.0/19RIPEInvalid: origin
217.117.33.0/24RIPENo ROA
217.117.35.0/24RIPENo ROA
217.117.40.0/21RIPENo ROA
217.117.40.0/24RIPENo ROA
217.117.41.0/24RIPENo ROA
217.117.43.0/24RIPENo ROA
217.117.44.0/24RIPENo ROA
217.117.60.0/24RIPENo 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.