Flexera Status

Resolved: All backlog processing has been completed and services remain stable. This issue has now been resolved.

Our teams will continue to monitor the platform to ensure ongoing stability. Further details will be shared in a post mortem report.

Monitoring: Most data processing has completed, and the platform continues to operate in a stable state while keeping up with incoming data. Our teams are performing final validations to confirm everything is functioning as expected.

We will provide a final update once these validations are complete.

Monitoring: Processing continues following an overnight service restart that required a portion of data to be replayed. Most organizations are now processing within approximately one hour of real time, and the remaining backlog continues to reduce steadily.

Our teams are actively monitoring the environment to ensure full recovery and continued platform stability.

Monitoring: Most data is now being processed successfully, and the platform continues to operate in a stable state while keeping up with incoming data. A small amount of remaining backlog is still being worked through, with recovery activities managed carefully to maintain overall service stability.

We will continue to monitor progress and provide additional updates as recovery completes.

Monitoring: Our technical teams continue to closely monitor recovery progress. The system is steadily processing the existing backlog in a controlled manner, with priority placed on maintaining platform stability. We will continue to provide updates as recovery progresses or if there are any material changes.

Monitoring: Backlog processing continues, and the platform remains stable. The system is keeping up with incoming data while previously delayed inventory data is being processed in a controlled manner to ensure overall service stability.

We will continue to monitor progress and provide additional updates as recovery continues.

Monitoring: Backlog processing remains in progress, and the platform continues to operate in a stable state. Recovery activities are being carefully managed to ensure delayed inventory data is processed safely while maintaining overall service stability.

We will continue to monitor progress and provide additional updates as recovery continues.

Monitoring: Backlog processing continues to make steady progress following the previously deployed fix. The platform remains stable, and recovery activities are being carefully managed to ensure delayed inventory data is processed safely without impacting downstream services.

Customers may continue to experience delays in updated inventory data appearing during this recovery period. We will continue to monitor progress and provide further updates as appropriate.

Monitoring: Our technical teams continue to work through the backlog recovery process. Recovery activities are being carried out cautiously to avoid overwhelming downstream services and to ensure platform stability throughout the restoration process.

Monitoring: Our technical teams have successfully designed and implemented a fix. Services are now operating normally, and backlog processing is underway for the data accumulated during the incident.

Investigating: Incident Description: We are investigating an issue impacting IT Visibility (ITV) services in the US Production environment. Affected customers may experience delays in normalized inventory updates appearing in ITV .

Priority: P2

Restoration Activity: Our technical teams have identified that a backend service is experiencing elevated request throttling from an upstream cloud provider dependency, resulting in delayed inventory processing. Teams are actively investigating the issue and working to restore normal processing. We are monitoring the environment closely and will continue to provide updates as progress is made toward full restoration.

Resolved: Our technical teams have completed validation of the affected areas and confirmed that services have been fully restored.

The platform is now operating normally, and we are continuing to monitor to ensure sustained stability. This issue is considered resolved, and further details will be shared in a post-mortem report.

Monitoring: Our technical teams are actively investigating and validating the affected areas while continuing to monitor overall service behavior. Initial findings suggest the issue may have been influenced by a service provider disruption, which has now been resolved.

We are continuing to assess any residual impact and closely monitoring the platform to ensure stability. Further updates will be provided as more information becomes available.

Investigating: Incident Description: We are investigating a service degradation affecting Flexera One customers in the NAM region. Customers may experience intermittent errors, delayed page loading, or pages remaining in a loading state when accessing certain areas of the application, including Cloud Cost Optimization functionality and Administration > Shared Settings. Some Cloud Cost Optimization customers may also experience delays in cost data processing.

Priority: P2

Restoration Activity: Our technical teams are actively investigating and validating the affected areas. We are also monitoring upstream service provider disruptions that may be contributing to the issue. We will continue to monitor service behavior and work toward restoration.

We will provide another update as soon as additional information is available.

Resolved: Our technical teams have completed validation of the affected areas and confirmed that services have been fully restored.

The platform is now operating normally, and we are continuing to monitor to ensure sustained stability. This issue is considered resolved, and further details will be shared in a post-mortem report.

Monitoring: Our technical teams are actively investigating and validating the affected areas while continuing to monitor overall service behavior. Initial findings suggest the issue may have been influenced by a service provider disruption, which has now been resolved.

