Revenera Outage History

Started Nov 27, 2025, 01:42 AM UTC· resolved Nov 27, 2025, 02:57 AM UTC

1. investigating Nov 27, 2025, 01:42 AM UTC

   The FlexNet Operations Data Access API service are currently unavailable. We are investigating the problem and working to restore the service.

2. investigating Nov 27, 2025, 01:56 AM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 27, 2025, 01:59 AM UTC

   We have identified a fix and restored the Data Access API service. We are monitoring the service to ensure it remains available.

4. resolved Nov 27, 2025, 02:57 AM UTC

   Our monitoring has not found any problems and the FlexNet Operations Data access APIs are working normally. We consider the issue resolved.

Read the full incident report →

Started Nov 20, 2025, 09:18 AM UTC· resolved Nov 22, 2025, 05:32 PM UTC

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.

Read the full incident report →

Started Nov 13, 2025, 04:39 PM UTC· resolved Nov 14, 2025, 10:09 PM UTC

1. investigating Nov 13, 2025, 04:39 PM UTC

   We are currently experiencing an issue with the FlexNet Operations Cloud ALM application in the Production NAM2 environment. The problem is preventing the List Entitlements page from loading in the FlexNet Operations ALM Producer Portal. Our teams are diligently working to restore full functionality as quickly as possible. We will continue to share status updates as new information becomes available.

2. identified Nov 13, 2025, 07:49 PM UTC

   Our team has 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.

3. identified Nov 14, 2025, 06:37 AM UTC

   We are continuing to work on a fix for this issue.

4. identified Nov 14, 2025, 05:00 PM UTC

   We are addressing this issue with the highest priority. We appreciate your continued patience and will share further updates as soon as we have more information.

5. monitoring Nov 14, 2025, 07:50 PM UTC

   A fix has been implemented and initial results indicate that the issue has been addressed. We are actively monitoring the system to confirm that functionality is operating as expected.

6. resolved Nov 14, 2025, 10:09 PM UTC

   Since the previous update, the system has operated without further issues. We are closing this incident as resolved.

Read the full incident report →

Started Nov 13, 2025, 01:58 AM UTC· resolved Nov 13, 2025, 04:46 AM UTC

1. investigating Nov 13, 2025, 01:58 AM UTC

   We are experiencing issues with the FlexNet Operations Cloud ALM application in the NAM region Our teams are diligently working to restore full functionality as quickly as possible. We will continue to share status updates as new information becomes available.

2. investigating Nov 13, 2025, 02:35 AM UTC

   We are continuing to investigate this issue.

3. identified Nov 13, 2025, 02:41 AM UTC

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

4. monitoring Nov 13, 2025, 02:44 AM UTC

   A fix has been implemented, and we’ve verified the service is fully restored. We will continue to monitor the service to ensure ongoing stability.

5. resolved Nov 13, 2025, 04:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 07, 2025, 02:23 AM UTC· resolved Nov 10, 2025, 05:36 AM UTC

1. investigating Nov 07, 2025, 02:23 AM UTC

   We are investigating an issue with sending email from FlexNet Operations ALM Production. We will update once the cause of the problem has been identified.

2. investigating Nov 07, 2025, 02:34 AM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 07, 2025, 02:36 AM UTC

   We performed a fix to the problem with email not sending from FlexNet Operations ALM and our test show email is now sending. We are monitoring to make sure no further errors occur.

4. resolved Nov 10, 2025, 05:36 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 05, 2025, 01:56 PM UTC· resolved Nov 06, 2025, 12:05 PM UTC

1. investigating Nov 05, 2025, 01:56 PM UTC

   FlexNet Operations ALM/LLM Software Delivery (ESD) is experiencing degraded performance which is delaying uploaded file availability. We are actively working to resolve the issue and will provide updates as more information is available.

