We will be performing infrastructure maintenance during this window. Customers may experience delays in PR scans, along with brief service interruptions

Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.

Functionality is fully restored; we are continuing to monitor to ensure everything remains stable.

The incident has been resolved, and the platform is operating normally.

A fix has been applied and functionality is fully restored; we are continuing to monitor to ensure everything remains stable.

We’re continuing to monitor detection processing and the associated delays in violation status updates (including auto-resolution)

Summary
On June 10, 2026, customers may have experienced slowness in SAST Pull Request scanning. The root cause has been identified in insufficient processing capacity in one of the services used in SAST Pull Request scans flow. This resulted in degraded performance and a portion of scans taking longer time than usual to start and to complete. The processing capacity has since been increased and adequate alerts have been created to ensure the issue does not occur again.

Key Timeline (IDT)

• June 10, 2026, 17:50 IDT: Performance degradation began.

• June 10, 2026, 18:15 IDT: The team noticed degraded performance and began working on stabilizing the system.

• June 10, 2026, 18:40 IDT: The system was confirmed to be fully operational.

Root Cause
The incident was caused by an insufficient processing capacity in one of the services involved in SAST Pull Request scan flow. This means, that under heavy load, the service struggled to maintain its operational velocity. The team also found that the SAST Pull Request scans flow was not fully optimized and it lead to over-utilization of the service.

Actions Taken

• Increased processing capacity of the bottleneck service.

• Created alert to detect bottlenecks quicker.

• Optimized behavior of the service.

Action Items

• Further optimize SAST Pull Request scanning flow.

The system is now fully operational. There should be no more degraded performance.

Summary
We observed a period of slowness and intermittent timeouts affecting various system functions in the EU region, including the application interface and pull request (PR) scans. The issue was primarily caused by a processing system reaching its network and memory capacity limits, exacerbated by a high volume of automated activity from a single source. We have since upgraded the underlying infrastructure and implemented safeguards to prevent similar high-volume activity from impacting the system. The issue is now fully resolved, and all services have returned to expected performance levels.

Key Timeline (IDT)

• July 13, 2026, 11:44 IDT: Incident detected following reports of UI slowness and PR scan delays.

• July 13, 2026, 12:19 IDT: Infrastructure bottleneck identified; decision made to upgrade the processing cluster.

• July 13, 2026, 12:26 IDT: A high-volume automated process was identified and disabled to reduce immediate load.

• July 13, 2026, 13:09 IDT: Infrastructure upgrade completed; network throughput returned to normal levels.

• July 13, 2026, 15:35 IDT: All backlogs cleared, and the incident was officially resolved.

Root Cause
The incident was triggered by a combination of factors: a processing cluster reached its maximum network bandwidth and memory capacity due to an undersized configuration for the current workload. This was further strained by a specific automated workflow that generated an unusually high volume of update requests. Additionally, a configuration difference in the message processing pipeline in the EU region prevented the system from effectively handling the resulting backlog.

Actions Taken

• Upgraded Infrastructure: The processing cluster was upgraded to a higher-capacity instance type to provide more network bandwidth and memory.

• Disabled High-Volume Source: A specific client identifier responsible for excessive traffic was temporarily disabled to restore system stability.

• Restored Connectivity: Affected service components were restarted to ensure they re-established clean connections to the upgraded infrastructure.

• Increased Processing Parallelism: The number of partitions in the affected message queue was increased to allow the system to process the backlog more quickly.

Action Items

• Enhance Monitoring: Implement new alerts for network and memory utilization to detect capacity issues before they impact customers.

• Optimize Update Workflow: Refactor the status update process to batch requests, significantly reducing the load on the processing system.

• Implement Rate Limiting: Introduce safeguards to prevent any single source from consuming disproportionate system resources.

• Standardize Regional Configurations: Conduct an audit to ensure infrastructure and message queue settings are consistent across all regions.

The issue affecting Maestro AI services has been resolved. Maestro Risk Explorability, Risk AI Remediation, Maestro Remediation, and Graph AI are now available and operating normally.

Summary

On July 9, 2026, customers using the Maestro service in the European production environment experienced a period of service unavailability. The issue began following a configuration update that inadvertently changed the service's regional routing. This caused the system to attempt connections through a network path that lacked the necessary permissions and to a region where specific processing models were unavailable. The issue has been fully resolved, and service has been restored to all affected customers.