We are continuing to assess any residual impact and closely monitoring the platform to ensure stability. Further updates will be provided as more information becomes available.

Investigating: Incident Description: We are investigating a service degradation affecting Flexera One customers in the NAM region. Customers may experience intermittent errors, delayed page loading, or pages remaining in a loading state when accessing certain areas of the application, including Cloud Cost Optimization functionality and Administration > Shared Settings. Some Cloud Cost Optimization customers may also experience delays in cost data processing.

Priority: P2

Restoration Activity: Our technical teams are actively investigating and validating the affected areas. We are also monitoring upstream service provider disruptions that may be contributing to the issue. We will continue to monitor service behavior and work toward restoration.

We will provide another update as soon as additional information is available.

Resolved: Our technical teams have completed validation of the affected areas and confirmed that services have been fully restored.

The platform is now operating normally, and we are continuing to monitor to ensure sustained stability. This issue is considered resolved, and further details will be shared in a post-mortem report.

Monitoring: Our technical teams are actively investigating and validating the affected areas while continuing to monitor overall service behavior. Initial findings suggest the issue may have been influenced by a service provider disruption, which has now been resolved.

We are continuing to assess any residual impact and closely monitoring the platform to ensure stability. Further updates will be provided as more information becomes available.

Investigating: Incident Description: We are investigating a service degradation affecting Flexera One customers in the NAM region. Customers may experience intermittent errors, delayed page loading, or pages remaining in a loading state when accessing certain areas of the application, including Cloud Cost Optimization functionality and Administration > Shared Settings. Some Cloud Cost Optimization customers may also experience delays in cost data processing.

Priority: P2

Restoration Activity: Our technical teams are actively investigating and validating the affected areas. We are also monitoring upstream service provider disruptions that may be contributing to the issue. We will continue to monitor service behavior and work toward restoration.

We will provide another update as soon as additional information is available.

Postmortem: Description: Flexera- Spot- US east- 1a- Database connection and low request issues

Timeframe: May 7, 2026, 4:25 PM PST to May 8, 2026, 7:04 PM PST

‌

Incident Summary

‌

On May 7, 2026, Flexera identified a service degradation impacting Spot services in the US East 1a region. During the impact duration, customers experienced difficulties launching instances. In addition, some backend services experienced reduced request handling capacity and intermittent database connectivity issues, resulting in degraded provisioning behavior and delayed scaling operations.

Initial investigation determined that the issue coincided with a broader disruption affecting an external cloud infrastructure provider. The external disruption introduced elevated latency and intermittent service instability across dependent infrastructure components, which contributed to degraded provisioning and backend service performance within the Spot platform.

During the investigation, engineering teams also identified a database issue caused by the service provider outage that posed a potential performance risk under degraded infrastructure conditions. The issue was mitigated early in the response process, and system stability improved following remediation actions.

Throughout the incident, technical teams continuously monitored service health, validated provisioning behavior, and assessed mitigation options to minimize customer impact while the external provider disruption remained active. Over several hours following mitigation, Spot services remained stable with no recurrence of customer-facing issues observed.

After an extended monitoring period confirmed continued stability, the incident was considered resolved following confirmation that the underlying external provider disruption had been fully remediated on May 8, 2026, at 7:04 PM PST.

‌

Root Cause

‌

The issue was primarily caused by a disruption affecting an external cloud infrastructure provider supporting services in the US East 1a region. The disruption resulted in increased latency, intermittent connectivity issues, and degraded infrastructure performance, which impacted Spot instance provisioning operations and related backend services.

Contributing Factors:

• Elevated latency and intermittent failures across dependent infrastructure services increased provisioning delays and request instability.
• A database performance issue, triggered by the underlying service provider disruption, introduced additional load under degraded infrastructure conditions and increased the risk of intermittent service instability.
• The prolonged nature of the external provider disruption extended the duration of customer impact and required continuous monitoring and mitigation activities.

‌

Remediation Actions

‌

The following remediation steps were implemented to restore service functionality:

• Investigated and monitored infrastructure and provisioning service behavior across impacted Spot components.
• Identified and mitigated a database performance degradation contributing to elevated performance risk.
• Validated provisioning stability and backend service recovery following mitigation efforts.
• Performed extended monitoring to ensure sustained service stability and confirm the absence of recurring customer impact.

‌

Future Preventative Measures

‌

