Red Canary Outage History

Started Oct 15, 2026, 03:14 AM UTC· resolved Oct 15, 2026, 05:12 AM UTC

1. investigating Oct 15, 2026, 03:14 AM UTC

   We are currently experiencing data processing delays, resulting in late detection notification to some customers. This incident will be updated as additional information becomes available.

2. identified Oct 15, 2026, 03:19 AM UTC

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

3. identified Oct 15, 2026, 03:43 AM UTC

   Telemetry is delayed and systems are degraded as we continue to work on a fix for this issue.

4. resolved Oct 15, 2026, 05:12 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 07:07 PM UTC· resolved Jun 30, 2026, 02:44 AM UTC

1. identified Jun 29, 2026, 07:07 PM UTC

   The issue has been identified and we are currently working on a fix.

2. monitoring Jun 30, 2026, 01:46 AM UTC

   A fix has been implemented and we are monitoring results.

3. monitoring Jun 30, 2026, 02:44 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Jun 30, 2026, 02:44 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 16, 2026, 08:13 PM UTC· resolved May 16, 2026, 08:49 PM UTC

1. identified May 16, 2026, 08:13 PM UTC

   Threat detection for our Government CrowdStrike customers may be delayed due to an incident with CrowdStrike’s Falcon Data Replicator. This incident will be updated as additional information becomes available from CrowdStrike.

2. identified May 16, 2026, 08:17 PM UTC

   Threat detection for our Government CrowdStrike customers may be delayed due to an incident with CrowdStrike’s Falcon Data Replicator. This incident will be updated as additional information becomes available from CrowdStrike.

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

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 10:40 PM UTC· resolved May 09, 2026, 05:46 AM UTC

1. investigating May 08, 2026, 10:40 PM UTC

   We are investigating an issue impacting AWS ingestors, which is causing a delay in our processing of Cloudtrail and GuardDuty alerts.

2. identified May 08, 2026, 11:07 PM UTC

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

3. resolved May 09, 2026, 05:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 08, 2026, 07:50 PM UTC· resolved Apr 08, 2026, 10:16 PM UTC

1. monitoring Apr 08, 2026, 07:50 PM UTC

   We are currently investigating reports of intermittent detection delays. The issue has been identified and a fix has been implemented. We are monitoring the system to confirm that it is returning to normal operations.

2. resolved Apr 08, 2026, 10:16 PM UTC

   Monitoring has confirmed the system is operating normally and detections are no longer delayed.

Read the full incident report →

Started Apr 06, 2026, 11:26 PM UTC· resolved Apr 07, 2026, 03:34 AM UTC

1. investigating Apr 06, 2026, 11:26 PM UTC

   We are investigating delayed telemetry surrounding Google Cloud Platform data due to underlying issues in the AWS Cloud Platform. We have notified the AWS production engineering team and are monitoring the issue to ensure they resolve the issue promptly. Telemetry, events, and detections may be delayed in our Web Portal, APIs, and systems that leverage those APIs such as Canary Exporter for GCP telemetry.

2. monitoring Apr 07, 2026, 02:19 AM UTC

   We are monitoring the system to confirm that it is returning to normal operations.

3. resolved Apr 07, 2026, 03:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 04, 2025, 10:33 PM UTC· resolved Dec 05, 2025, 01:56 AM UTC

1. monitoring Dec 04, 2025, 10:33 PM UTC

   We are investigating ingestion issues with VMware Carbon Black Response services hosted by Red Canary. Sensor telemetry, events, and detections may be delayed in our Web Portal, APIs, and systems that leverage those APIs such as Canary Exporter. New sensor connections and installations may be impacted. The issue has been identified and a fix is being implemented. We are monitoring the system to confirm that it is returning to normal operations.

2. resolved Dec 05, 2025, 01:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 11, 2025, 12:33 PM UTC· resolved Nov 11, 2025, 12:57 PM UTC

1. monitoring Nov 11, 2025, 12:33 PM UTC

   We are currently experiencing data processing delays, resulting in late detection notification to some customers.

2. resolved Nov 11, 2025, 12:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 31, 2025, 06:17 PM UTC· resolved Nov 01, 2025, 12:28 PM UTC

1. identified Oct 31, 2025, 06:17 PM UTC

   We have identified an issue that is causing intermittent delays in processing cloud and identity data. We are actively working on a fix. Detections may be delayed.

2. identified Oct 31, 2025, 09:55 PM UTC

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

3. resolved Nov 01, 2025, 12:28 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 05:16 PM UTC· resolved Oct 29, 2025, 10:18 PM UTC

1. investigating Oct 29, 2025, 05:16 PM UTC

   We are aware of a reported degradation with the manage.office.com domain that is impacting some Microsoft Office 365 services. At this time telemetry and detections for Microsoft Office 365 External Service Integrations may be delayed.

