bgpreport

Network · data from 2026-11-12

AS204591 AZCUSTOMERS AMALYZE AG

Registry name: AZCUSTOMERS AMALYZE AG, DE · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
2Route objects not announced registered with origin AS204591, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS204591, 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.
185.242.196.0/22 No ROA RIR databaseRIPE 671 100% 66

AS-SET

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

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none185.242.196.0/22No ROA covers it. Add a ROA for AS204591, maxLength 22.671 of 673

Route objects not announced

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

193.22.232.0/22RIPEValid
2a0d:6d80::/29RIPENo 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.