Secureworks Outage History

Secureworks is up right now

Secureworks had 54 outages in the last 2 years totaling 158h 42m of downtime — averaging 2.2 incidents per month.

There were 54 Secureworks outages since August 13, 2025 totaling 158h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ctpx.secureworks.com/#

Notice July 30, 2026

Taegis environments Delta and Foxtrot are currently experiencing ingest lag

Detected by Pingoru
Jul 30, 2026, 02:52 PM UTC
Resolved
Jul 30, 2026, 10:12 PM UTC
Duration
7h 19m
Timeline · 4 updates
  1. identified Jul 30, 2026, 02:52 PM UTC

    Delta and Foxtrot environments are current experiencing telemetry ingest lag. Users may see delayed detections during this time.

  2. monitoring Jul 30, 2026, 03:41 PM UTC

    We are seeing about an hour delay in alerts in Delta and Foxtrot, but improving. Will continue to monitor.

  3. monitoring Jul 30, 2026, 06:31 PM UTC

    Lag has recovered in the Delta environment. We are still working through backlog in Foxtrot.

  4. resolved Jul 30, 2026, 10:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 28, 2026

Detection Search Failures in Charlie Environment

Detected by Pingoru
Jul 28, 2026, 06:34 PM UTC
Resolved
Jul 28, 2026, 06:57 PM UTC
Duration
23m
Timeline · 2 updates
  1. identified Jul 28, 2026, 06:34 PM UTC

    Taegis XDR users in the Charlie environment maybe experiencing intermittent detection search failures. We have identified the problem and working on a fix.

  2. resolved Jul 28, 2026, 06:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 23, 2026

Office 365 Integrations may be impacted by an ongoing Azure issue

Detected by Pingoru
Jul 23, 2026, 06:14 PM UTC
Resolved
Jul 23, 2026, 08:40 PM UTC
Duration
2h 26m
Timeline · 2 updates
  1. investigating Jul 23, 2026, 06:14 PM UTC

    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

  2. resolved Jul 23, 2026, 08:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 22, 2026

Some environments (Charlie) have a delay in processing detections

Detected by Pingoru
Jul 22, 2026, 06:20 PM UTC
Resolved
Jul 23, 2026, 01:05 PM UTC
Duration
18h 44m
Timeline · 3 updates
  1. investigating Jul 22, 2026, 06:20 PM UTC

    We are actively investigating a potential detections issue in Charlie. ---------------------------------------------------------------------------------------- 現在、Charlieにおける検知に関する潜在的な問題について、積極的に調査を行っています。

  2. investigating Jul 22, 2026, 07:11 PM UTC

    We are investigating a delay in processing detections ---------------------------------------------------------- 検知結果の処理に遅延が発生していることを調査中です。

  3. resolved Jul 23, 2026, 01:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 14, 2026

Detections page is down in Charlie

Detected by Pingoru
Jul 14, 2026, 07:10 PM UTC
Resolved
Jul 14, 2026, 09:31 PM UTC
Duration
2h 21m
Timeline · 5 updates
  1. investigating Jul 14, 2026, 07:10 PM UTC

    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

  2. identified Jul 14, 2026, 07:10 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jul 14, 2026, 07:27 PM UTC

    We are continuing to work on a fix for this issue.

  4. identified Jul 14, 2026, 08:32 PM UTC

    A fix has been applied and we are monitoring the results.

  5. resolved Jul 14, 2026, 09:31 PM UTC

    All the systems are operational and the alert / detections backlog has been cleared.

Read the full incident report →

Minor June 24, 2026

Alert Search Delay in US East 2

Detected by Pingoru
Jun 24, 2026, 03:58 PM UTC
Resolved
Jun 25, 2026, 01:02 PM UTC
Duration
21h 4m
Timeline · 4 updates
  1. investigating Jun 24, 2026, 03:58 PM UTC

    We are aware of a delay in alert search in US East 2 - Charlie and are working on a fix

  2. investigating Jun 24, 2026, 06:51 PM UTC

    We're continuing to work through the Alert Search outage, and are attempting actions to mitigate the issue

  3. monitoring Jun 25, 2026, 02:03 AM UTC

    A fix has been applied and we are monitoring the results. There may be some delays in triaged alerts while the backlog is processed.

  4. resolved Jun 25, 2026, 01:02 PM UTC

    The alert backlog has been cleared and service has been restored

