Flexera Status

Resolved: The backlog has been addressed, and normal batch processing operations have resumed. This incident has been resolved.

Identified: We are making progress in processing tasks, especially those that accumulated substantial data backlog from earlier issues. We are now efficiently handling newer submissions.

Although there is still a volume of tasks pending, our systems are operating at increased capacity, processing multiple tasks concurrently to reduce the backlog swiftly.

We will continue to oversee the developments and provide updates on the progress.

Identified: We have successfully cleared all older backlog tasks, and only recent submissions are currently being processed. This has led to several tasks being completed successfully. However, we are observing a slowdown in the processing of some larger tasks and are actively investigating potential causes to prevent any impact on our services.

Investigations into this matter are underway to identify and resolve any underlying problems. We will continue to monitor the situation and take necessary actions to maintain system efficiency.

Identified: We continue to make substantial progress, significantly reducing the number of outstanding tasks. Currently, only a small number of tasks from previous days remain, with all of today's tasks being processed efficiently.

Additionally, we are addressing a backlog of routine system updates which do not impact the primary operations of our platform. Our team is actively managing these tasks to ensure they do not cause any disruptions to service.

Identified: The batch processor has continued to make steady progress in addressing a significant backlog of tasks. We have successfully moved through initial processing stages and are now handling subsequent data management operations. Our technical team is actively monitoring the situation and will continue to conduct periodic reviews to ensure all processes are completed efficiently.

Identified: The system continues to address the backlog of high-volume tasks. Progress is being made, particularly with significant operations that had slowed batch processing speeds. We are observing improvements as these key tasks near completion.

Our team is closely monitoring all processes to ensure their successful and timely conclusion. We will keep you updated on further developments and thank you for your continued patience.

Identified: The system is currently executing several high-volume database processes, including significant key operations. Once these substantial tasks are completed, we anticipate that the remaining batch processes will resume normal progress.

We are closely monitoring the situation to ensure successful completion.

Identified: Following the 2024 R2.1 upgrade last night, our team is actively addressing residual batch tasks that have accumulated post-upgrade. We have observed successful license reconciliations since yesterday and are ensuring that all tenant reconciliations are proceeding as expected.

We will continue to monitor the situation and provide updates as we make progress.

Identified: Our technical teams are actively monitoring the situation and anticipate that the upcoming 2024 R2.1 upgrade scheduled for tonight will result in the termination of the stalled processes, which is expected to alleviate the current backlog.

We will continue to monitor the system's performance following the upgrade to ensure that batch processing tasks return to normal operation. Further updates will be provided as necessary.

Identified: Incident Description: Following the resolution of yesterday's reconciliation issue, we are now investigating delays in batch processing tasks in the NA environment for Flexera One IT Asset Management (ITAM). Customers may experience delays in data updates, including reconciliation and other scheduled processes.

Priority: P2

Restoration Activity: While reconciliation functionality was successfully restored and verified, subsequent batch processing delays have emerged due to a backlog of tasks in the system. The reconciliation process was temporarily halted during the incident, and the resulting task volume is now contributing to the current delays.

Our teams are actively clearing the backlog, monitoring task performance, and addressing any stalled tasks. We are also reviewing the scheduler services and related infrastructure to ensure smooth task execution moving forward.

Resolved: The hotfixes for the affected customers have been successfully applied, and the cleanup process is complete. Our teams have monitored the platform and confirmed that the issue has been fully resolved.

Monitoring: All hotfixes have been applied, and our teams actively monitor the platform before declaring the issue as resolved.

Monitoring: The technical team has deployed hotfixes to address the remaining issues. While the overall impact remains minimal, we are working diligently to identify and resolve any outstanding issues to ensure complete resolution. We will continue to monitor the situation closely and keep you informed of our progress.

Monitoring: We are in the final stages of completing the cleanup process, and everything is progressing as expected. Nearly all customer data has been processed and validated. We are working closely to ensure the successful resolution of the incident.

Monitoring: The technical team has successfully implemented hotfixes for the majority of affected customers, resolving their issues. For the remaining few cases, solutions are prepared and will be executed promptly, with measures in place to ensure optimal performance. The overall impact continues to be minimal, and we are closely monitoring the situation to achieve full resolution.