2. investigating Nov 05, 2025, 03:03 PM 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 05, 2025, 03:39 PM UTC

   As we continue to investigate the issue, we've observed a degradation in performance that is resulting in email delivery delays for the following services: -FlexNet Operations LLM -Software Delivery (ESD) update notifications in FlexNet Operations ALM Our teams are actively working to restore full functionality as quickly as possible. We will continue to share status updates as new information becomes available. We appreciate your patience and apologize for any inconvenience this may cause.

4. identified Nov 05, 2025, 04:42 PM UTC

   Our team has identified the cause of the issue and is actively working with our service provider to implement a solution. We will update the status based on the results.

5. identified Nov 05, 2025, 05:49 PM UTC

   Our team has identified the cause of the issue and the potential solution. We are working to deploy and validate the fix in the affected environments. We will update the status based on the results. NOTE: This issue has been extended to include UAT and Production Copy Service (PCS) environments. We've removed the Device Activation Service and Cloud Licensing Service from the list of affected components. Those services continue to remain operational.

6. investigating Nov 05, 2025, 07:25 PM UTC

   Please note that the proposed fix did not resolve the ongoing issue. As a result, our team has escalated the matter to the service provider for further investigation and support in identifying a solution. We will provide additional updates as soon as more information becomes available. Thank you for your continued patience and understanding.

7. investigating Nov 05, 2025, 09:57 PM UTC

   Our team has implemented a fix to address the file synchronization delays impacting Software Delivery (ESD). While this issue has been mitigated, we are continuing to work closely with our service provider to resolve the ongoing email delivery problems affecting all FlexNet Operations LLM emails and FlexNet Operations ALM Software Delivery (ESD) update notifications. We will provide additional updates as soon as more information becomes available.

8. identified Nov 06, 2025, 08:05 AM UTC

   The team is actively working toward a permanent resolution. In the meantime, LLM API functionality may continue to experience disruptions. This issue is being addressed with utmost priority, and we will provide updates as they become available.

9. identified Nov 06, 2025, 09:57 AM UTC

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

10. monitoring Nov 06, 2025, 10:31 AM UTC

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

11. monitoring Nov 06, 2025, 11:11 AM UTC

    We are continuing to monitor for any further issues.

12. resolved Nov 06, 2025, 12:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Oct 14, 2025, 06:18 PM UTC· resolved Oct 15, 2025, 12:16 AM UTC

1. investigating Oct 14, 2025, 06:18 PM UTC

   We are experiencing issues with the FlexNet Operations Cloud LLM application in the UAT environment in the NAM region. Our teams are diligently working to restore full functionality as quickly as possible. We will continue to share status updates as new information becomes available.

2. investigating Oct 14, 2025, 06:41 PM UTC

   The issues are also being observed in the FlexNet Operations Cloud LLM application running in Production Copy Service (PCS) environments.

3. identified Oct 14, 2025, 06:56 PM UTC

   Our team has identified the cause of the issue and the potential solution for the FlexNet Operations LLM UAT environment. We are continuing our investigation in identifying and restoring services in the FlexNet Operations LLM Production Copy Service (PCS) environment.

4. monitoring Oct 14, 2025, 08:11 PM UTC

   We've identified and implemented a fix in FlexNet Operations LLM PCS environments and services have been restored. We are continuing to monitor our systems to ensure no further issues occur.

5. resolved Oct 15, 2025, 12:16 AM UTC

   Our monitoring shows the FlexNet Operations LLM application in UAT and PCS environments continues to operate as expected. We are marking this incident as resolved.

Read the full incident report →

Started Oct 14, 2025, 12:06 PM UTC· resolved Oct 15, 2025, 04:26 AM UTC

1. investigating Oct 14, 2025, 12:06 PM UTC

   We are experiencing database errors in ALM Reporter, we are working to resolve this issue. Please subscribe to this message, we will keep updating the progress. Impact - The Prod ALM SAP BO Reporter database will be temporarily unavailable until the issues are fully addressed. Please note that this will impact the ALM SAP BO Reporter, which may be inaccessible during this period.

2. investigating Oct 14, 2025, 12:34 PM UTC

   We are continuing to investigate this issue.

