Secureworks Outage History

Started Apr 01, 2026, 02:33 PM UTC· resolved Apr 01, 2026, 06:08 PM UTC

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 →

Started Mar 09, 2026, 03:11 PM UTC· resolved Mar 10, 2026, 06:36 PM UTC

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 →

Started Mar 04, 2026, 09:09 PM UTC· resolved Mar 05, 2026, 01:40 PM UTC

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 →

Started Feb 16, 2026, 12:03 AM UTC· resolved Feb 16, 2026, 02:07 AM UTC

1. investigating Feb 16, 2026, 12:03 AM UTC

   A subset of alerts experienced a delay and we are monitoring for recovery.

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

   This incident has been resolved.

Read the full incident report →

Started Feb 07, 2026, 10:50 PM UTC· resolved Feb 08, 2026, 02:16 AM UTC

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 →

Started Feb 04, 2026, 06:50 AM UTC· resolved Feb 04, 2026, 01:05 PM UTC

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 →

Started Jan 22, 2026, 09:45 PM UTC· resolved Jan 22, 2026, 11:35 PM UTC

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 →

Started Jan 21, 2026, 06:00 AM UTC· resolved Jan 21, 2026, 06:00 AM UTC

1. resolved Jan 21, 2026, 02:35 PM UTC

   Some users may have experienced delayed processing of process events. This issue is now resolved and all events are processing normally.

Read the full incident report →

Started Jan 21, 2026, 05:00 AM UTC· resolved Jan 21, 2026, 05:00 AM UTC

1. resolved Jan 21, 2026, 02:38 PM UTC

   Alerts were delayed last night by up to 5 hours. The issue was resolved at about 5 AM ET.

Read the full incident report →

Started Jan 19, 2026, 07:52 PM UTC· resolved Jan 19, 2026, 10:05 PM UTC

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 →

Started Jan 13, 2026, 06:03 PM UTC· resolved Jan 13, 2026, 06:22 PM UTC

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 →

Started Jan 08, 2026, 04:32 PM UTC· resolved Jan 08, 2026, 06:01 PM UTC

1. identified Jan 08, 2026, 04:32 PM UTC

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

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

   This incident has been resolved.

Read the full incident report →

Started Dec 10, 2025, 11:13 PM UTC· resolved Dec 11, 2025, 06:36 AM UTC

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 →

Started Dec 05, 2025, 09:06 AM UTC· resolved Dec 05, 2025, 09:15 AM UTC

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 →

Started Nov 21, 2025, 02:35 PM UTC· resolved Nov 21, 2025, 04:29 PM UTC

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 →

Started Nov 20, 2025, 08:55 PM UTC· resolved Nov 20, 2025, 09:23 PM UTC

1. investigating Nov 20, 2025, 08:55 PM UTC

   ITDR is down in all regions. Engineering is actively investigating.

2. monitoring Nov 20, 2025, 09:00 PM UTC

   Engineering identified a breaking change that was rolled back. Service is restored.

3. resolved Nov 20, 2025, 09:23 PM UTC

   Service restoration confirmed. ITDR is operational.

Read the full incident report →

Started Nov 02, 2025, 10:30 PM UTC· resolved Nov 09, 2025, 12:06 AM UTC

1. investigating Nov 02, 2025, 10:30 PM UTC

   We are currently investigating a delay with custom rules on Netflow events.

2. identified Nov 02, 2025, 10:57 PM UTC

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

3. monitoring Nov 04, 2025, 07:09 PM UTC

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

4. resolved Nov 09, 2025, 12:06 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 04:55 PM UTC· resolved Oct 30, 2025, 02:47 AM UTC

1. investigating Oct 29, 2025, 04:55 PM UTC

   O365 Ingestion and integration telemetry may be delayed due to a Microsoft Azure outage: https://status.cloud.microsoft/. ITDR Customers may also experience errors adding a new provider in addition to the ingestion.

2. monitoring Oct 29, 2025, 10:59 PM UTC

   We are seeing improvements in service integrations as Azure services slowly return, we are continuing to monitor ingest