Key Timeline (IDT)

• July 9, 2026, 12:02 IDT: The incident was identified and an investigation was initiated.

• July 9, 2026, 12:07 IDT: Public notification was issued regarding the service interruption.

• July 9, 2026, 13:00 IDT: A network configuration fix was applied, restoring primary connectivity.

• July 9, 2026, 13:39 IDT: Service was fully restored after implementing model fallbacks, and the incident was marked as resolved.

Root Cause

The service interruption was triggered by a recent update to the authentication and configuration process. This update introduced a conflict in how the system identified its operating region. Specifically, an automated update process overrode manual settings, routing traffic to a different regional endpoint. This new path was blocked by a missing network security rule and attempted to use a processing model that was not supported in that specific region, leading to service failure.

Actions Taken

• Restored Network Connectivity: Manually updated network security rules to allow secure traffic through the new regional endpoint.

• Implemented Model Fallbacks: Configured the system to use alternative processing models to ensure immediate service availability while long-term regional configurations were adjusted.

• Updated Status Communications: Maintained real-time updates for stakeholders and customers throughout the recovery process.

Action Items

• Standardize Configuration Precedence: Update the deployment workflow to prevent automated processes from silently overriding critical environment settings.

• Infrastructure Audit: Conduct a comprehensive review of network security rules across all regions to ensure consistency and prevent similar connectivity gaps.

• Enhance Automated Monitoring: Implement end-to-end health checks and synthetic probes to detect regional connectivity issues automatically before they impact users.

• Improve Deployment Policies: Establish new guidelines to ensure that configuration changes are deployed and validated in production-like environments more frequently to reduce the risk of "stale" updates.

AWS has confirmed that the issue has been fully mitigated and we are currently not observing any related issues.

Summary

During the incident, customers experienced significant delays and temporary disruptions across SAST, SCA, CCA, and Secret repository scans and push events. The issue was caused by a surge in reachability scanner jobs that overwhelmed the processing queue, compounded by scanner pods requesting excessive CPU and memory, infrastructure resource limits being reached, and inefficiencies in job prioritization and retry logic. As a result, processing capacity was improperly consumed and a large job backlog accumulated. A series of corrective updates were deployed to stabilize the environment, and the processing environment has since returned to expected performance levels.

Impact

Customers experienced delays for SAST, SCA, CCA, and Secret repository scans and push events, with some requests delayed by several hours and a peak queue size of over 64,000 jobs. Lower priority scans such as Trivy, Syft, and CCA were most affected, though high-priority jobs were eventually processed without further delay.

Key Timeline (IDT)

• 21.06.2026, 17:16 IDT: A surge in reachability scanner jobs caused the CycodeX queue to grow rapidly.

• 22.06.2026, 10:07 IDT: The issue was identified by an on-call engineer.

• 22.06.2026, 12:55 IDT: We increased the scanning platform resources to process more jobs.

• 22.06.2026, 14:10 IDT: A fix that lowered new reachability scanners was deployed to production.

• 22.06.2026, 18:43 IDT: Existing reachability scanners' priority was lowered.

• 23.06.2026, 09:12 IDT: Scans with higher priority were processed. Only lower priority scans remained, including CCA.

• 23.06.2026, 13:51 IDT: A fix that reduced communication overload to Kubernetes was deployed. The scanning platform started processing scan jobs much faster.

• 23.06.2026, 17:34 IDT: The queue was fully processed.

Root Cause

The issue was triggered by a combination of factors:

• Reachability scanner job surge -- A surge in reachability scanner jobs caused the CycodeX queue to grow rapidly, which led to resource bottlenecks in the cluster and a peak queue size of over 64,000 jobs.

• Excessive pod resource requests -- Due to configuration bugs, scanner pods requested excessive CPU and memory, which prevented efficient scheduling and amplified the resource bottlenecks in the cluster.

• Infrastructure resource limits -- AWS VPC subnet IP and EKS API limits were reached, restricting the cluster's ability to scale and schedule new work.

• Job prioritization and retry inefficiencies -- Inefficiencies in job prioritization and retry logic meant lower priority scans (Trivy, Syft, CCA) competed for capacity and were most affected, while the backlog continued to grow.

Actions Taken

• Increased cluster and node pool capacity.

• Fixed job prioritization to deprioritize reachability scans.

• Capped resource requests for scanner pods to enable efficient scheduling.