3. identified Oct 14, 2025, 01:20 PM UTC

   We’ve identified the root cause of the issue, and our teams are actively working on a resolution. We’ll continue to share updates as more information becomes available. Thank you for your patience and understanding.

4. identified Oct 14, 2025, 02:15 PM UTC

   We are working on deploying the fix to the environment. We will update the status based on the results.

5. identified Oct 14, 2025, 03:56 PM UTC

   Current Status: We investigated an issue impacting access to the Reporter application within FlexNet Operations ALM due to an underlying database server problem. Our team is actively working with our vendor to restore the affected database. What’s Happening: The database supporting our reporting service experienced an unexpected failure. A repair process is underway to restore full functionality. Because of the database’s large size, recovery is taking longer than usual, but progress remains steady at approximately 10% per hour. Thank you for your patience as we work to fully restore service.

6. monitoring Oct 14, 2025, 09:07 PM UTC

   Reporter for FlexNet Operations ALM is now functional and reports are loading. We've changed the status of this incident to monitoring as we ensure continued stability of the Reporter application.

7. resolved Oct 15, 2025, 04:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 14, 2025, 05:13 AM UTC· resolved Oct 14, 2025, 09:25 AM UTC

1. investigating Oct 14, 2025, 05:13 AM UTC

   Partial System Outage on FlexNet Operations LLM PCS NAM, Our teams are actively investigating the issue and working to restore full functionality as quickly as possible. Thank you for your patience.

2. monitoring Oct 14, 2025, 07:43 AM UTC

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

3. monitoring Oct 14, 2025, 07:49 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 14, 2025, 09:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 29, 2025, 11:34 AM UTC· resolved Sep 29, 2025, 04:53 PM UTC

1. investigating Sep 29, 2025, 11:34 AM UTC

   We are currently experiencing issues with the FlexNet Operations ALM/LLM Cloud Device Activation Service in the following Production environments: NAM2. Our teams are actively investigating the issue and working to restore full functionality as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience.

2. investigating Sep 29, 2025, 12:30 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 29, 2025, 12:49 PM UTC

   We have identified the cause of the performance degradation. Our teams are working on a fix. We will provide updates as more information becomes available. Thank you for your patience.

4. identified Sep 29, 2025, 01:58 PM UTC

   Testing potential remediation for Performance Degradation before applying to PROD NAM 2

5. identified Sep 29, 2025, 02:55 PM UTC

   We are continuing to test potential remediation for the performance degradation.

6. monitoring Sep 29, 2025, 03:30 PM UTC

   A fix has been successfully implemented, and our testing confirms the application is fully operational. We continue to actively monitor performance to ensure ongoing stability.

7. resolved Sep 29, 2025, 04:53 PM UTC

   Our monitoring confirms that the application is stable and functioning as expected. The incident is now closed.

Read the full incident report →

Started Sep 25, 2025, 01:33 PM UTC· resolved Sep 26, 2025, 06:09 AM UTC

1. investigating Sep 25, 2025, 01:33 PM UTC

   We are currently experiencing issues with the FlexNet Operations ALM/LLM Cloud Device Activation Service in the following Production environments: NAM1, NAM2, NAM3, NAM4, NAM6, and NAM7. Our teams are actively investigating the issue and working to restore full functionality as quickly as possible. We will provide updates as more information becomes available. Thank you for your patience.

2. investigating Sep 25, 2025, 02:10 PM UTC

   At this time the root cause has not yet been identified. We are actively working to diagnose and resolve the issue, and will share further updates as soon as more information becomes available. Thank you for your patience.

3. identified Sep 25, 2025, 02:34 PM UTC

   Our teams have identified a potential area of concern that may be contributing to the issue. We are actively working with our vendor to further investigate and validate this finding. Additional updates will be provided as we learn more. Thank you for your continued patience and understanding.

4. identified Sep 25, 2025, 03:15 PM UTC

   We are continuing to work with our vendor to investigate the issue. Our teams remain actively engaged and are exploring all potential contributing factors. We will share further updates as soon as more information becomes available. Thank you for your continued patience and support.

