IBM webMethods iPaaS had 37 outages in the last 2 years totaling 221h 14m of downtime — averaging 1.5 incidents per month.
There were 37 IBM webMethods iPaaS outages since June 6, 2025 totaling 221h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Component status: major_outage
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Component status: major_outage
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating an incident affecting tenant access. Customers may experience 502 errors when attempting to access their tenants, impacting production transactions. This issue primarily affects webMethods.io Integration and API services. Our team is actively working to resolve this and will provide updates as they become available.
We are currently investigating the issue and will provide an update as soon as more information becomes available.
Our engineers are actively investigating this issue with AWS support, focusing on authentication challenges affecting service availability. We will provide updates as they become available.
Integration services are now healthy. Some API Gateway users may still experience intermittent issues. We are actively monitoring and working toward full resolution.
The issue has been identified and requires a code hotfix. The team is currently working on the fix, and it will be thoroughly tested before being deployed to production at the earliest.
The fix has been applied and we are currently monitoring the situation.
We are continuing to monitor for any further issues.
The fix has been released to Cloud environments, and customers need to apply it to take effect.
Component status: major_outage
Please refer https://status.webmethods.io/incidents/pdft0zhnsc9q for more updates.
A fix has been implemented and we are monitoring the results.
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Component status: major_outage
Component status: major_outage
Component status: major_outage
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The scheduled maintenance for Azure Database for MySQL Flexible Server on April 25, 2026, from 02:30 to 04:30 UTC has been cancelled. This decision was made due to capacity constraints on the underlying Azure cloud infrastructure, which prevent the upgrade from being performed safely during the planned window. There will be no impact to your services at this time. We are working closely with our cloud provider to secure the required capacity and will communicate a new maintenance schedule once confirmed. Thank you for your understanding
Marking the notification as closed since the upgrade has been canceled
Observing publish and design time issues, we are currently investigating the issue
We are continuing to investigate this issue.
The problem is resolved now.
We are currently investigating this issue.
This incident has been resolved.
The webmethods.io Integration Messaging functionality is impacting the processing of transactions as reported by multiple customers. The team is currently investigating, and further updates will be posted on the status page in a timely manner
The issue has been identified and fix is being applied. We are monitoring the platform.
The issue in the IBM webMethods Integration EU3 INT region has been resolved. All services are operating normally.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing intermittent service interruptions. Our team is actively investigating the issue and working to restore full functionality as quickly as possible. We will provide additional updates as soon as more information becomes available. Thank you for your patience and understanding.
We are still investigating the reported issue. At this time, our analysis indicates that the impact is limited to customers hosted in the West Europe (Netherlands) – Azure EU3 region. Other regions are not affected. Our engineering teams are actively working to identify the root cause and mitigate the issue as quickly as possible. We will provide further updates as more information becomes available.
The latest update is that the Azure Networking team is investigating the issue, and we are awaiting further updates from Azure.
The issue has been confirmed as an Azure networking problem. Services have been stabilizing over the past few minutes, and both we and Azure are actively monitoring the situation. Azure will share an official communication within the next two hours, and a Root Cause Analysis (RCA) will be provided for this incident.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Our third-party service provider implemented a fix which seems to resolve the issue. We will continue to monitor and provide updates as they become available.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.