• Deployed additional fixes to the scanning platform.

• Opened AWS support tickets to address resource limits.

• Restored monitoring and logging.

• Cleared the job backlog; the queue now processes new jobs as they arrive.

Action Items

• Improve monitoring to better understand the behavior of the processing environment.

• Improve scanning optimization and prioritization for all scan types.

Summary
During the incident, customers experienced delays and temporary disruptions in on demand scans. The issue was caused by a number of redundant SCA scans as well as unoptimized reachability scans. As a result, processing capacity was improperly used for redundant, duplicate, scans. A corrective update for both issues was deployed to stabilize the environment, and the processing environment has since returned to expected performance levels.

Key Timeline (IDT)

• 01.06.2026: Unoptimized code responsible for reachability scans was introduced.

• 03.06.2026: A faulty code responsible for redundant SCA scans was introduced.

• 11.06.2026, 16:00 IDT: Increased processing delays were detected, and an investigation into the scanning service began.

• 11.06.2026, 17:00 IDT: The root cause for redundant SCA scans was identified, and the team began working on improving the behavior.

• 12.06.2026, 10:30 IDT: The root cause of redundant SCA scans was resolved.

• 12.06.2026, 17:00 IDT: The root cause for degraded performance in reachability scans was identified.

• 15.06.2026, 16:00 IDT: A corrective update was deployed to restore the optimization of reachability scans.

• 15.06.2026, 17:00 IDT: System stability was confirmed.

Root Cause
The issue was triggered by a combination of two issues:

• Redundant SCA scans -- Upon receiving a new branch created event from the source code manager, the system attempted to scan all available branches that were configured to be scanned in the repository. In extreme cases, the team has found a magnitude of new scans started instead of one scan, when a branch was created. A faulty code introduced this bug on 03.06.2026 and got resolved on 12.06.2026

• Unoptimized reachability scans -- Reachability scanner in the processing environment, has been configured to scan a set of programming languages. However, due to misconfiguration, the scanner was also attempting to scan programming languages that have not been configured to be scanned. Additionally, the scanner has been running on programming languages that are not stable yet, and in extreme cases, it caused a portion of scans to be stuck until they got timed out.

Actions Taken

• Deployed a corrective update to remove redundant SCA scans.

• Deployed a performance upgrade to reachability scans.

Action Items

• Improve monitoring to better understand the behavior of the processing environment.

• Improve scanning optimization for all scan types.

Summary
During the incident, customers experienced delays and temporary disruptions in scans. The issue was caused by a degraded performance of a process responsible for starting the scans. This means that the processing environment was underutilized even though there were enqueued scans. A corrective update was deployed to stabilize the environment, and the system has since returned to expected performance levels.

Key Timeline (IDT)

• 07.06.2026, 07:00 IDT: Degraded performance of scans began.

• 08.06.2026, 11:00 IDT: Degraded performance was noted and the investigation began.

• 08.06.2026, 13:15 IDT: A bottleneck was identified and a corrective update was deployed.

• 08.06.2026, 14:00 IDT: It was confirmed that the update increased the throughput of the system.

• 09.06.2026, 14:00 IDT: System stability was confirmed, and the system was restored to normal operation.

Root Cause
The issue was triggered by degraded performance of a process responsible for starting scans. This caused the processing environment to be underutilized (even as low as 30% processing capacity), despite there being enqueued scans.

The root cause of the degraded performance has been identified in a race condition when attempting to rerun a failed scan. When attempting to rescan, the system occasionally encountered an error, because the first attempt of a scan failed, and the job was in terminating state. This resulted in extensive retries of the starting the rescans, which caused the degraded performance.

Actions Taken

• Deployed a corrective update to the bottleneck process.

• Restored expected processing performance.

• Improved monitoring to detect degraded performance.

Action Items

• Further improve monitoring to detect degraded performance.

• Further improve the performance of the bottleneck process.

The issue was resolved. The system is fully stable now

Summary

Between April 14 and April 28, 2026, a processing issue occurred within our scanning workflow that prevented a subset of code update events from being fully processed. As a result, some security findings may not have been updated or resolved as expected in the platform. The issue was caused by an update to the processing system that introduced a conflict in how data was written to the database. The issue has been fully resolved, and all affected data has been reprocessed to ensure accuracy.

Key Timeline (IDT)