2. monitoring Oct 29, 2025, 09:43 PM UTC

   Microsoft Office 365 external service integrations are now functioning as expected. Detections may be delayed as we process the backlog.

3. resolved Oct 29, 2025, 10:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 27, 2025, 09:06 PM UTC· resolved Oct 27, 2025, 10:18 PM UTC

1. identified Oct 27, 2025, 09:06 PM UTC

   We identified an issue impacting data processing for Google Workspace customers and have implemented a fix. Detections may be delayed.

2. resolved Oct 27, 2025, 10:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 04:38 PM UTC· resolved Oct 20, 2025, 10:55 PM UTC

1. monitoring Oct 20, 2025, 04:38 PM UTC

   We are aware of a reported AWS degradation that may be impacting some services. At this time, telemetry for Jamf Threat Defense and VMware Carbon Black Response, hosted by Red Canary, may experience delays. We have observed signs of recovery in the affected services and continue to monitor the situation closely.

2. resolved Oct 20, 2025, 10:55 PM UTC

   This incident has been resolved. Services are operating as expected.

Read the full incident report →

Started Oct 15, 2025, 09:20 PM UTC· resolved Oct 16, 2025, 12:56 AM UTC

1. investigating Oct 15, 2025, 09:20 PM UTC

   We are currently investigating an issue with some pages being unavailable in the Red Canary portal. We will update this incident as more information becomes available.

2. identified Oct 15, 2025, 09:55 PM UTC

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

3. monitoring Oct 15, 2025, 11:31 PM UTC

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

4. resolved Oct 16, 2025, 12:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 18, 2025, 06:18 PM UTC· resolved Sep 18, 2025, 06:40 PM UTC

1. identified Sep 18, 2025, 06:18 PM UTC

   We have identified an issue that is causing the Red Canary web portal and API requests to return errors intermittently for some customers. We are implementing a fix and will update this incident upon resolution of the impact.

2. resolved Sep 18, 2025, 06:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 10, 2025, 05:39 PM UTC· resolved Sep 10, 2025, 06:30 PM UTC

1. identified Sep 10, 2025, 05:39 PM UTC

   We have identified an issue that may be causing a degraded portal experience for our customers. Some portal pages may be slower to respond or appear missing. A fix has been identified and is currently being implemented and tested. We will provide more information as soon as possible.

2. resolved Sep 10, 2025, 06:30 PM UTC

   Our fix has been implemented, tested, and deployed. We've validated the portal is no longer degraded and pages that may have appeared to be missing are present.

Read the full incident report →

Started Aug 13, 2025, 08:49 PM UTC· resolved Aug 14, 2025, 07:02 PM UTC

1. identified Aug 13, 2025, 08:49 PM UTC

   SentinelOne declared an incident earlier today that has caused delays in receiving data from their platform: https://status.sentinelone.com/incidents/b03z8dft06hs We have engaged SentinelOne to determine how large their backlogs are and when we can expect to see data flow resume. We will update this incident as we learn more. Detections based on SentinelOne data may be delayed.

2. resolved Aug 14, 2025, 07:02 PM UTC

   This incident has been resolved. SentinelOne has fixed the issue on their end, processed their backlog, and we are receiving data again.

Read the full incident report →

Started Aug 12, 2025, 03:35 PM UTC· resolved Aug 12, 2025, 05:38 PM UTC

1. investigating Aug 12, 2025, 03:35 PM UTC

   We are currently observing errors with Broadcom VMware Carbon Black Cloud's alert APIs. Ingestion of CBC alerts are currently failing. We have engaged CBC to determine the cause of the errors and will post more information here as we get it. Detections based on CBC alerts may be delayed.

2. resolved Aug 12, 2025, 05:38 PM UTC

   We have determined the errors are due to a configuration change with CBC that required customers to make changes to their environments. Therefore this affects a small percentage of our customers and we are engaging with them directly to make the required changes.

Read the full incident report →

Started Jul 18, 2025, 04:31 PM UTC· resolved Jul 18, 2025, 07:46 PM UTC

1. investigating Jul 18, 2025, 04:31 PM UTC

   We are tracking an outage with Broadcom that is affecting authentication to Carbon Black Cloud environments. Active Remediation response actions may be delayed.

2. investigating Jul 18, 2025, 04:39 PM UTC

   We are continuing to investigate this issue.

3. investigating Jul 18, 2025, 04:45 PM UTC

   We are continuing to investigate this issue.

4. investigating Jul 18, 2025, 04:53 PM UTC

   A link to the Broadcom status can be found here: https://status.broadcom.com/notices/gnghnazmjpbilwta-carbon-black-cloud-us-region-outage

5. identified Jul 18, 2025, 05:02 PM UTC

   Broadcom has updated the status to Identified. We are tracking process. https://status.broadcom.com/notices/gnghnazmjpbilwta-carbon-black-cloud-us-region-outage

