bgpreport

Network · data from 2026-11-12

AS25504 Vautron Rechenzentrum AG

Registry name: CRONON-AS Vautron Rechenzentrum AG, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS25504, 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.
151.252.56.19/32 Invalid: maxLength Nonecovered by 151.252.48.0/20 3 0%low visibility 7
91.198.21.0/24 No ROA RIR databaseRIPE 673 100% 66
91.223.145.0/24 No ROA RIR databaseRIPE 673 100% 66
91.247.144.0/23 No ROA RIR databaseRIPE 673 100% 66
109.205.196.0/24 No ROA RIR databaseRIPE 673 100% 66
193.150.4.0/23 No ROA RIR databaseRIPE 673 100% 66
2a14:ea80::/48 No ROA RIR databaseRIPE 634 100% 67
46.151.160.0/21 Valid RIR databaseRIPE 673 100% 66
46.175.56.0/21 Valid RIR databaseRIPE 673 100% 66
83.243.56.0/21 Valid RIR databaseRIPE 673 100% 66
89.200.168.0/21 Valid RIR databaseRIPE 673 100% 66
91.223.141.0/24 Valid RIR databaseRIPE 673 100% 66
91.233.26.0/23 Valid RIR databaseRIPE 673 100% 66
94.102.208.0/20 Valid RIR databaseRIPE 673 100% 66
109.235.56.0/21 Valid RIR databaseRIPE 673 100% 66
151.252.48.0/20 Valid RIR databaseRIPE 673 100% 66
158.58.144.0/21 Valid RIR databaseRIPE 673 100% 66
185.90.232.0/22 Valid RIR databaseRIPE 673 100% 66
193.254.184.0/21 Valid RIR databaseRIPE 673 100% 66
2001:67c:2394::/48 Valid RIR databaseRIPE 636 100% 69
2a00:19e0::/29 Valid RIR databaseRIPE 635 100% 69
195.191.92.0/23 Valid RIR databaseRIPE 631 94% 65

AS-SET

AS25504's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: maxLength1
  • ROA: none6
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength151.252.56.19/32ROA 151.252.48.0/20 AS25504 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 151.252.56.19/32.3 of 673
Route object: none151.252.56.19/32No route object for it. A route object for 151.252.48.0/20 with origin AS25504 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS25504 in the RIR database for the space.3 of 673
ROA: none91.198.21.0/24No ROA covers it. Add a ROA for AS25504, maxLength 24.673 of 673
ROA: none91.223.145.0/24No ROA covers it. Add a ROA for AS25504, maxLength 24.673 of 673
ROA: none91.247.144.0/23No ROA covers it. Add a ROA for AS25504, maxLength 23.673 of 673
ROA: none109.205.196.0/24No ROA covers it. Add a ROA for AS25504, maxLength 24.673 of 673
ROA: none193.150.4.0/23No ROA covers it. Add a ROA for AS25504, maxLength 23.673 of 673
ROA: none2a14:ea80::/48No ROA covers it. Add a ROA for AS25504, maxLength 48.634 of 636

Route objects not announced

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

91.230.83.0/24RIPEInvalid: origin
195.191.92.0/24RIPEValid
195.191.93.0/24RIPEValid
2a00:19e0::/32RIPEValid

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.