IBM webMethods iPaaS had 35 outages in the last 2 years totaling 1621h 44m of downtime — averaging 1.4 incidents per month.
There were 35 IBM webMethods iPaaS outages since October 25, 2025 totaling 1621h 44m 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
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
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
We are in the process of migrating from Atlassian Statuspage to the IBM Client Communication Center (CCC). Starting June 28, 2026, https://status.webmethods.io/ will automatically redirect to CCC, and you will begin to see all alerts, incidents, and maintenance communications published in this new page. Please ensure you subscribe to CCC to avoid missing critical updates. For more information, visit the IBM Client Communication Center (https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-client-communications-center) overview. Further updates will be shared soon.
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
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.