6. monitoring Jul 18, 2025, 06:44 PM UTC

   Broadcom has implemented a fix and we are monitoring progress. Broadcom Status Page: https://status.broadcom.com/notices/gnghnazmjpbilwta-carbon-black-cloud-us-region-outage

7. resolved Jul 18, 2025, 07:46 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 13, 2025, 03:42 AM UTC· resolved Jul 13, 2025, 01:24 PM UTC

1. investigating Jul 13, 2025, 03:42 AM UTC

   We are currently investigating an issue processing some raw telemetry. Detections may be delayed. We will update this incident as more information becomes available.

2. identified Jul 13, 2025, 04:54 AM UTC

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

3. monitoring Jul 13, 2025, 06:15 AM UTC

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

4. resolved Jul 13, 2025, 01:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2025, 02:11 PM UTC· resolved Jun 30, 2025, 02:44 PM UTC

1. identified Jun 30, 2025, 02:11 PM UTC

   We have identified a technical issue with our ticketing system that is preventing us from viewing ticket details. All tickets are currently affected. We are actively working with our support vendor to get this resolved.

2. resolved Jun 30, 2025, 02:44 PM UTC

   This issue has been resolved.

Read the full incident report →

Started Jun 25, 2025, 06:58 PM UTC· resolved Jun 25, 2025, 11:44 PM UTC

1. investigating Jun 25, 2025, 06:58 PM UTC

   We have identified an issue that may lead to delayed detections for Identity and Cloud activity. We are currently remediating this issue and will provide updates as they become available.

2. investigating Jun 25, 2025, 06:58 PM UTC

   We are continuing to investigate this issue.

3. resolved Jun 25, 2025, 11:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2025, 08:10 PM UTC· resolved Jun 12, 2025, 11:43 PM UTC

1. investigating Jun 12, 2025, 08:10 PM UTC

   We are investigating delayed data from Palo Alto Cortex and Google Cloud Platform that may result in delayed detections until these issues are resolved. Additional status may be obtained from our partner's status pages: Palo Alto Cortex: https://rootly.com/external-status-pages/palo-alto-networks Google Cloud Platform: https://status.cloud.google.com/

2. investigating Jun 12, 2025, 08:11 PM UTC

   We are continuing to investigate this issue.

3. investigating Jun 12, 2025, 10:52 PM UTC

   The Google Cloud Platform has recovered. We are continuing to monitor delayed data from Palo Alto Cortex that may result in delayed detections. Additional status may be obtained from our partner's status pages: Palo Alto Cortex: https://rootly.com/external-status-pages/palo-alto-networks Google Cloud Platform: https://status.cloud.google.com/

4. resolved Jun 12, 2025, 11:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 10, 2025, 07:55 PM UTC· resolved Jun 11, 2025, 01:35 AM UTC

1. investigating Jun 10, 2025, 07:55 PM UTC

   We are currently investigating an increased number of failing system status checks across multiple customers.

2. identified Jun 10, 2025, 08:03 PM UTC

   We believe we have identified the root cause of the failing system status checks and currently believe most of these failures are false positives and failed incorrectly. We are validating these findings and will implement a fix as appropriate. There is no impact to data ingestion, detection, or response capabilities of the Red Canary platform.

3. monitoring Jun 10, 2025, 08:36 PM UTC

   We believe we have identified the root cause of the failing systems status checks. A fix has been implemented and we are monitoring the system to confirm it is returning to normal operations . Alert ingestion, alert timeliness, and response capabilities of the Red Canary platform are delayed. Telemetry ingestion and telemetry related detection are not affected.

4. resolved Jun 11, 2025, 01:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 06, 2025, 04:53 PM UTC· resolved Jun 10, 2025, 06:10 PM UTC

1. investigating Jun 06, 2025, 04:53 PM UTC

   We are investigating authentication issues with VMware Carbon Black (hosted by VMware Carbon Black). We have notified the VMware Carbon Black production engineering team and are working with them to ensure they resolve the issue promptly. Active Remediation response actions may be delayed.

2. monitoring Jun 10, 2025, 06:07 PM UTC

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

3. resolved Jun 10, 2025, 06:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 29, 2025, 03:07 PM UTC· resolved May 30, 2025, 02:55 PM UTC

1. monitoring May 29, 2025, 03:07 PM UTC

   We are monitoring a potential SentinelOne outage that is impacting telemetry ingestion for SentinelOne customers. Detections may be delayed until the issue is resolved.

2. monitoring May 29, 2025, 09:04 PM UTC

   We are monitoring delayed data from the earlier SentinelOne outage. Detections may be delayed until the issue is resolved.

3. resolved May 30, 2025, 02:55 PM UTC

   This incident has been resolved.

Read the full incident report →