• April 14, 2026, 09:00 IDT: A new update was deployed to the processing system which introduced the underlying issue.

• April 28, 2026, 15:30 IDT: A subsequent system update was rolled out that inadvertently corrected the processing error.

• May 4, 2026, 11:00 IDT: Internal teams identified reports of inconsistent status updates and began a technical investigation.

• May 6, 2026, 10:00 IDT: A formal incident was initiated to analyze the full scope of the impact and coordinate remediation.

• May 7, 2026, 14:00 IDT: Data collection was completed to identify all repositories and branches that required reprocessing.

• May 8, 2026, 08:00 IDT: Reprocessing of affected data began for several scanning modules.

• May 9, 2026, 18:00 IDT: Initial reprocessing for the majority of modules was successfully completed.

• June 11, 2026, 12:00 IDT: Final reprocessing for all remaining modules was completed, and the incident was officially closed.

Root Cause

The issue was triggered by a change in the update process that attempted to perform multiple database operations simultaneously within the same request. This led to connectivity conflicts and prevented certain background tasks from completing successfully. Consequently, a small portion of events were not recorded, leading to delays in updating the status of findings for customers.

Actions Taken

• Deployed a corrective update to the processing system to ensure stable database interactions.

• Conducted a comprehensive data analysis to identify all events that were missed during the affected period.

• Triggered system-wide rescans for all affected branches to restore the expected state of all findings.

• Verified that all processed updates are now reflecting correctly across the platform.

Action Items

• Enhance system logging to provide better visibility into background processing failures.

• Implement automated alerts for specific error patterns to decrease detection time.

• Improve the scalability of the underlying processing services to handle high volumes more efficiently.

• Develop improved internal tools for bulk data correction and status verification.

Summary
On June 10, 2026, customers may have experienced intermittent issues with their GitHub integrations due to an external authentication incident on GitHub's side. This resulted in some integrations temporarily reporting invalid access tokens and a brief pause in repository syncing and scanning. The issue was resolved once the external provider restored their authentication services. All integrations have automatically returned to normal operation, and no customer action is required.

Key Timeline (IDT)

• June 10, 2026, 18:20 IDT: The external provider began experiencing authentication issues affecting API requests.

• June 10, 2026, 18:20 IDT: Our processing system began receiving intermittent unauthorized responses, leading to temporary integration errors and paused syncing.

• June 10, 2026, 19:39 IDT: The external provider identified and mitigated the faulty component, resolving the incident.

• June 10, 2026, 19:39 IDT: Integrations automatically re-validated, and expected processing behavior was restored.

Root Cause
The incident was caused by an external authentication failure at GitHub. During this window, the provider's API erroneously returned "Unauthorized" responses for a portion of traffic. Our system interpreted these responses as revoked access tokens, which triggered temporary integration error states and paused background workflows.

Actions Taken

• Monitored the external incident status and its impact on our integration workflows.

• Verified that integrations automatically recovered and resumed syncing once the external provider restored service.

• Confirmed that no manual re-authentication was necessary for affected customers.

Action Items

• Improve internal handling of intermittent authentication errors to better distinguish between temporary external outages and actual token revocations.

• Enhance monitoring to more quickly identify when third-party service disruptions impact integration health.

The incident has been resolved. We will provide the RCA shortly.

Summary

Between 16:00 and 17:30 UTC on May 28, we observed an issue where integration connections were intermittently reported as invalid. During this period, the processing of pull requests was paused until connection tokens were successfully refreshed. As a result, some pull requests may have experienced delays or remained in a stuck state. The issue is now resolved, and processing has resumed normally.

Key Timeline (UTC)

• May 28, 16:00 UTC: A high rate of integration connections were reported as invalid, and pull request processing was paused.

• May 28, 17:00 UTC: The external service began returning successful responses, and the system started marking integrations as valid.

• May 28, 17:30 UTC: Connection tokens were successfully refreshed and pull request processing resumed.

Root Cause

The issue was caused by an external service provider returning "no access" responses during a routine validity check. This caused the system to mark integrations as invalid and pause processing. The failures occurred simultaneously across many unrelated accounts and were resolved without any changes on our side, indicating a service disruption on the provider's side.

While the observed behavior clearly points to the external provider, we are continuing to work with GitHub to better understand the underlying cause of this transient failure.

Actions Taken

• Restored expected processing behavior once connection tokens were successfully refreshed.

