Red Canary Outage History
Red Canary is up right nowPingoru has recorded 50 incidents for Red Canary: 11 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 7 of 720 (1%) |
| May 2026 | 2 | 8 of 744 (1%) |
| June 2026 | 1 | 8 of 720 (1%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 1 | 2 of 591 (0%) |
Incidents, newest first
Minor April 21, 2025 Security Data Lake Ingestion Degradation 7h 34m Web Portal, Ingestion, Search
Started Apr 21, 2025, 01:53 PM UTC· resolved Apr 21, 2025, 09:27 PM UTC
- investigating Apr 21, 2025, 01:53 PM UTC
We are currently investigating an issue impacting data ingestion into the Security Data Lake. There is no indication of data loss at this time. Searches will only return data ingested prior to 7 AM MT on 4/21/2025.
- investigating Apr 21, 2025, 02:25 PM UTC
We are continuing to investigate this issue.
- identified Apr 21, 2025, 04:01 PM UTC
We have resolved the issue impacting data ingestion into the Security Data Lake. Data is being ingested as expected. Searches will only return data ingested prior to 7 AM MT on 4/21/2025.
- resolved Apr 21, 2025, 09:27 PM UTC
This incident has been resolved.
Minor April 6, 2025 Delayed SentinelOne Telemetry Ingestion 1h 49m SentinelOne, SentinelOne
Started Apr 06, 2025, 04:09 PM UTC· resolved Apr 06, 2025, 05:59 PM UTC
- identified Apr 06, 2025, 04:09 PM UTC
We are currently monitoring a SentinelOne maintenance window which is impacting our ability to ingest telemetry for SentinelOne customers. Detection for these customers may be delayed until maintenance is complete.
- identified Apr 06, 2025, 04:10 PM UTC
We are currently monitoring a SentinelOne maintenance window which is impacting our ability to ingest telemetry for SentinelOne customers. Detection for these customers may be delayed until maintenance is complete.
- resolved Apr 06, 2025, 05:59 PM UTC
SentinelOne’s maintenance window is complete. We are ingesting telemetry from SentinelOne customers.
Minor March 13, 2025 Ingestion Issues for Carbon Black Cloud Customers 1d 4h Detections, VMware Carbon Black Cloud
Started Mar 13, 2025, 08:59 AM UTC· resolved Mar 14, 2025, 01:33 PM UTC
- monitoring Mar 13, 2025, 08:59 AM UTC
We are investigating ingestion issues with Carbon Black Cloud. We are monitoring the Carbon Black Cloud status page and will provide updates when they are available. Sensor telemetry, events, and detections may be delayed.
- monitoring Mar 13, 2025, 10:02 AM UTC
Carbon Black Cloud has implemented a fix and they are monitoring the service for stability. Ingestion of Carbon Black Cloud telemetry is no longer delayed. We will leave this incident open until Broadcom resolves theirs.
- monitoring Mar 13, 2025, 04:05 PM UTC
Broadcom's incident remains in a monitoring state and we have been successfully ingesting and processing telemetry from Carbon Black Cloud for the past 6 hours. We will continue to leave this incident open while we monitor Broadcom's status.
- monitoring Mar 13, 2025, 10:39 PM UTC
Broadcom's incident remains in a monitoring state and is being regularly checked for updates. Telemetry from Carbon Black Cloud is being successfully ingested and processed. We will provide additional updates when they are available.
- resolved Mar 14, 2025, 01:33 PM UTC
Broadcom's incident remains in a monitoring state and we have not observed any errors on our end over the past 24 hours.
Minor February 10, 2025 Alert Ingestion Delays Causing Failing Status Checks 3h 2m SentinelOne, Microsoft, Detections, Proofpoint TAP and 3 more
Started Feb 10, 2025, 08:00 PM UTC· resolved Feb 10, 2025, 11:02 PM UTC
- identified Feb 10, 2025, 08:00 PM UTC
We have identified an issue causing some alerts to fail ingestion, which may result in failing status checks for certain customers. Our team is actively testing a fix and assessing its impact. No alert data has been lost and all failed alerts will be reprocessed once the fix is implemented. Please note that detections based on these alerts may be delayed until ingestion is fully restored. We appreciate your patience and will provide further updates as they become available.
- monitoring Feb 10, 2025, 08:41 PM UTC
We have successfully deployed a fix for the alert ingestion issue and alerts are now being ingested. Detections may still be delayed while we process the backlog of failed alerts. In addition, status checks that appeared to fail during this incident will automatically resolve; no customer action is required. We will continue to monitor the situation and will close this incident once all backlogged alerts have been ingested.
- monitoring Feb 10, 2025, 08:42 PM UTC
We have successfully deployed a fix for the alert ingestion issue and alerts are now being ingested. Detections may still be delayed while we process the backlog of failed alerts. In addition, status checks that appeared to fail during this incident will automatically resolve; no customer action is required. We will continue to monitor the situation and will close this incident once all backlogged alerts have been ingested.
- resolved Feb 10, 2025, 11:02 PM UTC
This incident has been resolved and all backlogged alerts processed.
Minor February 9, 2025 Delayed Telemetry Processing for Multiple Telemetry Sources 10h 15m Detections, VMware Carbon Black Cloud, Microsoft Office 365, CrowdStrike Falcon and 7 more
Started Feb 09, 2025, 04:42 AM UTC· resolved Feb 09, 2025, 02:58 PM UTC
- investigating Feb 09, 2025, 04:42 AM UTC
We have identified an issue that is causing delayed telemetry processing for Carbon Black Cloud EDR, Microsoft Defender for Endpoint, Microsoft Office365, SentinelOne, CrowdStrike, TrendMicro, AWS, Microsoft Azure, Jamf, and Linux EDR. This delay in telemetry may cause potential delays in detecting threats based on this telemetry. We are investigating the cause of this issue currently and will provide updates as we know more and are able to take action to address the issue.
- investigating Feb 09, 2025, 04:43 AM UTC
We are continuing to investigate this issue.
- monitoring Feb 09, 2025, 05:40 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 09, 2025, 02:58 PM UTC
This incident has been resolved.
Minor January 10, 2025 Tracking an external incident with Broadcom Carbon Black Cloud 2d Carbon Black Cloud
Started Jan 10, 2025, 05:24 PM UTC· resolved Jan 12, 2025, 06:09 PM UTC
- identified Jan 10, 2025, 05:24 PM UTC
We are tracking an outage with Broadcom Carbon Black Cloud (CbC) that is affecting alert ingest and correlation of alerts to endpoint data. https://status.broadcom.com/services/carbon-black/notices/kcjrp2fn7pniepsu-carbon-black-cloud-alerts-page-search-degraded-performance
- identified Jan 10, 2025, 06:47 PM UTC
Broadcom Carbon Black continues to investigate this issue.
- monitoring Jan 11, 2025, 01:11 PM UTC
After a few false starts, Broadcom has shifted their incident to "Monitoring". We have been successfully ingesting and correlating alerts for the past 5 hours. We will leave this incident open until Broadcom resolves theirs.
- resolved Jan 12, 2025, 06:09 PM UTC
Broadcom's incident remains in a monitoring state and we have not observed any errors on our end over the past 24 hours.
Minor November 6, 2024 Alert ingestion Issues for Microsoft Defender for Endpoint Customers 10h 27m Detections, Microsoft
Started Nov 06, 2024, 02:32 PM UTC· resolved Nov 07, 2024, 01:00 AM UTC
- investigating Nov 06, 2024, 02:32 PM UTC
We are investigating ingestion issues of alerts from Microsoft Graph V2. We have notified the Microsoft support team and are working with them to resolve the issue promptly. Process execution (EDR) telemetry is still being ingested and processed by Red Canary. Detection of threats from Microsoft Graph V2 alerts may be delayed.
- investigating Nov 06, 2024, 06:36 PM UTC
We are continuing to monitor the status of this ingestion issue with Microsoft Graph V2 alerts. At this time there is no update.
- resolved Nov 07, 2024, 01:00 AM UTC
This incident has been resolved.
Minor October 30, 2024 Ingestion Delays for JAMF Telemetry 15h 31m Detections
Started Oct 30, 2024, 07:32 PM UTC· resolved Oct 31, 2024, 11:04 AM UTC
- identified Oct 30, 2024, 07:32 PM UTC
We are currently monitoring an operational incident with Jamf (https://status.jamf.com/) that is impacting our ability to ingest telemetry for Jamf customers. Detection for these customers may be delayed until the issue is resolved. This incident will be updated as additional information becomes available from Jamf.
- resolved Oct 31, 2024, 11:04 AM UTC
We have confirmed that we are now ingesting telemetry from JAMF.