Flexera One & Other Flexera SaaS Applications – Service Disruption

Update timeline

1. monitoring Oct 20, 2025, 09:45 AM UTC

   We experienced a widespread outage impacting Flexera One (including IT Visibility, IT Asset Management, SaaS Manager, other applications, and related services). Customers across all regions may have been unable to log in or access functionality during this period. Spot services also experienced impact, and potentially other SaaS products may have been affected. This outage was caused by a major service provider disruption affecting multiple services globally. Priority: P1 Restoration Activity: Flexera One services have now been restored. Our technical teams are continuing validations across all regions and are actively monitoring the environment to ensure full recovery.

2. monitoring Oct 20, 2025, 10:27 AM UTC

   Services are coming back online and functionality has been restored across Flexera One products. Customers should now be able to log in and access core features normally. Spot services were also impacted during the outage and remain in a degraded state. Our teams are continuing to work on validations and are monitoring closely until full recovery is confirmed.

3. monitoring Oct 20, 2025, 10:27 AM UTC

   Flexera One services have been restored, and customers should now be able to log in and access product functionality across regions. Spot services remain degraded, and our teams are continuing to monitor recovery efforts closely. We will share further updates as confirmations are received.

4. monitoring Oct 20, 2025, 01:45 PM UTC

   Flexera One services continue to operate normally, with no further issues observed. Customers should be able to log in and access functionality across all regions. Spot services are still impacted, with newly launched instances unable to progress beyond a pending state. Our teams are continuing to collaborate closely with our service provider to address this issue. Full validations will be performed as soon as recovery is confirmed.

5. monitoring Oct 20, 2025, 04:48 PM UTC

   Spot services are still affected due to restrictions at our service provider. To stabilize their environment during recovery, new instance launches are being limited, which may result in instances remaining in a pending state. Our teams are monitoring closely and will perform full validations once recovery is confirmed. Additional updates will be shared as progress continues.

6. monitoring Oct 20, 2025, 05:14 PM UTC

   Spot services remain affected due to limitations at our service provider, which are preventing new instances from launching. Our teams are monitoring closely and will validate recovery as it progresses. Cloud Cost Optimization (CCO) services in North America are also experiencing partial impact. Specific functions that rely on cost data may load more slowly or be unavailable, while other areas remain accessible. Our teams are actively engaged and will provide updates as recovery continues.

7. monitoring Oct 20, 2025, 07:22 PM UTC

   Our teams are continuing to monitor the situation closely. The following remain impacted due to the ongoing service provider issue: • Spot – New instance launches are limited, which may result in pending states and delays. • Cloud Cost Optimization (CCO) – North America functions that rely on cost data are degraded, while other areas remain accessible. • CloudCheckr – US region is experiencing degraded performance. We are actively monitoring these services and will provide updates as recovery progresses.

8. monitoring Oct 21, 2025, 12:10 AM UTC

   Our service provider has confirmed resolution of the outage, and we have verified restoration of impacted Flexera applications with most services now stable. . Cloud Cost Optimization (CCO) – Service confirmed restored in North America and operating normally. . CloudCheckr – Service confirmed restored in the US region. Some customers may observe minor delays while the provider clears backlog processing, but overall services have stabilized. . Spot – Recovery validation remains in progress. Teams are monitoring closely to confirm full restoration. . All Other Applications and Services – Including ITAM, ITV, and SaaS Manager, were confirmed restored earlier today and remain healthy. We will provide a final confirmation once all services are fully validated.

9. resolved Oct 21, 2025, 12:58 AM UTC

   Following confirmation from our service provider that the underlying issue has been resolved, our technical teams have validated that all Flexera applications and services are restored. . Spot – Service has been fully restored and is operating normally. . Cloud Cost Optimization (CCO) – Functionality has been confirmed restored in NA. . CloudCheckr – Service in the US region has been restored. Some backlog may still be observed, but overall functionality has stabilized. . All Other Applications and Services – Including ITAM (NA), ITV (NA and APAC), and SaaS Manager (NA), were restored earlier today and remain healthy. We will continue monitoring closely. A full post-mortem report will be shared in the coming days, capturing the complete scope and timeline of impact. We are also working closely with our service provider and will address any concerns if identified.

