bgpreport

Network · data from 2026-11-12

AS39804 VDAB Vlaamse Dienst voor Arbeidsbemiddelling en Beroepsopleiding

Registry name: VDAB Vlaamse Dienst voor Arbeidsbemiddelling en Beroepsopleiding, BE · not in 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
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS39804, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS39804, 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.
193.53.207.0/24 No ROA Nonecovered by 193.53.200.0/21 670 100% 67
193.53.218.0/23 No ROA None 670 100% 67
193.53.220.0/23 No ROA None 670 100% 67
193.53.216.0/24 Valid RIR databaseRIPE 671 100% 67
193.53.217.0/24 Valid RIR databaseRIPE 671 100% 67
193.53.224.0/23 Valid RIR databaseRIPE 671 100% 67
193.53.226.0/23 Valid RIR databaseRIPE 671 100% 67
193.53.235.0/24 Valid RIR databaseRIPE 671 100% 67
193.53.238.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS39804 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 16 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none193.53.207.0/24No ROA covers it. Add a ROA for AS39804, maxLength 24.670 of 673
Route object: none193.53.207.0/24No route object for it. A route object for 193.53.200.0/21 with origin AS39804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39804 in the RIR database for the space.670 of 673
ROA: none193.53.218.0/23No ROA covers it. Add a ROA for AS39804, maxLength 23.670 of 673
Route object: none193.53.218.0/23No route object for it. Add a route object with origin AS39804 in the RIR database for the space.670 of 673
ROA: none193.53.220.0/23No ROA covers it. Add a ROA for AS39804, maxLength 23.670 of 673
Route object: none193.53.220.0/23No route object for it. Add a route object with origin AS39804 in the RIR database for the space.670 of 673

Route objects not announced

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

193.53.200.0/21RIPENo ROA
193.53.212.0/24RIPENo ROA
193.53.213.0/24RIPENo ROA
193.53.218.0/24RIPENo ROA
193.53.219.0/24RIPENo ROA
193.53.220.0/24RIPENo ROA
193.53.236.0/24RIPENo ROA
193.53.237.0/24RIPENo ROA
193.53.238.199/32RIPEInvalid: maxLength
193.53.242.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.