Axway Outage History

This incident has been resolved.

We observed a brief period of degraded authentication service between 05:50 UTC and 06:50 UTC on 11 August 2026, during which a small number of users may have experienced login failures. The issue has been fully resolved, and services are operating normally. Additional monitoring and preventive measures have been put in place to help maintain service reliability. We regret any disruption this may have caused and appreciate your continued trust.

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.