10. postmortem Oct 31, 2025, 10:04 PM UTC

    **Description:** Flexera One & Other Flexera SaaS Applications – NA – Service Disruption Caused by Upstream Provider Outage **Timeframe:** * **Initial impact window – Flexera One service unavailability** \(Cloud Cost Optimization, Cloud License Management, IT Asset Management, IT Visibility, SaaS Manager\): October 20, 12:03 AM – 2:35 AM PDT * **Partial service degradation and delayed processing** \(CloudCheckr, Cloud Cost Optimization, Spot Platform\): October 20, 12:03 AM – 2:20 PM PDT **Incident Summary** On October 20, 2025, at approximately 12:03 AM PDT, Flexera’s monitoring systems detected a widespread service degradation affecting multiple Flexera One and other SaaS applications. During this period, customers may have experienced intermittent login failures, delayed data processing, or temporary unavailability across certain workflows. The disruption was linked to a major outage at an underlying cloud service provider that affected multiple global customers and services. Core systems responsible for compute provisioning, authentication, and network traffic routing were degraded, impacting several Flexera applications hosted or dependent on that environment. As a result, Flexera One applications including Cloud Cost Optimization \(CCO\), Cloud License Management \(CLM\), IT Asset Management \(ITAM\), IT Visibility \(ITV\), and SaaS Manager experienced temporary service unavailability during the early hours of the incident. Additional application services that relied on extended dependencies, such as CCO, CloudCheckr, and Spot Platform, continued to experience partial impact with degraded performance and delayed processing as the service provider completed its recovery process. Throughout the event, Flexera’s technical and incident management teams continuously monitored the situation, validated system behavior, and coordinated across product, platform, and support teams to ensure consistent visibility and recovery validation. By 2:20 PM PDT, the service provider had completed full recovery, after which Flexera performed extended monitoring and comprehensive post-recovery checks to confirm that all applications were operating normally with no residual impact. **Root Cause** The disruption was caused by a large-scale service failure within the infrastructure of a third-party cloud provider supporting several Flexera applications. This event disrupted authentication and traffic management processes, resulting in temporary unavailability across multiple Flexera services. As the underlying environment was restored, service functionality across impacted Flexera applications progressively returned to normal. **Remediation Actions** While the root cause originated outside Flexera’s environment, multiple teams remained fully engaged throughout the duration of the event to ensure coordinated response, timely stakeholder updates, and rapid recovery. During the early recovery phase, external customer communications were temporarily impacted due to an outage affecting Flexera’s StatusPage. Internal coordination channels remained active, and updates were prepared in advance to ensure that once StatusPage was restored, customers would promptly receive accurate information on service recovery and validation activities. The following actions were taken: 1. Event Detected and Response Initiated: Internal monitoring systems identified the service degradation, and response teams were immediately engaged under Flexera’s Major Incident framework. 2. Impact Assessment: Engineering and product teams analyzed affected applications, validated interdependencies, and identified potential customer impact. 3. Cross-Team Coordination: Technical, platform, and support teams maintained continuous communication to validate recovery progress and ensure consistent alignment across all product areas. 4. Progress Monitoring: As restoration progressed at the infrastructure level, teams performed iterative validation to confirm application stability and accessibility. 5. Customer Communication: Flexera closely tracked the service provider’s recovery progress, verifying each stage internally and communicating status updates as recovery milestones were confirmed. 6. Post-Recovery Validation: Following full restoration, Flexera conducted extended testing and monitoring to confirm application health and verify that all systems were operating normally. **Future Preventative Measures** Flexera treats every incident, including third-party outages of this scale, with the highest level of priority and accountability. Following this event, a detailed internal retrospective was completed, and the service provider’s published post-incident summary was thoroughly reviewed to identify lessons learned and opportunities for improvement. As part of ongoing service reliability improvements, the following initiatives are underway: 1. Enhanced Communication Resilience o Revisiting existing documentation to define clear contingency steps for customer updates during third-party outages. o Establishing alternate communication channels, such as the Flexera Community, to ensure customers remain informed if primary platforms are unavailable. o Collaborating with customer-facing teams, including Support and Customer Success, to explore additional mechanisms that enable timely and proactive outreach during widespread service disruptions. 2. Operational Readiness and Industry Alignment o Conducting regular reviews of industry standards and best practices for managing cloud dependencies and maintaining communication continuity. o Expanding observability across provider-dependent components to accelerate detection and improve early impact assessment.