IBM webMethods iPaaS incident

Intermittent failures are observed in the API Gateway components in AWS EU2 (Frankfurt).

Minor Resolved View vendor source →

IBM webMethods iPaaS experienced a minor incident on May 21, 2026 affecting EU2 INT and EU2 APIGW K8, lasting 4d 22h. The incident has been resolved; the full update timeline is below.

Started
May 21, 2026, 07:02 AM UTC
Resolved
May 26, 2026, 05:05 AM UTC
Duration
4d 22h
Detected by Pingoru
May 21, 2026, 07:02 AM UTC

Affected components

EU2 INTEU2 APIGW K8

Update timeline

  1. investigating May 21, 2026, 07:02 AM UTC

    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.

  2. investigating May 21, 2026, 09:41 AM UTC

    We are currently investigating the issue and will provide an update as soon as more information becomes available.

  3. investigating May 21, 2026, 10:35 AM UTC

    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.

  4. identified May 21, 2026, 11:54 AM UTC

    Integration services are now healthy. Some API Gateway users may still experience intermittent issues. We are actively monitoring and working toward full resolution.

  5. identified May 21, 2026, 01:20 PM UTC

    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.

  6. monitoring May 21, 2026, 02:36 PM UTC

    The fix has been applied and we are currently monitoring the situation.

  7. monitoring May 26, 2026, 04:23 AM UTC

    We are continuing to monitor for any further issues.

  8. resolved May 26, 2026, 05:05 AM UTC

    The fix has been released to Cloud environments, and customers need to apply it to take effect.