Axway Outage History
Axway is up right nowPingoru has recorded 13 incidents for Axway: 5 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 2 | 1 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 510 (0%) |
Incidents, newest first
Critical August 18, 2026 Axway Login Issues 24m Platform Dashboard, Axway Community Portal, Platform Dashboard, Amplify Engage and 16 more
Started Aug 18, 2026, 07:40 PM UTC· resolved Aug 18, 2026, 08:05 PM UTC
- investigating Aug 18, 2026, 08:05 PM UTC
We observed a brief period of degraded authentication service starting 19:40 UTC on 18 August 2026, during which a number of users may have experienced login failures. We're currently investigating the issue.
- resolved Aug 18, 2026, 09:54 PM UTC
This incident has been resolved.
Minor August 11, 2026 Axway Platform Intermittent Login Issues 1h
Started Aug 11, 2026, 05:50 AM UTC· resolved Aug 11, 2026, 06:50 AM UTC
- resolved Aug 11, 2026, 12:02 PM UTC
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.
Minor May 11, 2026 Axway Platform Analytics intermittent query failure –
Started May 11, 2026, 02:00 PM UTC· resolved May 11, 2026, 02:00 PM UTC
- resolved May 11, 2026, 04:19 PM UTC
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.
Major February 19, 2026 Axway Platform Outage 1h
Started Feb 19, 2026, 01:00 PM UTC· resolved Feb 19, 2026, 02:00 PM UTC
- resolved Feb 19, 2026, 05:28 PM UTC
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.
Notice December 9, 2025 Amplify Studio outage - US & EU –
Started Dec 09, 2025, 06:30 AM UTC· resolved Dec 09, 2025, 06:30 AM UTC
- resolved Dec 12, 2025, 10:13 AM UTC
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.
Major May 7, 2025 Amplify Engage - Event Processing Outage in EU Production Environment 4h 32m Amplify Engage
Started May 07, 2025, 04:42 PM UTC· resolved May 07, 2025, 09:14 PM UTC
- investigating May 07, 2025, 04:42 PM UTC
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.
- investigating May 07, 2025, 04:43 PM UTC
We are continuing to investigate this issue.
- identified May 07, 2025, 08:43 PM UTC
The issue has been identified and a fix is being implemented.
- resolved May 07, 2025, 09:14 PM UTC
This incident has been resolved.
Notice February 21, 2025 Amplify Fusion EU - Outage –
Started Feb 21, 2025, 07:00 AM UTC· resolved Feb 21, 2025, 07:00 AM UTC
- resolved Feb 25, 2025, 09:10 AM UTC
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.
Notice February 5, 2025 Amplify Fusion EU and US - Outage 12h 20m
Started Feb 05, 2025, 09:00 PM UTC· resolved Feb 06, 2025, 09:20 AM UTC
- resolved Feb 11, 2025, 04:13 PM UTC
Date: February 5-6, 2024 (Start time after 22:00 UTC on February 5th; end time 09:20 UTC on February 6th) Impact: The Shared Data Plane experienced an outage, resulting in the interruption of transaction processing. Description: A thorough investigation of system logs revealed a disruption in network connectivity between nodes within the Hazelcast cluster. Hazelcast serves as the messaging layer between various components in our Orchestrator. The network disruption prevented communication between these critical components, halting message processing and consequently, transaction processing. Corrective Actions & Future Plans: A root cause analysis is underway to determine the specific cause of the network disruption within the Hazelcast cluster. Aside from this analysis, the team is planning to replace Hazelcast with an alternative messaging platform. Enhancements to the monitoring framework are implemented to proactively detect and alert on similar connectivity issues, enabling prompt intervention and minimizing service disruption.