Secureworks had 50 outages in the last 2 years totaling 838h 4m of downtime — averaging 2.1 incidents per month.
There were 50 Secureworks outages since October 8, 2025 totaling 838h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some Taegis Echo users may see a 47min delay in detections. Taegis engineering is working to reduce this lag.
This incident has been resolved.
Processing is likely to be slow through the weekend.
The issue is resolved.
ITDR customers had new checks rolled out which prematurely created a large number of findings, detections and cases. These checks have been rolled back and detections and cases will be triaged. Customers may experience brief interruptions to playbook execution and detection linking to cases.
This incident has been resolved.
Some detections/Alerts in the foxtrot environment are delayed by up to three hours. Engineering is working to address the issue and process the backlog.
This incident has been resolved.
Taegis users in the India environment maybe experiencing a detection delay of up to 7h hours. We are working on removing this delay.
Detections/Alerts in the India environment are not processing normally.
Alerts are delayed in charlie by upto 40mins. We are closely monitoring the situation
This incident has been resolved.
Playbook executions may be delayed --------------------------------------- プレイブックの実行が遅延する可能性があります。
This incident has been resolved.
Event searches in Foxtrot are currently being affected by an outage at our upstream provider
We are waiting on the upstream provider for additional details.
This incident has been resolved by the upstream provider.
Delta and Foxtrot environments are current experiencing telemetry ingest lag. Users may see delayed detections during this time.
We are seeing about an hour delay in alerts in Delta and Foxtrot, but improving. Will continue to monitor.
Lag has recovered in the Delta environment. We are still working through backlog in Foxtrot.
This incident has been resolved.
Taegis XDR users in the Charlie environment maybe experiencing intermittent detection search failures. We have identified the problem and working on a fix.
This incident has been resolved.
Due to an ongoing Azure issue, Office 365 integrations may be impacted https://azure.status.microsoft/en-us/status ---------------------------------------------------------------------------------------------------------------------- 現在発生しているAzureの障害により、Office 365との連携に影響が及ぶ可能性があります。 https://azure.status.microsoft/en-us/status
This incident has been resolved.
We are actively investigating a potential detections issue in Charlie. ---------------------------------------------------------------------------------------- 現在、Charlieにおける検知に関する潜在的な問題について、積極的に調査を行っています。
We are investigating a delay in processing detections ---------------------------------------------------------- 検知結果の処理に遅延が発生していることを調査中です。
This incident has been resolved.
We have identified an issue on Detections page and are actively working on getting the services restored. Please note there will be a delay in triage
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been applied and we are monitoring the results.
All the systems are operational and the alert / detections backlog has been cleared.
We are aware of a delay in alert search in US East 2 - Charlie and are working on a fix
We're continuing to work through the Alert Search outage, and are attempting actions to mitigate the issue
A fix has been applied and we are monitoring the results. There may be some delays in triaged alerts while the backlog is processed.
The alert backlog has been cleared and service has been restored
Microsoft Response Actions is a feature that allows MDR analysts and XDR customers to take containment actions is degraded in foxtrot region
This incident has been resolved.
We are currently monitoring a service degradation with Azure West US2 region. See https://app.azure.com/h/GHRP-84G/cc42f5 for Microsoft outage details. This issue is affecting Taegis MS Defender endpoint ingestion in the foxtrot environment. We will be monitoring the situation.
This incident has been resolved.
A small subset of Taegis MDR customers may have triage delayed, we are currently investigating the issue
A fix has been implemented and we are monitoring the results.
Triage backlog for a small subset of Taegis MDR customers is currently being worked through
All delays have been resolved.
We are investigating a delay in Entra sign in event ingestion, the team is actively investigating this.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of a delay in alert triaging in Echo and are working on a fix.
The issue has been found and we're deploying a solution
The issue has been resolved and triage is continuing as usual
We are currently investigating this issue.
This incident has been resolved.
We are actively looking into the delay in Alert / Detections triage in Echo.
This incident has been resolved.
There is a delay in processing a subset of Alerts in Charlie and we are actively working on it
This incident has been resolved.
Currently users are unable attach alerts to cases (investigations). Our engineers have identified the cause and are working on deploying a fix. Alerting is still functioning, and there is no data loss risk.
A fix has been deployed. We are monitoring to verify that all function is restored.
Issue is fixed.
There may be an increase in notifications due to automations catching up after processing a backlog of automation jobs. ------------------------------------------------------------------------------------------------------------------------- 自動化ジョブの未処理分（バックログ）の処理が完了し、自動化システムが通常の状態に復帰する過程で、通知が増加する可能性があります。
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Please use incognito to log into the Taegis platform if you experience login issues. ------------------------------------------------------------------------------------ ログインに関する問題が発生した場合は、シークレットモードを使用してTaegisプラットフォームにログインしてください。
This incident has been resolved.