bgpreport

Network · data from 2026-11-12

AS204296 VEKA VEKA AG

Registry name: VEKA VEKA AG, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204296, 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.
2001:67c:2018::/48 No ROA RIR databaseRIPE 635 100% 68
185.254.60.0/23 Valid RIR databaseRIPE 673 100% 66
185.254.62.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
2a0c:4840::/29 Valid RIR databaseRIPE 634 100% 68

AS-SET

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

  • ROA: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:2018::/48No ROA covers it. Add a ROA for AS204296, maxLength 48.635 of 636

Route objects not announced

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

185.254.60.0/22RIPENo ROA
185.254.60.0/24RIPEValid
185.254.61.0/24RIPEValid
185.254.63.0/24RIPEValid
2001:67c:2018::48/128RIPENo ROA
2a0c:4847:ffff::/48RIPEValid

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.