bgpreport

Network · data from 2026-11-12

AS209549 provide Kreuze Managed Solutions BV

Registry name: provide Kreuze Managed Solutions BV, NL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS209549, 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.
5.180.125.0/24 No ROA RIR databaseRIPE 673 100% 67
185.149.36.0/24 Valid Nonecovered by 185.149.36.0/23 673 100% 67
185.149.37.0/24 Valid Nonecovered by 185.149.36.0/23 673 100% 67
185.149.38.0/24 Valid Nonecovered by 185.149.38.0/23 673 100% 67
5.180.124.0/24 Valid RIR databaseRIPE 673 100% 67
185.149.36.0/22 Valid RIR databaseRIPE 673 100% 67
2a0d:b780::/29 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS209549 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 6 are in fix.csv.

  • ROA: none1
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none5.180.125.0/24No ROA covers it. Add a ROA for AS209549, maxLength 24.673 of 673
Route object: none185.149.36.0/24No route object for it. A route object for 185.149.36.0/23 with origin AS209549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209549 in the RIR database for the space.673 of 673
Route object: none185.149.37.0/24No route object for it. A route object for 185.149.36.0/23 with origin AS209549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209549 in the RIR database for the space.673 of 673
Route object: none185.149.38.0/24No route object for it. A route object for 185.149.38.0/23 with origin AS209549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209549 in the RIR database for the space.673 of 673

Route objects not announced

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

185.149.36.0/23RIPEInvalid: maxLength
185.149.38.0/23RIPEInvalid: maxLength

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.