Secureworks Outage History

Secureworks is up right now

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

There were 54 Secureworks outages since June 16, 2025 totaling 119h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

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 →

Notice January 19, 2026

There may be issues adding detections to cases

Detected by Pingoru
Jan 19, 2026, 07:52 PM UTC
Resolved
Jan 19, 2026, 10:05 PM UTC
Duration
2h 12m
Timeline · 2 updates
  1. investigating Jan 19, 2026, 07:52 PM UTC

    Some users are experiencing issues adding detections to cases. This is being looked into.

  2. resolved Jan 19, 2026, 10:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 13, 2026

ITDR unresponsive on UI

Detected by Pingoru
Jan 13, 2026, 06:03 PM UTC
Resolved
Jan 13, 2026, 06:22 PM UTC
Duration
18m
Timeline · 3 updates
  1. investigating Jan 13, 2026, 06:03 PM UTC

    We are aware of an issue affecting our authentication between platforms that is affecting ITDR and XDR EAP customers

  2. monitoring Jan 13, 2026, 06:12 PM UTC

    A rollback was made and service should be returning shortly

  3. resolved Jan 13, 2026, 06:22 PM UTC

    Incident has been resolved and service has been restored

Read the full incident report →

Notice December 10, 2025

Taegis Detection Delay in all Environments

Detected by Pingoru
Dec 10, 2025, 11:13 PM UTC
Resolved
Dec 11, 2025, 06:36 AM UTC
Duration
7h 23m
Timeline · 4 updates
  1. identified Dec 10, 2025, 11:13 PM UTC

    All Taegis environments are currently experiencing a detection delay. Team has identified the issue and is implementing a fix.

  2. monitoring Dec 11, 2025, 12:38 AM UTC

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

  3. monitoring Dec 11, 2025, 02:10 AM UTC

    We are still experiencing delays in the Taegis Foxtrot environment. All other environments have recovered. We'll continue to monitor the situation.

  4. resolved Dec 11, 2025, 06:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 5, 2025

cloudflare outage

Detected by Pingoru
Dec 05, 2025, 09:06 AM UTC
Resolved
Dec 05, 2025, 09:15 AM UTC
Duration
8m
Timeline · 2 updates
  1. monitoring Dec 05, 2025, 09:06 AM UTC

    There is currently an incident with Cloudflare - you may have difficulty reaching support until it is resolved.

  2. resolved Dec 05, 2025, 09:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 21, 2025

Data from Taegis NDR is delayed in all environments

Detected by Pingoru
Nov 21, 2025, 02:35 PM UTC
Resolved
Nov 21, 2025, 04:29 PM UTC
Duration
1h 54m
Timeline · 3 updates
  1. investigating Nov 21, 2025, 02:35 PM UTC

    Engineering is investigating an issue where Taegis NDR data is delayed in all environments.

  2. identified Nov 21, 2025, 02:46 PM UTC

    Engineering has identified the issue and is deploying a fix across all environments. Alerts on data originating from data originating from Taegis NDR are delayed.

  3. resolved Nov 21, 2025, 04:29 PM UTC

    The engineering team has rolled back a faulty change that was causing NDR data processing to fail. Alerts were delayed, bu no NDR data was lost. The backlog has been processed, and all services are now operating normally.

Read the full incident report →