Historial de interrupciones de Revenera

1. 12 de agosto de 2026 a las 15:49 UTCinvestigating

   We are currently experiencing issues with the Revenera Documentation site (https://docs.revenera.com/) that may result in intermittent access or difficulty loading documentation for some users. Our IT team is actively investigating the issue and working to restore consistent access. We will provide updates as more information becomes available. If you are in urgent need of Revenera product documentation, please contact Revenera Technical Support for assistance.

1. 27 de julio de 2026 a las 14:33 UTCinvestigating

   Actualmente estamos experimentando un problema que afecta a la funcionalidad de Eventos Personalizados de Usage Intelligence, específicamente la vista de Eventos Aduaneros recientes y descargas de archivos de eventos personalizados. Nuestro equipo está investigando y trabajando activamente para resolver el problema. Proporcionaremos actualizaciones a medida que se disponga de más información.

2. 27 de julio de 2026 a las 17:16 UTCidentified

   Se ha resuelto la cuestión que afecta a la vista de Eventos Aduaneros Recientes y la capacidad de descargar Archivos de Eventos Personalizados. Aunque la recopilación de datos no se ve afectada, la generación de archivos de eventos personalizados se ha pausado temporalmente hasta que hayamos completado las mejoras del servidor. Proporcionaremos una actualización una vez que estas mejoras estén completas y se haya reanudado la generación de archivos.

3. 28 de julio de 2026 a las 16:56 UTCidentified

   Continuamos trabajando en las mejoras del servidor y compartiremos información adicional ya que está disponible.

4. 5 de agosto de 2026 a las 5:35 UTCresolved

   El equipo ha resuelto la cuestión y restablecido todos los servicios afectados. Todos los servicios siguen funcionando según lo previsto, y el medio ambiente sigue siendo estable. Si encuentra algún problema, póngase en contacto con Revenera Technical Support para recibir asistencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de julio de 2026 a las 15:54 UTCinvestigating

   Actualmente estamos experimentando un problema intermitente con el servicio de activación de dispositivos en la nube de ALM/LLM en el entorno PROD NAM2. Nuestro equipo está investigando activamente la cuestión y trabajando para identificar la causa raíz. Proporcionaremos más actualizaciones tan pronto como se disponga de información adicional. Gracias por su paciencia y comprensión.

2. 22 de julio de 2026 a las 16:06 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 22 de julio de 2026 a las 17:27 UTCinvestigating

   Seguimos investigando esta cuestión. Proporcionaremos más actualizaciones tan pronto como se disponga de información adicional. Gracias por su paciencia y comprensión.

4. 22 de julio de 2026 a las 18:52 UTCmonitoring

   Creemos que hemos resuelto el problema y ahora estamos monitoreando. Proporcionaremos actualizaciones tan pronto como esté disponible más información.

5. 22 de julio de 2026 a las 22:26 UTCresolved

   Nuestro monitoreo no ha encontrado ninguna señal de la cuestión y creemos que ahora está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 27 de mayo de 2026 a las 6:37 UTCinvestigating

   We are actively working with our vendor to restore email functionality and will provide an update as soon as more information becomes available. We apologise for the inconvenience.

2. 27 de mayo de 2026 a las 7:46 UTCmonitoring

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

3. 27 de mayo de 2026 a las 10:34 UTCresolved

   This incident has been resolved.

1. 22 de abril de 2026 a las 10:57 UTCinvestigating

   We are currently investigating an issue with scheduled report delivery. As a temporary workaround, customers may manually generate the reports until the issue is resolved.

2. 22 de abril de 2026 a las 12:24 UTCidentified

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

3. 22 de abril de 2026 a las 12:48 UTCmonitoring

   A fix has been implemented and our initial monitoring shows scheduled reports are being sent out. We are monitoring the application to ensure the fix remains stable.

4. 22 de abril de 2026 a las 18:20 UTCresolved

   This incident has been resolved.

1. 17 de abril de 2026 a las 13:36 UTCinvestigating

   Issue: The FlexNet Operations Analytics service is currently unavailable in the Production environment. Impact: Customers may experience errors when accessing analytics-related functionality via the FlexNet Operations Producer Portal impacting both NAM and EU. Current Status: Our engineering team is actively investigating the issue and working to restore service as quickly as possible. Updates will be shared as more information becomes available.

2. 17 de abril de 2026 a las 15:11 UTCidentified

   The issue has been identified, and a fix has been successfully applied to the NAM environment. We are actively monitoring the NAM environment to ensure stability. Work is currently underway to apply the fix to the EU environment. Further updates will be shared as progress continues.

3. 17 de abril de 2026 a las 15:30 UTCresolved

   The fix has been applied to the EU environment. Monitoring has verified that all services are operational and no further issues have been detected. This incident is now fully resolved.

1. 16 de abril de 2026 a las 16:44 UTCidentified

   Update: Clarification on Scope of UTF‑8 Character Impact In addition to email‑related issues previously reported, some customers may experience issues when creating users or accounts with non‑English (UTF‑8) characters via the application user interface. Specifically: - The issue only impacts users and accounts created or edited via the UI. - API‑based creation and updates are not affected. - Records created via the UI with non‑English characters may display incorrectly. - Data exports or extracts that include these UI‑created records may contain corrupted character data. The fix currently being prepared for deployment will prevent new occurrences of this issue. However, downstream processing of data that was already created with corrupted characters will not automatically correct that data, and any previously corrupted values in extracts will persist unless the source records are updated after the fix is applied. Next Steps: - The validated fix corrects character handling across email processing, account and user creation. - Deployment remains the top priority due to business and data integrity impact. - We will update this status page once deployment is complete. Workarounds: Until the fix is deployed, customers are advised to: - Avoid using non‑English characters when creating or modifying email templates, users or accounts through the UI, where possible. - Use API‑based processes if UTF‑8 characters are required. We recognize the impact this has caused and appreciate your patience as we work to fully resolve the issue.

2. 16 de abril de 2026 a las 18:15 UTCidentified

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

3. 17 de abril de 2026 a las 16:07 UTCidentified

   Fix Deployed to User Acceptance Testing (UAT) The fix addressing the UTF‑8 character handling issue has now been successfully deployed to the User Acceptance Testing (UAT) environment. Our validation and functional testing in UAT have completed successfully. We are currently monitoring the behavior of the fix in this environment to ensure stability and confirm there are no unintended side effects. Next Steps Continued monitoring in the UAT environment is in progress. Pending final verification, we are planning a production deployment on Monday, April 20. We will update this status page once the fix is deployed to Production or if timelines change. Important Note As previously communicated, this fix prevents new occurrences of UTF‑8 character corruption. Any data that was already created with corrupted characters prior to the fix will not be automatically corrected and will require updates to the source records after deployment. We appreciate your patience and will continue to share updates as we move toward full resolution.

4. 20 de abril de 2026 a las 10:01 UTCmonitoring

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

5. 20 de abril de 2026 a las 14:11 UTCresolved

   This incident has been resolved.

1. 9 de abril de 2026 a las 13:30 UTCinvestigating

   We are currently experiencing data refresh delays, resulting in Reporter not displaying the latest data in the following environments: -All Reporter data in FlexNet Operations LLM Production -Software Delivery (Download Universe) Reporter data in FlexNet Operations ALM Production Note: Non-Software Delivery in FlexNet Operations ALM is unaffected by the data refresh delay. We are actively working to address the issue and will provide updates when more information becomes available. If you have any questions, please submit a ticket with Revenera Technical Support .

2. 9 de abril de 2026 a las 16:51 UTCresolved

   The Reporter data refresh has completed successfully.

1. 8 de abril de 2026 a las 18:47 UTCinvestigating

   We are currently experiencing data refresh delays, resulting in Reporter not displaying the latest data in the following environments: -All Reporter data in FlexNet Operations LLM Production -Software Delivery (Download Universe) Reporter data in FlexNet Operations ALM Production Note: Non-Software Delivery in FlexNet Operations ALM is not affected by the data refresh delay. We are actively working to address the issue and will provide updates when more information becomes available. If you have any questions, please submit a ticket with Revenera Technical Support .

2. 8 de abril de 2026 a las 19:16 UTCresolved

   The Reporter data refresh has completed successfully.

1. 2 de abril de 2026 a las 14:41 UTCmonitoring

   We experienced intermittent access issues in the FlexNet Operations ALM/LLM Production (NAM) environment that affected access to the ALM/LLM portals. The issue has been resolved, and we are monitoring to ensure continued stability.

2. 2 de abril de 2026 a las 17:12 UTCresolved

   FlexNet Operations ALM/LLM remains stable in the Production (NAM) environments, and no further issues have been observed. This incident is now resolved. If you experience any issues, please open a support ticket with Revenera Technical Support.

1. 23 de marzo de 2026 a las 18:09 UTCinvestigating

   We are experiencing issues with the FlexNet Operations Cloud ALM/LLM Device Activation Service in the Production environments NAM2. Functionality impacted by this outage includes, but may not be limited to, the following: -Device creation and activation -View device or device related details -Device lifecycle activities 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. 23 de marzo de 2026 a las 18:49 UTCmonitoring

   Our team has identified the cause of the issue and a fix has been implemented. We have verified the service is fully restored. We will continue to monitor the service to ensure ongoing stability.

3. 23 de marzo de 2026 a las 21:16 UTCresolved

   Our monitoring confirms that the service is operating as normal. We are marking this incident as resolved.

1. 22 de enero de 2026 a las 18:35 UTCinvestigating

   We are experiencing issues with the FlexNet Operations Cloud ALM application and FlexNet Operations ALM/LLM Cloud Licensing Service. 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. 22 de enero de 2026 a las 19:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 de enero de 2026 a las 19:45 UTCidentified

   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.

4. 22 de enero de 2026 a las 19:57 UTCmonitoring

   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. 22 de enero de 2026 a las 23:51 UTCresolved

   Our monitoring confirms that the service is operating as normal. We are marking this incident as resolved.

1. 2 de enero de 2026 a las 16:56 UTCinvestigating

   We are currently experiencing degraded performance with Revenera Usage Intelligence services due to an issue with our service provider. Our team is actively working to resolve this and restore full functionality as quickly as possible. We appreciate your patience and will provide updates as they become available. Services affected: -Analytics Dashboard (analytics.revenera.com) -Web Reporting APIs (analytics-api.revenera.com) Services unaffected: -Collection of usage data from installations via SDK call-home

2. 5 de enero de 2026 a las 17:15 UTCidentified

   We’ve identified a potential fix for the issue and are currently implementing it. Our team is actively working to resolve the problem and will provide another update once the fix has been fully applied and verified. Thank you for your patience.

3. 6 de enero de 2026 a las 19:05 UTCidentified

   Our team continues to work diligently to implement the identified fix and making progress toward full resolution. We’ll continue to share updates as work advances. Thank you for your continued patience.

4. 8 de enero de 2026 a las 15:18 UTCmonitoring

   A fix has been deployed and all affected services are operational. We will continue to monitoring these services for any issues.

5. 13 de enero de 2026 a las 16:14 UTCresolved

   Monitoring has verified that all services are operational and no further issues have been detected. This incident is now fully resolved.

1. 2 de diciembre de 2025 a las 19:59 UTCinvestigating

   We are experiencing an issue preventing emails from being sent from FlexNet Operations ALM/LLM across all Production (NAM) environments. We are actively working to restore email functionality and will provide an update as soon as more information becomes available. We apologize for the inconvenience.

2. 2 de diciembre de 2025 a las 20:33 UTCmonitoring

   A fix has been implemented and emails have resumed processing. We will continue to monitor the service to ensure all emails processed completely and no further issues occur.

3. 3 de diciembre de 2025 a las 6:27 UTCmonitoring

   We will continue to monitor the service to ensure all emails are processed completely and no further issues occur.

4. 3 de diciembre de 2025 a las 8:36 UTCresolved

   This incident has been resolved.

1. 27 de noviembre de 2025 a las 1:42 UTCinvestigating

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

2. 27 de noviembre de 2025 a las 1:56 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 de noviembre de 2025 a las 1:59 UTCmonitoring

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

4. 27 de noviembre de 2025 a las 2:57 UTCresolved

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

1. 20 de noviembre de 2025 a las 9:18 UTCinvestigating

   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. 20 de noviembre de 2025 a las 11:34 UTCinvestigating

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

3. 20 de noviembre de 2025 a las 15:31 UTCinvestigating

   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. 20 de noviembre de 2025 a las 15:52 UTCidentified

   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.

5. 20 de noviembre de 2025 a las 19:48 UTCinvestigating

   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.

6. 21 de noviembre de 2025 a las 4:45 UTCinvestigating

   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.

7. 21 de noviembre de 2025 a las 7:28 UTCinvestigating

   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.

8. 21 de noviembre de 2025 a las 9:36 UTCidentified

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

9. 21 de noviembre de 2025 a las 9:46 UTCmonitoring

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

10. 21 de noviembre de 2025 a las 12:58 UTCmonitoring

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

11. 22 de noviembre de 2025 a las 17:32 UTCresolved

    This incident has been resolved.

1. 13 de noviembre de 2025 a las 16:39 UTCinvestigating

   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. 13 de noviembre de 2025 a las 19:49 UTCidentified

   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. 14 de noviembre de 2025 a las 6:37 UTCidentified

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

4. 14 de noviembre de 2025 a las 17:00 UTCidentified

   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. 14 de noviembre de 2025 a las 19:50 UTCmonitoring

   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. 14 de noviembre de 2025 a las 22:09 UTCresolved

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

1. 13 de noviembre de 2025 a las 1:58 UTCinvestigating

   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. 13 de noviembre de 2025 a las 2:35 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 de noviembre de 2025 a las 2:41 UTCidentified

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

4. 13 de noviembre de 2025 a las 2:44 UTCmonitoring

   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. 13 de noviembre de 2025 a las 4:46 UTCresolved

   This incident has been resolved.

1. 7 de noviembre de 2025 a las 2:23 UTCinvestigating

   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. 7 de noviembre de 2025 a las 2:34 UTCinvestigating

   We are continuing to investigate this issue.

3. 7 de noviembre de 2025 a las 2:36 UTCmonitoring

   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. 10 de noviembre de 2025 a las 5:36 UTCresolved

   This incident has been resolved.

1. 5 de noviembre de 2025 a las 13:56 UTCinvestigating

   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. 5 de noviembre de 2025 a las 15:03 UTCinvestigating

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

3. 5 de noviembre de 2025 a las 15:39 UTCinvestigating

   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. 5 de noviembre de 2025 a las 16:42 UTCidentified

   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. 5 de noviembre de 2025 a las 17:49 UTCidentified

   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. 5 de noviembre de 2025 a las 19:25 UTCinvestigating

   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. 5 de noviembre de 2025 a las 21:57 UTCinvestigating

   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. 6 de noviembre de 2025 a las 8:05 UTCidentified

   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. 6 de noviembre de 2025 a las 9:57 UTCidentified

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

10. 6 de noviembre de 2025 a las 10:31 UTCmonitoring

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

11. 6 de noviembre de 2025 a las 11:11 UTCmonitoring

    We are continuing to monitor for any further issues.

12. 6 de noviembre de 2025 a las 12:05 UTCresolved

    This incident has been resolved.