Monitoring: The technical team continues to make progress in resolving the previously identified issues. Hotfixes have been developed and are being implemented for the remaining affected customers. The overall impact remains minimal, and efforts are ongoing to expedite full resolution.

We will continue to monitor the situation closely and provide updates as they become available.

Monitoring: The recent cleanup process has effectively addressed the majority of the remaining customers, with a very small number requiring additional attention; however, the impact is minimal. We will continue to monitor the situation closely and work diligently until full restoration is achieved.

Monitoring: The cleanup process for remaining tenants is progressing well. We will continue to monitor the situation and provide updates as we progress.

Monitoring: The recent cleanup has been effective. Initial log reviews show no issues, and checks across multiple databases confirm the removal of duplicate software license connections. Additionally, previously identified duplicate licenses have been successfully eliminated.

The next step is to address individual customer cases and any tenants that were missed in the initial cleanup, which is currently ongoing.

Monitoring: The cleanup process has been successfully completed in both the APAC and EU production environments. We will continue to monitor the progress and provide updates as the process advances.

Monitoring: Our team has identified a scenario where some duplicate licenses may reappear after reconciliation. We are actively working on a fix to address this and prevent further duplication. A hotfix has been raised for testing, and we will continue to provide updates as progress is made.

Please note that this issue has been resolved for the majority of customers. A small subset of cases has been identified, which we are addressing before fully resolving the incident.

Monitoring: The cleanup has resolved the issue for the majority of customers, with only a small subset requiring further fixes due to scenarios that the initial cleanup script couldn't address. The team has identified the affected tenants in both EU and APAC, and specific hotfixes will be developed to handle these cases.

Monitoring: The cleanup hotfix was successfully completed. Our technical team is actively monitoring the services to ensure the issue is fully resolved.

Identified: The cleanup hotfix is progressing as expected, with significant progress made. Our technical team continues to monitor the process to ensure successful completion

Identified: The cleanup hotfix has successfully completed another stage and is progressing as expected, with multiple databases still pending. We will keep you informed as we move forward.

Identified: The cleanup hotfix in production is underway, with our team actively monitoring and addressing any issues in real time to ensure successful completion across both environments. Further updates will be shared as progress continues.

Identified: After extended monitoring over the weekend, our teams confirmed that the test results met our expectations. The hotfix has been promoted to production, and our teams are actively working on the implementation. We will provide further updates as they become available.

Identified: Initial checks indicate that duplicated licenses are being retired as expected. We will continue monitoring to ensure consistent results across both the EU and APAC environments.

Identified: The rollback has been successfully applied in the EU and APAC environments, following successful testing in UAT. Our team will monitor reconciles over the weekend to ensure data is properly processed before initiating the cleanup in production on Monday.

While minor issues were encountered during testing, they are being addressed. We expect the cleanup to resolve the issue for the majority of customers, though a small subset may require additional follow-up. Further updates will be provided as progress continues.

Identified: The data cleanup process has been initiated in our testing environment, though some results are still under review. Our team is analyzing the outcome to ensure all issues are fully addressed.

Identified: Our team is diligently working to resolve this issue and has initiated the data cleanup process. We will continue to provide updates as we make progress.

Identified: Following successful system tests, we have proceeded with deploying the update. The next step involves data cleanup to address any remaining impacts, which is expected to begin tomorrow. Our team is working diligently to resolve this issue and will continue to provide updates as progress is made.

Identified: Our team has completed the initial build and identified areas requiring further refinement to ensure system stability. We are currently conducting comprehensive system tests to verify these improvements. If these tests are successful, we plan to proceed with the deployment of the update. We understand the impact this issue may have on your operations and are working diligently to resolve it. We will continue to provide updates as progress is made.

Identified: Our team continues to work through validation and testing. While the initial build was completed, additional refinements were necessary to ensure stability before moving forward. We are now addressing the final steps, and if all goes as planned, we anticipate proceeding to the next phase of testing soon. Further updates will be provided as progress continues.

Identified: Our team is still awaiting the necessary build completion before proceeding with the deployment. Testing and validation efforts are ongoing to ensure a smooth rollout. We will provide further updates as progress continues.

