Vendor Status Watch

← all vendors

Secureworks status history

Current state: operational — “All Systems Operational” per https://status.ctpx.secureworks.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

5incidents, last 30 days
13incidents, last 90 days
52incidents on record
Incidents per week, last 12 weeks:

How long do Secureworks incidents last?

3.1 hmedian incident duration51 measured
16.5 h90th percentile1 in 10 ran longer
37 minmedian, major/critical only1 incident

From 51 incidents with a vendor-posted start and resolve time. Longest on record: Charlie: Delayed custom rules for netflow — 6.1 days (2025-11-02 22:30 UTC). Excluded, never estimated: 1 still open / no resolve time. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (52)

StartedIncidentStatusImpactDuration
2026-09-11 00:57 UTCFoxtrot Environment: Detections/Alerts Delayedidentifiednoneopen
2026-09-10 18:12 UTC7 hour detection delay in the Taegis India environmentresolvednone6 h 40 min
2026-08-27 16:10 UTCAlerts are delayed in charlie by upto 40minsresolvednone8 h 54 min
2026-08-18 17:25 UTCPlaybook executions may be delayedresolvednone2 h 54 min
2026-08-18 11:53 UTCPlaybook executions may be delayedresolvednone2 h 43 min
2026-08-06 04:57 UTCFoxtrot athena outageresolvednone2 h 09 min
2026-07-30 14:52 UTCTaegis environments Delta and Foxtrot are currently experiencing ingest lagresolvednone7 h 19 min
2026-07-28 18:34 UTCDetection Search Failures in Charlie Environmentresolvednone23 min
2026-07-23 18:14 UTCOffice 365 Integrations may be impacted by an ongoing Azure issueresolvednone2 h 26 min
2026-07-22 18:20 UTCSome environments (Charlie) have a delay in processing detectionsresolvednone18 h 44 min
2026-07-14 19:10 UTCDetections page is down in Charlieresolvednone2 h 21 min
2026-06-24 15:58 UTCAlert Search Delay in US East 2resolvedminor21 h 04 min
2026-06-18 15:17 UTCMicrosoft Response Actions is a feature degraded in foxtrotresolvednone17 min
2026-05-29 15:57 UTCAzure West US2 Service Degradation for Taegis Defender Endpoint Ingest for Foxtrot Environmentresolvednone6 h 03 min
2026-05-27 10:55 UTCTriage of certain Taegis MDR alerts may be delayedresolvednone3 h 40 min
2026-05-11 21:47 UTCEntra Sign In Events Delayedresolvednone17 h 12 min
2026-05-08 11:23 UTCAlert Triage Delay in Echoresolvednone53 min
2026-05-06 20:15 UTCAn error in the case handling workflow resulted in a delay in case escalations. The impacted cases are being manually re escalatedresolvednone1 h 49 min
2026-05-03 12:37 UTCDelay in Alert, Detections triage in Echo.resolvednone2 h 43 min
2026-04-24 20:58 UTCDelay in Alert Processing for Subset of Alerts in Charlieresolvednone3 h 08 min
2026-04-23 16:49 UTCAll environments: unable to attach alerts to cases (investigations)resolvednone1 h 00 min
2026-04-02 06:00 UTCThere may be an increase in the number of notificationsresolvednone7 h 52 min
2026-04-01 18:35 UTCIssues with login to Taegis Platformresolvednone36 min
2026-04-01 14:33 UTCPlaybook automations may not be running for some customersresolvednone3 h 34 min
2026-03-09 15:11 UTCDelayed customer service responses from @secureworks tagging in case comments in all environmentsresolvednone27 h 24 min
2026-03-04 21:09 UTCNoisy Tactic Graphs Ruleresolvednone16 h 30 min
2026-02-16 00:03 UTCDelay in Alert Processing for Subset of Alerts in Foxtrotresolvednone2 h 04 min
2026-02-13 23:07 UTCDelay in Alert Processing for Subset of Alerts in Charlieresolvednone12 h 20 min
2026-02-07 22:50 UTCError when attempting to view data sources--charlie environment onlyresolvedminor3 h 25 min
2026-02-04 06:50 UTCDetection Delays - US-3 (Foxtrot)resolvednone6 h 15 min
2026-01-22 21:45 UTCDefender Ingestion Delayed approximately one hourresolvednone1 h 50 min
2026-01-21 06:00 UTCDelayed event processing pipeline for process eventsresolvednone0 min
2026-01-21 05:00 UTCInformational: Alert triage delay in Charlie last night - recoveredresolvednone0 min
2026-01-19 19:52 UTCThere may be issues adding detections to casesresolvednone2 h 12 min
2026-01-13 18:03 UTCITDR unresponsive on UIresolvednone18 min
2026-01-08 16:32 UTCIssue with data sources loading in all environment - data flow is unaffectedresolvednone1 h 28 min
2025-12-10 23:13 UTCTaegis Detection Delay in all Environmentsresolvednone7 h 23 min
2025-12-05 09:06 UTCcloudflare outageresolvednone8 min
2025-11-21 14:35 UTCData from Taegis NDR is delayed in all environmentsresolvednone1 h 54 min
2025-11-20 20:55 UTCITDR is down in all regionsresolvednone28 min
2025-11-02 22:30 UTCCharlie: Delayed custom rules for netflowresolvedminor6 d 1 h
2025-10-29 16:55 UTCO365 Ingestion Delayedresolvednone9 h 51 min
2025-10-29 00:16 UTCTaegis Foxtrot Detection Delaysresolvednone12 h 49 min
2025-10-28 17:03 UTCDetection Delays in Foxtrot Environmentresolvednone4 h 23 min
2025-10-20 17:25 UTCCurrent AWS Outage Impeding SOC response timesresolvednone5 h 55 min
2025-10-20 08:29 UTCTaegis Application Disuptionsresolvednone3 h 30 min
2025-10-14 12:54 UTCSecureworks mentions on cases are not creating Zendesk ticketsresolvednone4 h 50 min
2025-10-10 03:42 UTCProblems with search, ingestion and other services in detlaresolvedmajor37 min
2025-10-08 02:25 UTCAll environments: newly created cases (investigations) are not appearing, even though they do existresolvedminor14 h 58 min
2025-10-03 00:59 UTCNDRs in CTPX and DELTA are mistakenly displaying Warning in the Network tab - data is correctresolvednone2 h 15 min
2025-09-25 20:42 UTCEvent processing delays in Taegis Echo environmentresolvednone2 h 29 min
2025-09-19 14:51 UTCTaegis IDR ingestion delays in all environmentsresolvednone6 h 28 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Secureworks with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "secureworks"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}