Revenera incident

Intermittent Connectivity to FlexNet Operations Cloud EU servers

Critical Resolved View vendor source →

Revenera experienced a critical incident on March 17, 2025 affecting FlexNet Operations ALM End User Portal EU1 and FlexNet Operations ALM End User Portal UAT EU1 and 1 more component, lasting 1d 5h. The incident has been resolved; the full update timeline is below.

Started
Mar 17, 2025, 09:47 PM UTC
Resolved
Mar 19, 2025, 03:44 AM UTC
Duration
1d 5h
Detected by Pingoru
Mar 17, 2025, 09:47 PM UTC

Affected components

FlexNet Operations ALM End User Portal EU1FlexNet Operations ALM End User Portal UAT EU1FlexNet Operations ALM End User Portal UAT EU2FlexNet Operations ALM End User Portal EU2FlexNet Operations ALM Producer Portal EU1FlexNet Operations ALM Producer Portal UAT EU1FlexNet Operations ALM Producer Portal UAT EU2FlexNet Operations ALM Producer Portal EU2FlexNet Operations Cloud Device Activation Service EU1FlexNet Operations Cloud Device Activation Service UAT EU1

Update timeline

  1. investigating Mar 17, 2025, 09:47 PM UTC

    We are currently investigating intermittent connectivity to FlexNet Operations Cloud EU servers. This is affecting production EU1 and EU2 and UAT EU1. We will update as soon as we have more information available.

  2. investigating Mar 17, 2025, 09:56 PM UTC

    We are continuing to investigate the problem and also found FlexNet Operations EU2 UAT systems are also include. We will continue to update as information becomes available.

  3. investigating Mar 17, 2025, 09:57 PM UTC

    We are continuing to investigate this issue.

  4. investigating Mar 17, 2025, 10:28 PM UTC

    The problem has changed to an unscheduled outage for the FlexNet Operations Cloud EU servers. We are working with our service provider to troubleshoot and resolved the problem.

  5. monitoring Mar 17, 2025, 10:39 PM UTC

    We believe we have now resolved the problems with the FlexNet Operations EU systems. Both Production and UAT sites are now available and we are monitoring to ensure there is no recurrence of the problem.

  6. resolved Mar 19, 2025, 03:44 AM UTC

    This incident has been resolved.