• Alerting Reliability Improvements: Improve alert delivery validation and monitoring to ensure critical database alerts are consistently propagated across all operational notification channels, including collaboration and incident management platforms.
• Regional Resilience Evaluation: Evaluate additional regional resilience and failover capabilities to reduce the impact scope of regional infrastructure disruptions. Any future implementation will be subject to cost-impact analysis and internal approval processes.
• Third-Party Provider Escalation Process: Enhance operational procedures for third-party infrastructure incidents by establishing earlier escalation and engagement processes with external cloud service providers during active service disruptions.

Resolved: Following an extended period of monitoring, our teams have confirmed that services have remained stable. The external service provider has also confirmed full resolution of their outage. This incident is now resolved, and a detailed post-mortem report will be shared with additional insights.

Monitoring: Our technical teams have completed internal stabilization actions to address the earlier service impact, and Spot services have remained stable for the last several hours. We have not observed any recurrence of customer-facing impact, and instance provisioning behavior continues to operate as expected.

We are continuing to monitor the environment and our service provider’s updates closely. The incident will remain in monitoring for the next few hours, with closure to follow once this additional monitoring period is complete.

Monitoring: Some customers may experience residual issues following the recent fix. Our technical teams are actively working to address these and ensure full service stability. We will provide further updates as more information becomes available.

Monitoring: Our teams have implemented mitigation measures to address the impact from the external service disruption, and services have now been restored. We are actively monitoring the platform to ensure continued stability and will provide further updates as more information becomes available.

Identified: Incident Description: We are currently investigating multiple issues impacting SPOT services.Customers may experience difficulties launching instances in the affected region, resulting in degraded provisioning capabilities. Initial findings indicate that the issue is related to an ongoing disruption within our cloud service provider, specifically in the us-east-1 region. As a result, customers may face difficulties launching instances, resulting in degraded service performance.

Priority: P2

Restoration Activity: Our technical teams are actively engaged and are working with the service provider to monitor the ongoing regional issue. We are assessing the impact on dependent services, including database connectivity and request processing, while identifying potential mitigation options. Further updates will be provided as more information becomes available and as service stability improves.

Resolved: Our technical teams have confirmed that all affected functionality has been fully restored.

Validation has completed successfully, including Elastigroup creation and page load performance. We are marking this incident as resolved and will continue standard monitoring.

Monitoring: Our technical teams have completed initial restoration actions, and validation confirms that Elastigroup creation is now working successfully.

We are continuing to monitor page load performance and overall functionality before confirming full resolution.

Identified: Our technical teams have identified that the issue is related to a recent change, and the change is currently being reverted.

Initial validation indicates that customers are now able to create Elastigroups again. We are continuing to validate page load performance and overall functionality before confirming full recovery.

Investigating: Incident Description: We are currently investigating degraded performance affecting Spot Elastigroup for AWS customers. Customers may experience delays when loading the Elastigroup page and may be unable to create new Elastigroups.

Priority: P2

Restoration Activity: Our technical teams are actively investigating and working to restore normal functionality. Current findings indicate the impact is limited to AWS customers. Validation is ongoing to confirm the full scope of impact.

Postmortem: Description: Flexera- Spot- US east- 1a- Database connection and low request issues

Timeframe: May 7, 2026, 4:25 PM PST to May 8, 2026, 7:04 PM PST

‌

Incident Summary

‌

On May 7, 2026, Flexera identified a service degradation impacting Spot services in the US East 1a region. During the impact duration, customers experienced difficulties launching instances. In addition, some backend services experienced reduced request handling capacity and intermittent database connectivity issues, resulting in degraded provisioning behavior and delayed scaling operations.

Initial investigation determined that the issue coincided with a broader disruption affecting an external cloud infrastructure provider. The external disruption introduced elevated latency and intermittent service instability across dependent infrastructure components, which contributed to degraded provisioning and backend service performance within the Spot platform.

During the investigation, engineering teams also identified a database issue caused by the service provider outage that posed a potential performance risk under degraded infrastructure conditions. The issue was mitigated early in the response process, and system stability improved following remediation actions.

Throughout the incident, technical teams continuously monitored service health, validated provisioning behavior, and assessed mitigation options to minimize customer impact while the external provider disruption remained active. Over several hours following mitigation, Spot services remained stable with no recurrence of customer-facing issues observed.

After an extended monitoring period confirmed continued stability, the incident was considered resolved following confirmation that the underlying external provider disruption had been fully remediated on May 8, 2026, at 7:04 PM PST.

‌

Root Cause