5. identified Sep 25, 2025, 03:45 PM UTC

   We continue to work with our cloud vendor to resolve the infrastructure issue as soon as possible.

6. identified Sep 25, 2025, 04:57 PM UTC

   We continue to work with our cloud vendor to resolve the infrastructure issue as soon as possible. We will provide updates as more information becomes available.

7. identified Sep 25, 2025, 05:33 PM UTC

   We remain actively engaged with our cloud vendor to resolve the underlying infrastructure issue as quickly as possible. We will continue to provide updates as new information becomes available.

8. identified Sep 25, 2025, 06:18 PM UTC

   We are continuing to work with our vendor to resolve the issue.

9. identified Sep 25, 2025, 07:31 PM UTC

   The FlexNet Operations ALM/LLM Cloud Device Activation Service remains unavailable. This incident is being handled at the highest escalation level—both with our vendor and internally at Revenera. The root cause has been identified; however, the required remediation and failover process is complex and ongoing. We are committed to keeping you informed with updates every 30 minutes.

10. identified Sep 25, 2025, 07:32 PM UTC

    Thank you for your patience and partnership as we work urgently to restore service. If your teams need to speak directly with a Revenera executive, please contact your customer success or support representative, and we will arrange a connection immediately. We will share an estimated time to resolution as soon as it becomes available.

11. identified Sep 25, 2025, 08:09 PM UTC

    The FlexNet Operations ALM/LLM Cloud Device Activation Service remains unavailable. This incident is being handled at the highest escalation level—both with our vendor and internally at Revenera. The root cause has been identified; however, the required remediation and failover process is complex and ongoing. We are committed to keeping you informed with updates every 30 minutes.

12. identified Sep 25, 2025, 08:38 PM UTC

    We are continuing to make progress with the remediation and failover process. If this continues error free, our expectation is to be able to provide an ETA for resolution within the next 30 minutes.

13. identified Sep 25, 2025, 09:18 PM UTC

    We are continuing to make progress with the remediation and failover process. We will continue to provide updates and share an ETA for resolution as soon as possible.

14. monitoring Sep 25, 2025, 10:06 PM UTC

    We have completed the remediation and failover process and FlexNet Operations ALM/LLM Cloud Device Activation Service in the following Production environments: NAM1, NAM2, NAM3, NAM4, NAM6, and NAM7 is now operational and we are closely monitoring the system. We will continue to monitor this for the next several hours before updating the status of this to resolved.

15. monitoring Sep 25, 2025, 10:32 PM UTC

    We are continuing to monitor for any further issues.

16. monitoring Sep 26, 2025, 05:51 AM UTC

    We are continuing to monitor for any further issues.

17. resolved Sep 26, 2025, 06:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Started Sep 02, 2025, 10:15 PM UTC· resolved Sep 02, 2025, 11:38 PM UTC

1. investigating Sep 02, 2025, 10:15 PM UTC

   We are experiencing intermittent issues affecting access to the following FlexNet Operations ALM/LLM services in the Production (NAM) environments. -FlexNet Operations ALM (Production NAM1, NAM2, NAM5, and NAM6) -Cloud Licensing Service for FlexNet Operations ALM/LLM (Production NAM1, NAM2, NAM5, and NAM6) -Reporter for FlexNet Operations ALM/LLM We are actively working to resolve the issue and will provide updates as we have more information.

2. monitoring Sep 02, 2025, 10:49 PM UTC

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

3. resolved Sep 02, 2025, 11:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2025, 11:13 PM UTC· resolved Aug 26, 2025, 10:30 AM UTC

1. investigating Aug 25, 2025, 11:13 PM UTC

   We are currently experiencing an issue with the SAP BO Reporter. Users attempting to launch reports are encountering the following error: "No business layer sent back from server" This issue is affecting ALM universes only. LLM universes remain unaffected. The problem is isolated to the Production environment; UAT is functioning normally. Our internal teams are investigating the root cause. We will update this page as soon as more information becomes available. Thank you for your patience and understanding.