• Monitored the system to ensure all integrations returned to a valid state.

Action Items

• Improve monitoring to detect similar external service anomalies.

• Add alerting on simultaneous validity-check failures across unrelated accounts.

Summary
Between May 15 and May 28, 2026, a processing delay was identified affecting dependency update workflows for several large accounts. During this period, customers may have experienced significant lag in the time required to process and reflect dependency updates within the system. The issue was caused by an inefficiency in how the database retrieved specific project records, leading to temporary performance degradation. The issue has been fully resolved, and processing speeds have returned to expected levels.

Key Timeline (IDT)
May 17, 2026, 09:00 IDT: Initial reports of increased processing times for dependency updates were observed.
May 24, 2026, 14:30 IDT: System resources were increased to provide temporary relief while the investigation continued.
May 28, 2026, 11:15 IDT: Technical analysis identified a specific database query that was not utilizing the most efficient lookup path.
May 30, 2026, 16:45 IDT: A corrective update to the database indexing structure was deployed.
May 31, 2026, 10:00 IDT: Monitoring confirmed that processing latency returned to sub-millisecond levels and the backlog was cleared.

Root Cause
The root cause was a performance regression in the update workflow’s data retrieval process. The database’s automated query planner began selecting a less efficient path to locate project references. Because the system was searching through a very large volume of records, this inefficient path resulted in the system scanning thousands of unnecessary rows for each update. This led to high disk activity and significant delays, particularly for accounts with a high density of shared dependencies across many projects.

Actions Taken

• Resource Scaling: Temporarily increased database memory and processing power to mitigate the immediate impact on customers.

• Database Optimization: Performed a deep analysis of query execution plans to identify the specific bottleneck.

• Index Refinement: Replaced an existing database index with an optimized version that ensures the query planner always selects the most direct path for data retrieval.

• Validation: Verified the fix across all environments to ensure the new indexing structure supports both data integrity and high-speed lookups.

Action Items

• Enhanced Monitoring: Implement more granular alerts for database query performance to detect similar planning inefficiencies before they impact customers.

• Optimization Standards: Update internal database design guidelines to prevent overlapping index patterns that can confuse automated query planners.

• Performance Testing: Incorporate “cold cache” scenarios into performance testing for large-scale data operations to better simulate real-world disk I/O constraints.

Summary

Between May 15 and May 28, 2026, a processing delay was identified affecting dependency update workflows for several large accounts. During this period, customers may have experienced significant lag in the time required to process and reflect dependency updates within the system. The issue was caused by an inefficiency in how the database retrieved specific project records, leading to temporary performance degradation. The issue has been fully resolved, and processing speeds have returned to expected levels.

Key Timeline (IDT)

May 17, 2026, 09:00 IDT: Initial reports of increased processing times for dependency updates were observed.

May 24, 2026, 14:30 IDT: System resources were increased to provide temporary relief while the investigation continued.

May 28, 2026, 11:15 IDT: Technical analysis identified a specific database query that was not utilizing the most efficient lookup path.

May 30, 2026, 16:45 IDT: A corrective update to the database indexing structure was deployed.

May 31, 2026, 10:00 IDT: Monitoring confirmed that processing latency returned to sub-millisecond levels and the backlog was cleared.

Root Cause

The root cause was a performance regression in the update workflow's data retrieval process. The database's automated query planner began selecting a less efficient path to locate project references. Because the system was searching through a very large volume of records, this inefficient path resulted in the system scanning thousands of unnecessary rows for each update. This led to high disk activity and significant delays, particularly for accounts with a high density of shared dependencies across many projects.

Actions Taken

• Resource Scaling: Temporarily increased database memory and processing power to mitigate the immediate impact on customers.

• Database Optimization: Performed a deep analysis of query execution plans to identify the specific bottleneck.

• Index Refinement: Replaced an existing database index with an optimized version that ensures the query planner always selects the most direct path for data retrieval.

• Validation: Verified the fix across all environments to ensure the new indexing structure supports both data integrity and high-speed lookups.

Action Items

• Enhanced Monitoring: Implement more granular alerts for database query performance to detect similar planning inefficiencies before they impact customers.

• Optimization Standards: Update internal database design guidelines to prevent overlapping index patterns that can confuse automated query planners.

• Performance Testing: Incorporate "cold cache" scenarios into performance testing for large-scale data operations to better simulate real-world disk I/O constraints.