3. resolved Oct 30, 2025, 02:47 AM UTC

   This incident has been resolved. We will continue monitoring for any changes in behavior

Read the full incident report →

Started Oct 29, 2025, 12:16 AM UTC· resolved Oct 29, 2025, 01:06 PM UTC

1. identified Oct 29, 2025, 12:16 AM UTC

   Users in the Taegis Foxtrot environment may be experiencing continued delays for all detections. Team is working to reduce this delay.

2. monitoring Oct 29, 2025, 12:49 AM UTC

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

3. resolved Oct 29, 2025, 01:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 28, 2025, 05:03 PM UTC· resolved Oct 28, 2025, 09:26 PM UTC

1. identified Oct 28, 2025, 05:03 PM UTC

   Taegis users in the Foxtrot environment maybe seeing delayed detections. The issue has been identified and a fix is being implemented to reduce current lag.

2. monitoring Oct 28, 2025, 09:12 PM UTC

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

3. resolved Oct 28, 2025, 09:26 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 05:25 PM UTC· resolved Oct 20, 2025, 11:20 PM UTC

1. monitoring Oct 20, 2025, 05:25 PM UTC

   Taegis SecOps working through a high backlog due to the AWS outage that's happening today. Expect delays with ZenDesk responses and other interactions with SOC.

2. monitoring Oct 20, 2025, 06:22 PM UTC

   We're also seeing delays in Red Cloak endpoint telemetry ingestion due to current AWS outage. Team will continue to monitor the situation.

3. resolved Oct 20, 2025, 11:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 08:29 AM UTC· resolved Oct 20, 2025, 12:00 PM UTC

1. monitoring Oct 20, 2025, 08:29 AM UTC

   AWS is currently experiencing an outage in the US-EAST-1 region. Teagis users may be seeing login errors or degraded performance at this time. We will be monitoring the situation reported at https://health.aws.amazon.com/health/status

2. resolved Oct 20, 2025, 12:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 14, 2025, 12:54 PM UTC· resolved Oct 14, 2025, 05:45 PM UTC

1. investigating Oct 14, 2025, 12:54 PM UTC

   Secureworks mentions on cases are not creating Zendesk tickets --------------------------------------------------------------------- ケースのSecureworksの言及がZendeskチケットを作成しない

2. resolved Oct 14, 2025, 05:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 10, 2025, 03:42 AM UTC· resolved Oct 10, 2025, 04:19 AM UTC

1. investigating Oct 10, 2025, 03:42 AM UTC

   Engineering is investigating an incident that is impacting a wide range of services in the delta environment.

2. investigating Oct 10, 2025, 03:42 AM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 10, 2025, 03:55 AM UTC

   Engineering identified an issue with a supporting service that allows our services to access underlying infrastructure. The underlying service was recycled, and services are now restored.

4. resolved Oct 10, 2025, 04:19 AM UTC

   Engineering has confirmed that services in delta are now functioning.

Read the full incident report →

Started Oct 08, 2025, 02:25 AM UTC· resolved Oct 08, 2025, 05:23 PM UTC

1. investigating Oct 08, 2025, 02:25 AM UTC

   Users are reporting that newly created cases (investigations) are not appearing, even thought they have been created. Engineering is investigating. As a workaround, users can expand Created, In Range search--suggest 1 day before and after--and the case should appear.

2. investigating Oct 08, 2025, 01:14 PM UTC

   Engineering is continuing to investigate the root cause of this issue. As an alternative workaround, users may wish to go to User Profile & Settings -> Time Zone and set their profile time zone to UTC.

3. identified Oct 08, 2025, 02:32 PM UTC

   Our engineering team has identified a bug in the Taegis user interface. They are working on a bug fix.

4. resolved Oct 08, 2025, 05:23 PM UTC

   The engineering team deployed an update to the UI that makes it clearer how the default date filter functions. (No code/logic change was necessary.)

Read the full incident report →