Axway had 6 outages in the last 2 years totaling 4h 32m of downtime — averaging 0.2 incidents per month.
There were 6 Axway outages since February 11, 2025 totaling 4h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
Unbounded queries overwhelmed the analytics systems in use by Engage and Platform, causing delays in processing between 2PM-3PM UTC today. We will be working to improve query size and performance as well as introduce further restrictions to prevent this from causing issues in the future.
We’re sorry — between 13:00 UTC and 14:00 UTC today some customers experienced partial interruptions to Axway Platform, Axway Analytics, Amplify Marketplace, and Amplify Engage. During that window an internal service error caused elevated failures and automated retries, which temporarily prevented normal access for some users. We restored access by allowing queued requests to proceed while we validated and deployed a tested fix; normal service was confirmed at 14:00 UTC. No customer data was exposed. We’re taking steps to reduce the chance of this happening again, including additional safeguards, improved test coverage, and broader alerting so production issues are surfaced to our public status page and support teams more quickly. If you’re still seeing problems or need help, please contact support through your usual channels.
Description: During the detected outage on Amplify Studio, users experienced instability in activating integrations. Additionally, the receipt of monitoring data from Fusion was affected. Root Cause: The introduction of additional monitoring checks in the environments led to a permissions error on the clusters. This error disrupted connectivity between the Studio and Fusion instances. The standard validation routines prior to being deployed in production didn’t catch this permission mismatch. Corrective Action: The permissions were promptly reverted, and impacted services were verified. To prevent recurrence, we have implemented additional checks to ensure such changes do not affect production without being detected in lower environments first.
We are currently experiencing a major disruption in our EU production environment where event processing has stopped for the majority of services. This issue is impacting several critical functions, including but not limited to: - Product and asset releases (publish/unpublish) - Credential and access request processing - Subscription management - Agent and webhook event delivery Our engineering team is actively working to resolve the invalid event entries to resume normal processing. Once the blockers are cleared, queued and new events will begin processing as expected.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Date: Start Friday 21st - 08:02 AM End Friday 21st - 12:23 PM Impact: The Shared Data Plane experienced an outage, resulting in the interruption of transaction processing. Details: During the startup of new worker nodes two issues were discovered. The startup of the CNI plugin failed and was therefore not initialized. A CNI plugin is required to implement the Kubernetes network model. The second issue was due to the EFS plugin crashing with OOM. EFS is used for persistent storage. To resolve the issue, the memory was increased and unstable nodes were restarted. After these actions the Shared Data Plane returned to a stable state and the outage ended.