Monitoring: To ensure comprehensive system stability, our team has been deploying additional hotfixes. However, we have encountered some issues, which we are currently addressing. The cleanup script has been completed and tested. We are actively working to resolve any lingering issues to proceed as planned.

Monitoring: Our team is currently conducting a thorough validation process to ensure system stability and accuracy. This involves detailed analysis and testing to confirm that all residual issues are effectively addressed. We are also performing a comprehensive data cleanup to remove any remaining impacts. We will continue to provide updates as progress is made.

Monitoring: A past change that caused the issue has been reverted, and our teams are validating the rollback. Testing is actively underway to ensure everything functions as expected. Additionally, a data cleanup process is in progress to address any remaining impact.

Due to the need for thorough validation, testing, and cleanup across environments, the entire process may take multiple days to complete. If all goes well, the next phase of testing is scheduled for tomorrow. We will continue providing updates as progress is made.

Identified: We have taken corrective action and are progressing through our testing processes.

Monitoring: Our teams are actively working on a fix to address the issue and take corrective measures, after which additional steps and validations will follow to ensure accuracy. We will continue to provide updates as progress is made.

Monitoring: We are actively investigating and evaluating remediation options to resolve the problem.

Identified: We have escalated the priority of the incident to P1.

Identified: We are continuing to work on the fix and actively monitoring the environment over the weekend to prevent further impact. Our team is working to expedite the resolution and will provide updates as progress is made.

Identified: We have identified an issue related to a past release that is causing duplicate license records to appear. Our team is actively working on a resolution and will provide further updates as soon as more information becomes available.

Investigating: Incident Description: Our teams have identified an issue impacting multiple customers in the EU and Australia regions. Affected customers may encounter duplicate records when importing licenses from the SaaS manager.

Priority: P1

Restoration activity: Our technical team is actively working on identifying the root cause and restoring services. Further updates will be provided as we continue our efforts to resolve the incident.

Resolved: The hotfixes for the affected customers have been successfully applied, and the cleanup process is complete. Our teams have monitored the platform and confirmed that the issue has been fully resolved.

Monitoring: All hotfixes have been applied, and our teams actively monitor the platform before declaring the issue as resolved.

Monitoring: The technical team has deployed hotfixes to address the remaining issues. While the overall impact remains minimal, we are working diligently to identify and resolve any outstanding issues to ensure complete resolution. We will continue to monitor the situation closely and keep you informed of our progress.

Monitoring: We are in the final stages of completing the cleanup process, and everything is progressing as expected. Nearly all customer data has been processed and validated. We are working closely to ensure the successful resolution of the incident.

Monitoring: The technical team has successfully implemented hotfixes for the majority of affected customers, resolving their issues. For the remaining few cases, solutions are prepared and will be executed promptly, with measures in place to ensure optimal performance. The overall impact continues to be minimal, and we are closely monitoring the situation to achieve full resolution.

Monitoring: The technical team continues to make progress in resolving the previously identified issues. Hotfixes have been developed and are being implemented for the remaining affected customers. The overall impact remains minimal, and efforts are ongoing to expedite full resolution.

We will continue to monitor the situation closely and provide updates as they become available.

Monitoring: The recent cleanup process has effectively addressed the majority of the remaining customers, with a very small number requiring additional attention; however, the impact is minimal. We will continue to monitor the situation closely and work diligently until full restoration is achieved.

Monitoring: The cleanup process for remaining tenants is progressing well. We will continue to monitor the situation and provide updates as we progress.

Monitoring: The recent cleanup has been effective. Initial log reviews show no issues, and checks across multiple databases confirm the removal of duplicate software license connections. Additionally, previously identified duplicate licenses have been successfully eliminated.

The next step is to address individual customer cases and any tenants that were missed in the initial cleanup, which is currently ongoing.

Monitoring: The cleanup process has been successfully completed in both the APAC and EU production environments. We will continue to monitor the progress and provide updates as the process advances.

Monitoring: Our team has identified a scenario where some duplicate licenses may reappear after reconciliation. We are actively working on a fix to address this and prevent further duplication. A hotfix has been raised for testing, and we will continue to provide updates as progress is made.