Read the full incident report →

Notice June 18, 2026

Microsoft Response Actions is a feature degraded in foxtrot

Detected by Pingoru
Jun 18, 2026, 03:17 PM UTC
Resolved
Jun 18, 2026, 03:34 PM UTC
Duration
17m
Timeline · 2 updates
  1. investigating Jun 18, 2026, 03:17 PM UTC

    Microsoft Response Actions is a feature that allows MDR analysts and XDR customers to take containment actions is degraded in foxtrot region

  2. resolved Jun 18, 2026, 03:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 29, 2026

Azure West US2 Service Degradation for Taegis Defender Endpoint Ingest for Foxtrot Environment

Detected by Pingoru
May 29, 2026, 03:57 PM UTC
Resolved
May 29, 2026, 10:01 PM UTC
Duration
6h 3m
Timeline · 2 updates
  1. monitoring May 29, 2026, 03:57 PM UTC

    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.

  2. resolved May 29, 2026, 10:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 27, 2026

Triage of certain Taegis MDR alerts may be delayed

Detected by Pingoru
May 27, 2026, 10:55 AM UTC
Resolved
May 27, 2026, 02:35 PM UTC
Duration
3h 40m
Timeline · 4 updates
  1. investigating May 27, 2026, 10:55 AM UTC

    A small subset of Taegis MDR customers may have triage delayed, we are currently investigating the issue

  2. monitoring May 27, 2026, 11:15 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring May 27, 2026, 11:20 AM UTC

    Triage backlog for a small subset of Taegis MDR customers is currently being worked through

  4. resolved May 27, 2026, 02:35 PM UTC

    All delays have been resolved.

Read the full incident report →

Notice May 11, 2026

Entra Sign In Events Delayed

Detected by Pingoru
May 11, 2026, 09:47 PM UTC
Resolved
May 12, 2026, 02:59 PM UTC
Duration
17h 12m
Timeline · 3 updates
  1. identified May 11, 2026, 09:47 PM UTC

    We are investigating a delay in Entra sign in event ingestion, the team is actively investigating this.

  2. monitoring May 11, 2026, 11:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 12, 2026, 02:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 8, 2026

Alert Triage Delay in Echo

Detected by Pingoru
May 08, 2026, 11:23 AM UTC
Resolved
May 08, 2026, 12:16 PM UTC
Duration
53m
Timeline · 3 updates
  1. investigating May 08, 2026, 11:23 AM UTC

    We are aware of a delay in alert triaging in Echo and are working on a fix.

  2. identified May 08, 2026, 11:33 AM UTC

    The issue has been found and we're deploying a solution

  3. resolved May 08, 2026, 12:16 PM UTC

    The issue has been resolved and triage is continuing as usual

Read the full incident report →

Notice May 3, 2026

Delay in Alert, Detections triage in Echo.

Detected by Pingoru
May 03, 2026, 12:37 PM UTC
Resolved
May 03, 2026, 03:21 PM UTC
Duration
2h 43m
Timeline · 2 updates
  1. investigating May 03, 2026, 12:37 PM UTC

    We are actively looking into the delay in Alert / Detections triage in Echo.

  2. resolved May 03, 2026, 03:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 23, 2026

All environments: unable to attach alerts to cases (investigations)

Detected by Pingoru
Apr 23, 2026, 04:49 PM UTC
Resolved
Apr 23, 2026, 05:50 PM UTC
Duration
1h
Timeline · 3 updates
  1. identified Apr 23, 2026, 04:49 PM UTC

    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.

  2. monitoring Apr 23, 2026, 05:10 PM UTC

    A fix has been deployed. We are monitoring to verify that all function is restored.

  3. resolved Apr 23, 2026, 05:50 PM UTC

    Issue is fixed.

Read the full incident report →

Notice April 2, 2026

There may be an increase in the number of notifications

Detected by Pingoru
Apr 02, 2026, 06:00 AM UTC
Resolved
Apr 02, 2026, 01:53 PM UTC
Duration
7h 52m
Timeline · 3 updates
  1. investigating Apr 02, 2026, 06:00 AM UTC

    There may be an increase in notifications due to automations catching up after processing a backlog of automation jobs. ------------------------------------------------------------------------------------------------------------------------- 自動化ジョブの未処理分(バックログ)の処理が完了し、自動化システムが通常の状態に復帰する過程で、通知が増加する可能性があります。

  2. monitoring Apr 02, 2026, 06:01 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 02, 2026, 01:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 1, 2026