‌

The issue was primarily caused by a disruption affecting an external cloud infrastructure provider supporting services in the US East 1a region. The disruption resulted in increased latency, intermittent connectivity issues, and degraded infrastructure performance, which impacted Spot instance provisioning operations and related backend services.

Contributing Factors:

• Elevated latency and intermittent failures across dependent infrastructure services increased provisioning delays and request instability.
• A database performance issue, triggered by the underlying service provider disruption, introduced additional load under degraded infrastructure conditions and increased the risk of intermittent service instability.
• The prolonged nature of the external provider disruption extended the duration of customer impact and required continuous monitoring and mitigation activities.

‌

Remediation Actions

‌

The following remediation steps were implemented to restore service functionality:

• Investigated and monitored infrastructure and provisioning service behavior across impacted Spot components.
• Identified and mitigated a database performance degradation contributing to elevated performance risk.
• Validated provisioning stability and backend service recovery following mitigation efforts.
• Performed extended monitoring to ensure sustained service stability and confirm the absence of recurring customer impact.

‌

Future Preventative Measures

‌

• Alerting Reliability Improvements: Improve alert delivery validation and monitoring to ensure critical database alerts are consistently propagated across all operational notification channels, including collaboration and incident management platforms.
• Regional Resilience Evaluation: Evaluate additional regional resilience and failover capabilities to reduce the impact scope of regional infrastructure disruptions. Any future implementation will be subject to cost-impact analysis and internal approval processes.
• Third-Party Provider Escalation Process: Enhance operational procedures for third-party infrastructure incidents by establishing earlier escalation and engagement processes with external cloud service providers during active service disruptions.

Resolved: Following an extended period of monitoring, our teams have confirmed that services have remained stable. The external service provider has also confirmed full resolution of their outage. This incident is now resolved, and a detailed post-mortem report will be shared with additional insights.

Monitoring: Our technical teams have completed internal stabilization actions to address the earlier service impact, and Spot services have remained stable for the last several hours. We have not observed any recurrence of customer-facing impact, and instance provisioning behavior continues to operate as expected.

We are continuing to monitor the environment and our service provider’s updates closely. The incident will remain in monitoring for the next few hours, with closure to follow once this additional monitoring period is complete.

Monitoring: Some customers may experience residual issues following the recent fix. Our technical teams are actively working to address these and ensure full service stability. We will provide further updates as more information becomes available.

Monitoring: Our teams have implemented mitigation measures to address the impact from the external service disruption, and services have now been restored. We are actively monitoring the platform to ensure continued stability and will provide further updates as more information becomes available.

Identified: Incident Description: We are currently investigating multiple issues impacting SPOT services.Customers may experience difficulties launching instances in the affected region, resulting in degraded provisioning capabilities. Initial findings indicate that the issue is related to an ongoing disruption within our cloud service provider, specifically in the us-east-1 region. As a result, customers may face difficulties launching instances, resulting in degraded service performance.

Priority: P2

Restoration Activity: Our technical teams are actively engaged and are working with the service provider to monitor the ongoing regional issue. We are assessing the impact on dependent services, including database connectivity and request processing, while identifying potential mitigation options. Further updates will be provided as more information becomes available and as service stability improves.

Resolved: Our technical teams have confirmed that all affected functionality has been fully restored.

Validation has completed successfully, including Elastigroup creation and page load performance. We are marking this incident as resolved and will continue standard monitoring.

Monitoring: Our technical teams have completed initial restoration actions, and validation confirms that Elastigroup creation is now working successfully.

We are continuing to monitor page load performance and overall functionality before confirming full resolution.

Identified: Our technical teams have identified that the issue is related to a recent change, and the change is currently being reverted.

Initial validation indicates that customers are now able to create Elastigroups again. We are continuing to validate page load performance and overall functionality before confirming full recovery.

Investigating: Incident Description: We are currently investigating degraded performance affecting Spot Elastigroup for AWS customers. Customers may experience delays when loading the Elastigroup page and may be unable to create new Elastigroups.

Priority: P2

Restoration Activity: Our technical teams are actively investigating and working to restore normal functionality. Current findings indicate the impact is limited to AWS customers. Validation is ongoing to confirm the full scope of impact.

Postmortem: Description: Flexera- Spot- US east- 1a- Database connection and low request issues

Timeframe: May 7, 2026, 4:25 PM PST to May 8, 2026, 7:04 PM PST