Resolved

Summary
On May 8, 2026, a temporary issue within our internal processing system interrupted the routine renewal of GitLab access credentials for a subset of integrations. This caused affected integrations to stop syncing and appear as disconnected. Because the affected credentials were no longer valid, they could not be restored from our end — each affected integration had to be manually re-authenticated by the customer in order to resume syncing. No customer data was lost or exposed, and no credential security was compromised.

Key Timeline (UTC)
May 8, 2026, 21:10 UTC: A temporary slowdown in the database processing system began affecting credential updates.
May 8, 2026, 21:40 UTC: The system identified that a subset of GitLab integrations were unable to complete their routine credential renewals.
May 8, 2026, 22:30 UTC: The root cause was identified as a failure to save newly issued credentials during the renewal process.
May 8, 2026, 23:30 UTC: Corrective measures were implemented to stabilize the update workflow and prevent further integrations from being affected.
May 9, 2026, 00:40 UTC: The affected integrations were identified, and impacted customers were notified that re-authentication was required to restore them.

Root Cause
The issue was triggered by a temporary interruption in our internal update process. During a routine renewal of access credentials, a brief disruption in the processing system prevented the newly issued credentials from being saved successfully. Because the previous credentials were automatically retired by GitLab as part of the standard security workflow — the moment the new credentials were issued — the affected integrations were left without a valid credential. As the credential was no longer valid and could not be recovered from our end, these integrations could not be restored automatically and required the customer to re-authenticate.

Actions Taken
Stabilized the internal update workflow to prevent further integrations from being affected.
Identified the affected integrations and notified the impacted customers that re-authentication was required.
All affected customers re-authenticated their integrations, fully restoring normal syncing.
Verified that all previously synced data remained intact and secure.

Action Items
Improve monitoring to detect similar processing issues in the update workflow more quickly.
Make credential renewal resilient so a newly issued credential is reliably saved as part of the same operation, and so any save failure is detected immediately — eliminating the window where a renewed credential can be lost and an integration is left unrecoverable.
Optimize the processing system to better handle temporary fluctuations in activity.

Summary

On May 5, 2026, customers in the EU region experienced issues with Custom Dashboards not loading as expected, and some filtering/grouping actions were slower than usual on the Violations page. The issue was caused by a configuration update that included an invalid setting, which prevented the EU analytics data service from operating normally. The service was restored the same evening, and we confirmed no data was lost.

Key Timeline (IDT)

May 5, 2026, 16:51 IDT – A configuration update was deployed to the EU production environment.
May 5, 2026, 19:06 IDT – Monitoring detected availability issues and alerts were triggered.
May 5, 2026, 19:23 IDT – Investigation began.
May 5, 2026, 19:36 IDT – The invalid configuration was identified and confirmed as the cause.
May 5, 2026, 19:40 IDT – A controlled recovery approach was planned to ensure data integrity throughout remediation.
May 5, 2026, 19:50 IDT – Additional safeguards and validation steps were performed prior to remediation, including recovery validation in a non-production environment.
May 5, 2026, 21:45 IDT – A safe recovery procedure was confirmed.
May 5, 2026, 22:05 IDT – Production service was recovered and data accessibility was confirmed.

Root Cause

A configuration update introduced an invalid resource value. While the change initially appeared to apply successfully, it caused repeated failures in the automated update process responsible for keeping the service healthy. After continuing to fail, the process removed the running service components associated with the EU analytics service, leading to service unavailability for customers until restoration was completed.

Actions Taken

• Investigated alerts and isolated the problematic configuration change.

• Performed additional safeguards and validation steps prior to remediation.

• Validated recovery steps in a non-production environment before applying them in production.

• Restored service by safely reattaching existing storage and returning processing to normal operation.

• Confirmed service availability and verified that data remained intact.

Action Items

• Add stronger pre-deployment validation to catch malformed configuration values before rollout.

• Improve monitoring and alerting to detect repeated update failures and destructive actions earlier.

• Implement safeguards to prevent automated update workflows from removing stateful resources for this analytics service during invalid update scenarios.

• Improve operational logging and visibility to speed up diagnosis during similar events.

• Expand and regularly validate backup/restore coverage for the affected analytics stateful components.

A fix supporting both the old and new formats was deployed at 13:00 IST.

The incident has been resolved.