Please note that this issue has been resolved for the majority of customers. A small subset of cases has been identified, which we are addressing before fully resolving the incident.

Monitoring: The cleanup has resolved the issue for the majority of customers, with only a small subset requiring further fixes due to scenarios that the initial cleanup script couldn't address. The team has identified the affected tenants in both EU and APAC, and specific hotfixes will be developed to handle these cases.

Monitoring: The cleanup hotfix was successfully completed. Our technical team is actively monitoring the services to ensure the issue is fully resolved.

Identified: The cleanup hotfix is progressing as expected, with significant progress made. Our technical team continues to monitor the process to ensure successful completion

Identified: The cleanup hotfix has successfully completed another stage and is progressing as expected, with multiple databases still pending. We will keep you informed as we move forward.

Identified: The cleanup hotfix in production is underway, with our team actively monitoring and addressing any issues in real time to ensure successful completion across both environments. Further updates will be shared as progress continues.

Identified: After extended monitoring over the weekend, our teams confirmed that the test results met our expectations. The hotfix has been promoted to production, and our teams are actively working on the implementation. We will provide further updates as they become available.

Identified: Initial checks indicate that duplicated licenses are being retired as expected. We will continue monitoring to ensure consistent results across both the EU and APAC environments.

Identified: The rollback has been successfully applied in the EU and APAC environments, following successful testing in UAT. Our team will monitor reconciles over the weekend to ensure data is properly processed before initiating the cleanup in production on Monday.

While minor issues were encountered during testing, they are being addressed. We expect the cleanup to resolve the issue for the majority of customers, though a small subset may require additional follow-up. Further updates will be provided as progress continues.

Identified: The data cleanup process has been initiated in our testing environment, though some results are still under review. Our team is analyzing the outcome to ensure all issues are fully addressed.

Identified: Our team is diligently working to resolve this issue and has initiated the data cleanup process. We will continue to provide updates as we make progress.

Identified: Following successful system tests, we have proceeded with deploying the update. The next step involves data cleanup to address any remaining impacts, which is expected to begin tomorrow. Our team is working diligently to resolve this issue and will continue to provide updates as progress is made.

Identified: Our team has completed the initial build and identified areas requiring further refinement to ensure system stability. We are currently conducting comprehensive system tests to verify these improvements. If these tests are successful, we plan to proceed with the deployment of the update. We understand the impact this issue may have on your operations and are working diligently to resolve it. We will continue to provide updates as progress is made.

Identified: Our team continues to work through validation and testing. While the initial build was completed, additional refinements were necessary to ensure stability before moving forward. We are now addressing the final steps, and if all goes as planned, we anticipate proceeding to the next phase of testing soon. Further updates will be provided as progress continues.

Identified: Our team is still awaiting the necessary build completion before proceeding with the deployment. Testing and validation efforts are ongoing to ensure a smooth rollout. We will provide further updates as progress continues.

Monitoring: To ensure comprehensive system stability, our team has been deploying additional hotfixes. However, we have encountered some issues, which we are currently addressing. The cleanup script has been completed and tested. We are actively working to resolve any lingering issues to proceed as planned.

Monitoring: Our team is currently conducting a thorough validation process to ensure system stability and accuracy. This involves detailed analysis and testing to confirm that all residual issues are effectively addressed. We are also performing a comprehensive data cleanup to remove any remaining impacts. We will continue to provide updates as progress is made.

Monitoring: A past change that caused the issue has been reverted, and our teams are validating the rollback. Testing is actively underway to ensure everything functions as expected. Additionally, a data cleanup process is in progress to address any remaining impact.

Due to the need for thorough validation, testing, and cleanup across environments, the entire process may take multiple days to complete. If all goes well, the next phase of testing is scheduled for tomorrow. We will continue providing updates as progress is made.

Identified: We have taken corrective action and are progressing through our testing processes.

Monitoring: Our teams are actively working on a fix to address the issue and take corrective measures, after which additional steps and validations will follow to ensure accuracy. We will continue to provide updates as progress is made.

Monitoring: We are actively investigating and evaluating remediation options to resolve the problem.