Issues with login to Taegis Platform

Detected by Pingoru
Apr 01, 2026, 06:35 PM UTC
Resolved
Apr 01, 2026, 07:12 PM UTC
Duration
36m
Timeline · 2 updates
  1. investigating Apr 01, 2026, 06:35 PM UTC

    Please use incognito to log into the Taegis platform if you experience login issues. ------------------------------------------------------------------------------------ ログインに関する問題が発生した場合は、シークレットモードを使用してTaegisプラットフォームにログインしてください。

  2. resolved Apr 01, 2026, 07:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 1, 2026

Playbook automations may not be running for some customers

Detected by Pingoru
Apr 01, 2026, 02:33 PM UTC
Resolved
Apr 01, 2026, 06:08 PM UTC
Duration
3h 34m
Timeline · 2 updates
  1. investigating Apr 01, 2026, 02:33 PM UTC

    Playbook automations may not be running for some customers. We are looking into the issue. ------------------------------------------------------------------------------------------------ 一部のお客様において、プレイブックの自動化が実行されていない可能性があります。現在、本件について調査を行っております。

  2. resolved Apr 01, 2026, 06:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 9, 2026

Delayed customer service responses from @secureworks tagging in case comments in all environments

Detected by Pingoru
Mar 09, 2026, 03:11 PM UTC
Resolved
Mar 10, 2026, 06:36 PM UTC
Duration
1d 3h
Timeline · 4 updates
  1. investigating Mar 09, 2026, 03:11 PM UTC

    We are currently experiencing Zendesk ticket creation from @secureworks comments. Users may have delayed responses to inquires during this time. We are working to correct the situation.

  2. investigating Mar 09, 2026, 03:35 PM UTC

    Assigning via the "Assignee" field may also be affected. Team is still working toward a solution.

  3. monitoring Mar 10, 2026, 01:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 10, 2026, 06:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 4, 2026

Noisy Tactic Graphs Rule

Detected by Pingoru
Mar 04, 2026, 09:09 PM UTC
Resolved
Mar 05, 2026, 01:40 PM UTC
Duration
16h 30m
Timeline · 2 updates
  1. monitoring Mar 04, 2026, 09:09 PM UTC

    We are aware of a Tactic Graphs rule (multipleuasessions:9ad0d0a6-a99a-11f0-9000-7261c747c745) that has caused an increased detection volume. At this time, the rule has been disabled and will be evaluated for further tuning.

  2. resolved Mar 05, 2026, 01:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 7, 2026

Error when attempting to view data sources--charlie environment only

Detected by Pingoru
Feb 07, 2026, 10:50 PM UTC
Resolved
Feb 08, 2026, 02:16 AM UTC
Duration
3h 25m
Timeline · 2 updates
  1. identified Feb 07, 2026, 10:50 PM UTC

    Users may see an error message when attempting to view data sources in the charlie environment. Data continues to flow and alerts/detections are unaffected. Engineering is working on identifying and fixing the issue.

  2. resolved Feb 08, 2026, 02:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 4, 2026

Detection Delays - US-3 (Foxtrot)

Detected by Pingoru
Feb 04, 2026, 06:50 AM UTC
Resolved
Feb 04, 2026, 01:05 PM UTC
Duration
6h 15m
Timeline · 2 updates
  1. monitoring Feb 04, 2026, 06:50 AM UTC

    Detections are delayed in US-3 by approximately 1 hour. We have fixed the cause of the issue and are now monitoring as we process the backlog.

  2. resolved Feb 04, 2026, 01:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 22, 2026

Defender Ingestion Delayed approximately one hour

Detected by Pingoru
Jan 22, 2026, 09:45 PM UTC
Resolved
Jan 22, 2026, 11:35 PM UTC
Duration
1h 50m
Timeline · 3 updates
  1. identified Jan 22, 2026, 09:45 PM UTC

    The ingestion of Defender events is delayed approximately one hour. The issue has been identified and is currently being fixed.

  2. identified Jan 22, 2026, 11:35 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Jan 22, 2026, 11:35 PM UTC

    This incident has been resolved.

Read the full incident report →