Revenera incident

Intermittent Issues on FlexNet Operations ALM

Notice Resolved View vendor source →

Revenera experienced a notice incident on November 20, 2025 affecting FlexNet Operations ALM End User Portal NAM2 and FlexNet Operations ALM End User Portal UAT NAM1 and 1 more component, lasting 2d 8h. The incident has been resolved; the full update timeline is below.

Started
Nov 20, 2025, 09:18 AM UTC
Resolved
Nov 22, 2025, 05:32 PM UTC
Duration
2d 8h
Detected by Pingoru
Nov 20, 2025, 09:18 AM UTC

Affected components

FlexNet Operations ALM End User Portal NAM2FlexNet Operations ALM End User Portal UAT NAM1FlexNet Operations ALM End User Portal EU1FlexNet Operations ALM End User Portal UAT EU1FlexNet Operations ALM End User Portal UAT NAM4FlexNet Operations ALM End User Portal NAM7FlexNet Operations ALM Producer Portal NAM6FlexNet Operations ALM Producer Portal UAT NAM3FlexNet Operations ALM End User Portal UAT NAM2FlexNet Operations ALM End User Portal NAM3

Update timeline

  1. investigating Nov 20, 2025, 09:18 AM UTC

    We are currently experiencing intermittent disruptions impacting FlexNet Operations functionalities, resulting in 502 Bad Gateway errors. Our engineering teams are actively investigating this issue with the highest priority and will provide timely updates as progress is made.

  2. investigating Nov 20, 2025, 11:34 AM UTC

    We are continuing to investigate the cause of the issue and will keep you informed as we make progress toward full resolution.

  3. investigating Nov 20, 2025, 01:31 PM UTC

    We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.

  4. investigating Nov 20, 2025, 02:12 PM UTC

    We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.

  5. investigating Nov 20, 2025, 02:43 PM UTC

    We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.

  6. investigating Nov 20, 2025, 03:31 PM UTC

    We are continuing to investigate the underlying cause. We remain focused on achieving full resolution. We will provide further updates as soon as new details become available.

  7. identified Nov 20, 2025, 03:52 PM UTC

    We have identified the cause of the issue and a potential solution. We are working to deploy and validate the fix in the affected environments. We will update the status based on the results.

  8. investigating Nov 20, 2025, 07:48 PM UTC

    We’ve identified that the recent fix did not fully resolve the issue. Our team is actively investigating alternative solutions and will share updates as soon as possible. Thank you for your patience and understanding as we work to stabilize the affected environments.

  9. investigating Nov 21, 2025, 04:45 AM UTC

    Our team is diligently exploring alternative solutions and will provide updates as soon as they become available. We appreciate your patience and understanding as we work to stabilize the affected environments.

  10. investigating Nov 21, 2025, 07:28 AM UTC

    The intensity and duration of intermittent issues have been reducing significantly over time. We are working with our cloud vendor to identify the root cause.

  11. identified Nov 21, 2025, 09:36 AM UTC

    The issue has been identified and a fix is being implemented.

  12. monitoring Nov 21, 2025, 09:46 AM UTC

    A fix has been implemented and we are monitoring the results.

  13. monitoring Nov 21, 2025, 12:58 PM UTC

    The issue has been fixed, and we will continue monitoring for the next 24 hours.

  14. resolved Nov 22, 2025, 05:32 PM UTC

    This incident has been resolved.