2. monitoring Aug 26, 2025, 05:49 AM UTC

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

3. resolved Aug 26, 2025, 10:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 27, 2025, 04:01 PM UTC· resolved Jul 28, 2025, 07:46 AM UTC

1. investigating Jul 27, 2025, 04:01 PM UTC

   We are working with our cloud vendor to resolve the issue.

2. identified Jul 27, 2025, 04:04 PM UTC

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

3. resolved Jul 28, 2025, 07:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 21, 2025, 04:33 PM UTC· resolved Jul 24, 2025, 03:31 PM UTC

1. investigating Jul 21, 2025, 04:33 PM UTC

   We are currently experiencing an issue with our cloud service provider that is preventing the listing and download of raw data exports on both the Usage Intelligence dashboard and reporting APIs. We will provide an update as more information becomes available. We apologize for the inconvenience.

2. resolved Jul 24, 2025, 03:31 PM UTC

   Services have been restored and are operating as normal. We are marking this incident as resolved.

Read the full incident report →

Started Jun 25, 2025, 07:31 PM UTC· resolved Jun 25, 2025, 08:09 PM UTC

1. investigating Jun 25, 2025, 07:31 PM UTC

   We are investigating an issue with the FlexNet Operations ALM Reporter in the NAM Production environment. Executing reports results in an error preventing users from extracting data.

2. identified Jun 25, 2025, 07:32 PM UTC

   The issue has been identified and a fix has been implemented. We are testing internally to confirm the fix is working.

3. monitoring Jun 25, 2025, 07:41 PM UTC

   The fix has been implemented and our internal tests have passed. We are monitoring the application.

4. resolved Jun 25, 2025, 08:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 06:42 PM UTC· resolved Jun 12, 2025, 08:55 PM UTC