‌

Incident Summary

‌

On May 7, 2026, Flexera identified a service degradation impacting Spot services in the US East 1a region. During the impact duration, customers experienced difficulties launching instances. In addition, some backend services experienced reduced request handling capacity and intermittent database connectivity issues, resulting in degraded provisioning behavior and delayed scaling operations.

Initial investigation determined that the issue coincided with a broader disruption affecting an external cloud infrastructure provider. The external disruption introduced elevated latency and intermittent service instability across dependent infrastructure components, which contributed to degraded provisioning and backend service performance within the Spot platform.

During the investigation, engineering teams also identified a database issue caused by the service provider outage that posed a potential performance risk under degraded infrastructure conditions. The issue was mitigated early in the response process, and system stability improved following remediation actions.

Throughout the incident, technical teams continuously monitored service health, validated provisioning behavior, and assessed mitigation options to minimize customer impact while the external provider disruption remained active. Over several hours following mitigation, Spot services remained stable with no recurrence of customer-facing issues observed.

After an extended monitoring period confirmed continued stability, the incident was considered resolved following confirmation that the underlying external provider disruption had been fully remediated on May 8, 2026, at 7:04 PM PST.

‌

Root Cause

‌

The issue was primarily caused by a disruption affecting an external cloud infrastructure provider supporting services in the US East 1a region. The disruption resulted in increased latency, intermittent connectivity issues, and degraded infrastructure performance, which impacted Spot instance provisioning operations and related backend services.

Contributing Factors:

• Elevated latency and intermittent failures across dependent infrastructure services increased provisioning delays and request instability.
• A database performance issue, triggered by the underlying service provider disruption, introduced additional load under degraded infrastructure conditions and increased the risk of intermittent service instability.
• The prolonged nature of the external provider disruption extended the duration of customer impact and required continuous monitoring and mitigation activities.

‌

Remediation Actions

‌

The following remediation steps were implemented to restore service functionality:

• Investigated and monitored infrastructure and provisioning service behavior across impacted Spot components.
• Identified and mitigated a database performance degradation contributing to elevated performance risk.
• Validated provisioning stability and backend service recovery following mitigation efforts.
• Performed extended monitoring to ensure sustained service stability and confirm the absence of recurring customer impact.

‌

Future Preventative Measures

‌

• Alerting Reliability Improvements: Improve alert delivery validation and monitoring to ensure critical database alerts are consistently propagated across all operational notification channels, including collaboration and incident management platforms.
• Regional Resilience Evaluation: Evaluate additional regional resilience and failover capabilities to reduce the impact scope of regional infrastructure disruptions. Any future implementation will be subject to cost-impact analysis and internal approval processes.
• Third-Party Provider Escalation Process: Enhance operational procedures for third-party infrastructure incidents by establishing earlier escalation and engagement processes with external cloud service providers during active service disruptions.

Resolved: Following an extended period of monitoring, our teams have confirmed that services have remained stable. The external service provider has also confirmed full resolution of their outage. This incident is now resolved, and a detailed post-mortem report will be shared with additional insights.

Monitoring: Our technical teams have completed internal stabilization actions to address the earlier service impact, and Spot services have remained stable for the last several hours. We have not observed any recurrence of customer-facing impact, and instance provisioning behavior continues to operate as expected.

We are continuing to monitor the environment and our service provider’s updates closely. The incident will remain in monitoring for the next few hours, with closure to follow once this additional monitoring period is complete.

Monitoring: Some customers may experience residual issues following the recent fix. Our technical teams are actively working to address these and ensure full service stability. We will provide further updates as more information becomes available.

Monitoring: Our teams have implemented mitigation measures to address the impact from the external service disruption, and services have now been restored. We are actively monitoring the platform to ensure continued stability and will provide further updates as more information becomes available.

Identified: Incident Description: We are currently investigating multiple issues impacting SPOT services.Customers may experience difficulties launching instances in the affected region, resulting in degraded provisioning capabilities. Initial findings indicate that the issue is related to an ongoing disruption within our cloud service provider, specifically in the us-east-1 region. As a result, customers may face difficulties launching instances, resulting in degraded service performance.

Priority: P2

Restoration Activity: Our technical teams are actively engaged and are working with the service provider to monitor the ongoing regional issue. We are assessing the impact on dependent services, including database connectivity and request processing, while identifying potential mitigation options. Further updates will be provided as more information becomes available and as service stability improves.