Identified: We have escalated the priority of the incident to P1.

Identified: We are continuing to work on the fix and actively monitoring the environment over the weekend to prevent further impact. Our team is working to expedite the resolution and will provide updates as progress is made.

Identified: We have identified an issue related to a past release that is causing duplicate license records to appear. Our team is actively working on a resolution and will provide further updates as soon as more information becomes available.

Investigating: Incident Description: Our teams have identified an issue impacting multiple customers in the EU and Australia regions. Affected customers may encounter duplicate records when importing licenses from the SaaS manager.

Priority: P1

Restoration activity: Our technical team is actively working on identifying the root cause and restoring services. Further updates will be provided as we continue our efforts to resolve the incident.

Resolved: Our monitoring and health checks have confirmed that the issue has been fully resolved, and all services are now operating as expected.

Monitoring: Our technical team has taken corrective measures, and we are conducting further validation to ensure full functionality. Monitoring is ongoing to confirm there are no lingering impacts. We will provide further updates as validation progresses.

Investigating: Incident Description: We are currently experiencing an issue affecting the Cloud Cost Optimization (CCO) platform in the EU and NA regions. While some pages are still operational, customers may experience issues when accessing pages displaying cost data.

Priority: P2

Restoration Activity: Our technical team is actively investigating the issue and working to restore functionality. We will provide further updates as we continue resolving the incident.

Resolved: Our monitoring and health checks have confirmed that the issue has been fully resolved, and all services are now operating as expected.

Monitoring: Our technical team has taken corrective measures, and we are conducting further validation to ensure full functionality. Monitoring is ongoing to confirm there are no lingering impacts. We will provide further updates as validation progresses.

Investigating: Incident Description: We are currently experiencing an issue affecting the Cloud Cost Optimization (CCO) platform in the EU and NA regions. While some pages are still operational, customers may experience issues when accessing pages displaying cost data.

Priority: P2

Restoration Activity: Our technical team is actively investigating the issue and working to restore functionality. We will provide further updates as we continue resolving the incident.

Resolved: The system has been fully restored, all checks have passed, and new data has successfully synced after the restoration. This incident has been resolved.

Identified: The replication and synchronization processes have been completed, and we are now moving on to the next steps, which include the restoration of the affected instances.

Identified: We are currently performing a critical data dump as part of the restoration process. Once completed, the data will be moved to the necessary environment. Following the dump, restoration will be carried out on the affected instances and this process is expected to take an extended period.

We sincerely apologize for the disruption this has caused and are closely monitoring the situation. We will continue to keep you updated as we make progress toward resolving the issue.

Investigating: Incident Description: We are currently addressing an issue that has disrupted the replication of vulnerability tracking (VT) data for Software Vulnerability Manager (SVM) customers. This issue has resulted in a temporary inability for customers to receive new advisories, patches, or vulnerability tracking data.

Priority: P2

Restoration Activity: Our technical team has identified that a critical component in the data replication chain was inadvertently turned off, which has halted the replication process. Efforts to restore this functionality are underway, including taking necessary data dumps to ensure integrity and completeness when replication resumes.

Resolved: The system has been fully restored, all checks have passed, and new data has successfully synced after the restoration. This incident has been resolved.

Identified: The replication and synchronization processes have been completed, and we are now moving on to the next steps, which include the restoration of the affected instances.

Identified: We are currently performing a critical data dump as part of the restoration process. Once completed, the data will be moved to the necessary environment. Following the dump, restoration will be carried out on the affected instances and this process is expected to take an extended period.

We sincerely apologize for the disruption this has caused and are closely monitoring the situation. We will continue to keep you updated as we make progress toward resolving the issue.

Investigating: Incident Description: We are currently addressing an issue that has disrupted the replication of vulnerability tracking (VT) data for Software Vulnerability Manager (SVM) customers. This issue has resulted in a temporary inability for customers to receive new advisories, patches, or vulnerability tracking data.

Priority: P2

Restoration Activity: Our technical team has identified that a critical component in the data replication chain was inadvertently turned off, which has halted the replication process. Efforts to restore this functionality are underway, including taking necessary data dumps to ensure integrity and completeness when replication resumes.