CloudCheckr – Federal Region – Service Degradation

Update timeline

1. investigating Dec 15, 2025, 05:56 PM UTC

   Incident Description: We are currently investigating a service degradation affecting the CloudCheckr platform in the Federal region. Customers may experience issues accessing services at this time. Priority: P1 Restoration Activity: Our technical teams are engaged and working to determine the underlying cause and restore normal service. We are monitoring system behavior closely and will provide further updates as restoration work continues.

2. identified Dec 15, 2025, 06:23 PM UTC

   Our teams have confirmed that a core service responsible for managing application operations in the CloudCheckr Federal region is not responding as expected. This is preventing the region from operating normally. We are actively working with our service provider to resolve the issue and move toward restoration. We will provide further updates as they become available.

3. identified Dec 15, 2025, 08:27 PM UTC

   Our teams and our service provider continue to investigate the issue to determine the underlying cause and implement the necessary remediation. Additional diagnostic work is underway to further pinpoint the source of the problem and move toward restoration.

4. resolved Dec 15, 2025, 08:57 PM UTC

   The issue affecting the CloudCheckr Federal region has been resolved. Our teams identified a configuration issue within the service components responsible for managing application operations in this environment. The configuration has been corrected, and the region is now operating normally.

5. postmortem Dec 31, 2025, 03:56 AM UTC

   **Description:** CloudCheckr – Federal Region – Service Outage **Timeframe:** December 15, 2025, 9:00 AM PST – 12:30 PM PST **Incident Summary** On December 15, 2025, at approximately 9:00 AM PST, customers using the CloudCheckr Federal region experienced a service outage that prevented access to the environment. During this period, customers may have experienced unavailability when attempting to access the Federal region. All other CloudCheckr regions remained accessible. Technical teams began investigating the issue and performing diagnostics to determine the underlying cause. The focus was placed on the components responsible for bringing the Federal environment online, and a configuration-related issue was identified that was preventing required services from starting successfully. This blocked the environment from completing its normal startup sequence and resulted in customer-facing unavailability. Once the configuration was corrected, affected services were able to initialize properly, and access to the CloudCheckr Federal region was restored at 12:30 PM PST. The environment was monitored following restoration, and no further disruption was observed. **Root Cause** The outage was caused by a configuration issue in the CloudCheckr Federal environment that prevented required service components from starting successfully after a platform update was applied. Because these components were unable to initialize, the region could not complete its normal startup sequence, resulting in service unavailability for customers in the Federal environment. Once the configuration issue was identified and corrected, the affected services were able to start as expected, access was restored, and the environment returned to normal operation. **Remediation Actions** 1. Issue Isolation: Confirmed impact was limited to the Federal region and all other CloudCheckr environments remained operational. 2. Configuration Correction: A configuration dependency preventing service startup was corrected, allowing the environment to recover. 3. Service Validation: Startup progression and access behavior were validated to confirm that all required components were functioning normally. 4. Post-Restoration Monitoring: The environment was monitored for continued stability after restoration was completed at 12:30 PM PST. **Future Preventative Measures** A full retrospective was completed with the teams involved to review the incident, contributing factors, and the response timeline. While this behavior has not been typical in prior update cycles, the review identified opportunities to improve how similar situations are identified and coordinated in the future. Based on that discussion, the following measures are being considered: 1. Earlier Identification of Startup Issues: The teams are reviewing options to help identify configuration or initialization issues earlier in the startup sequence, with the goal of reducing investigation time if similar behavior occurs again. 2. Clearer Coordination Paths During Update Events: Internal guidance is being reinforced so that, when needed, support channels, including engagement with the service provider, can be leveraged to help support completion of similar updates, along with validation or escalation if issues arise during future update activities. These efforts are intended to support faster identification and more coordinated response efforts if this type of issue were to occur again, with the goal of maintaining reliability for customers using the CloudCheckr Federal environment.