1. investigating Jun 12, 2025, 06:42 PM UTC

   We are experiencing issues with the Revenera Documentation site (https://docs.revenera.com/) resulting in an error page. Our service provider is investigating the cause of the issue and is working to resolve this quickly. We apologize for the inconvenience and ask that you contact Revenera Technical Support if you are in urgent need of product documentation.

2. identified Jun 12, 2025, 07:55 PM UTC

   The cause of the issue has been identified as today’s Google Cloud outage (https://status.cloud.google.com/). We will continue to monitor the situation and update this incident as more information becomes available. We appreciate your continued patience.

3. monitoring Jun 12, 2025, 08:25 PM UTC

   We have observed progress toward recovery and access to the Revenera Documentation site has been restored. We are continuing to monitor the situation and will provide further updates as needed.

4. resolved Jun 12, 2025, 08:55 PM UTC

   Access to the Revenera Documentation site is fully restored and this incident is now marked as resolved.

Read the full incident report →

Started May 14, 2025, 06:14 PM UTC· resolved May 15, 2025, 05:05 PM UTC

1. identified May 14, 2025, 06:14 PM UTC

   Please note: The following notice is applicable only for those tenants who are on the FlexNet Operations ALM Production (NAM2) environment. All other FlexNet Operations ALM Production (NAM/EU) and FlexNet Operations LLM Production environments are not impacted by this issue and can disregard this notice. The unaffected environments remain on the 2025.05 release. We've identified an issue in the FlexNet Operations ALM Production (NAM2) environment and have reverted the FlexNet Operations ALM 2025.05 release for that environment. The team is actively working to resolve the issue and will redeploy the FlexNet Operations ALM 2025.05 release to the Production (NAM2) environment once the fix has been validated. We will share the updated FlexNet Operations ALM 2025.05 release date for Production (NAM2) as soon as it is finalized. If you have any questions, please contact Revenera Technical Support for assistance.

2. resolved May 15, 2025, 05:05 PM UTC

   We’ve identified and resolved the issue that resulted in rolling back the FlexNet Operations 2025.05 release. The fix was validated, and the FlexNet Operations 2025.05 release was redeployed to the Production (NAM2) environment. We’ll continue to monitor the environment to ensure no further issues occur.

3. postmortem May 15, 2025, 05:06 PM UTC

   **What Happened:** The monitoring we have in place detected an increase in error messages appearing in the Production \(NAM2\) system logs. Since these errors began appearing around the completion of the FlexNet Operations 2025.05 release Production deployment, we performed a rollback of the release for this environment only as a precautionary measure. This mitigation approach enabled the team to assess the potential scope of impact, identify the root cause and possible fix, and avoid any disruption impact to our customers’ business. **Customer Impact:** * Only FlexNet Operations ALM customers whose tenants run in the Production \(NAM2\) environment were temporarily reverted to the previous release. * No service disruption occurred during the rollback process. **Resolution:** Upon investigation, we found the additional messages in the system logs were the result of an erroneous configuration. The configuration has been corrected and validated, and we’ve redeployed the FlexNet Operations 2025.05 release to the Production \(NAM2\) environment. **Next Steps:** * We continue to monitor the Production \(NAM2\) environment for errors. * Additional validations will be implemented to the release process to better identify these types of issues pre-release.

Read the full incident report →

Started May 14, 2025, 06:24 AM UTC· resolved May 14, 2025, 12:40 PM UTC

1. investigating May 14, 2025, 06:24 AM UTC

   Emails sent to Revenera Support using the [email protected] email address are bouncing and not getting through to Revenera. The relevant technical team has been engaged and is investigating. At this time, please use the Support case portal available at https://community.revenera.com/s/support-hub for creating and updating cases instead of sending email.

2. identified May 14, 2025, 06:33 AM UTC

   Our teams have successfully reproduced the issue and identified a configuration problem as the root cause. They are actively working on a fix and will provide further updates as they become available.

3. resolved May 14, 2025, 12:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 25, 2025, 07:16 AM UTC· resolved Apr 25, 2025, 08:25 AM UTC

1. investigating Apr 25, 2025, 07:16 AM UTC

   The license generator service is down, we are actively working to resolve the issue and restore functionality as quickly as possible.

2. investigating Apr 25, 2025, 07:18 AM UTC

   We are continuing to investigate this issue.

3. investigating Apr 25, 2025, 07:37 AM UTC

   We are continuing to investigate this issue.

4. identified Apr 25, 2025, 08:23 AM UTC

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

5. resolved Apr 25, 2025, 08:25 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 16, 2025, 10:11 PM UTC· resolved Apr 16, 2025, 10:11 PM UTC

1. resolved Apr 16, 2025, 10:11 PM UTC

   We found a networking problem that caused scheduled reports to not be sent on April 15 and 16. The problem has been corrected and any reports scheduled for April 17 should send. If you need the scheduled reports from April 15 and 16, you will need to manually re-run them from Reporter. Please reach out to our Support team (https://community.revenera.com/s/support-hub) if you require any assistance.

Read the full incident report →

Started Apr 16, 2025, 02:51 PM UTC· resolved Apr 16, 2025, 06:06 PM UTC

1. investigating Apr 16, 2025, 02:51 PM UTC

   We are currently working to resolve an unscheduled outage affecting the FlexNet Operations LLM UAT Producer Portal and End User Portal applications. This issue is impacting access to the application via both the user interface and web services.

2. investigating Apr 16, 2025, 03:39 PM UTC

   Based on our investigations, the ongoing outage in the FlexNet Operations LLM UAT application is also impacting the Electronic Software Delivery module for FlexNet Operations ALM UAT for NAM1, NAM2, NAM4. Our teams are actively working to resolve this matter, and we will provide further updates as more information becomes available. Thank you for your patience and understanding.

3. identified Apr 16, 2025, 03:45 PM UTC

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

4. monitoring Apr 16, 2025, 04:27 PM UTC

   A fix has been successfully implemented. We are currently monitoring to ensure stability and optimal performance.

5. resolved Apr 16, 2025, 06:06 PM UTC

   This incident has been resolved.

Read the full incident report →