Störungsverlauf von Red Canary

1. 15. Oktober 2026 um 03:14 UTCinvestigating

   Wir erleben derzeit Verzögerungen bei der Datenverarbeitung, was zu einer späten Benachrichtigung einiger Kunden führt. Dieser Vorfall wird aktualisiert, sobald zusätzliche Informationen verfügbar sind.

2. 15. Oktober 2026 um 03:19 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 15. Oktober 2026 um 03:43 UTCidentified

   Die Telemetrie verzögert sich und die Systeme sind degradiert, da wir weiterhin an einer Lösung für dieses Problem arbeiten.

4. 15. Oktober 2026 um 05:12 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Juni 2026 um 19:07 UTCidentified

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

2. 30. Juni 2026 um 01:46 UTCmonitoring

   A fix has been implemented and we are monitoring results.

3. 30. Juni 2026 um 02:44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 30. Juni 2026 um 02:44 UTCresolved

   This incident has been resolved.

1. 16. Mai 2026 um 20:17 UTCidentified

   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. 16. Mai 2026 um 20:49 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 22:40 UTCinvestigating

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

2. 8. Mai 2026 um 23:07 UTCidentified

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

3. 9. Mai 2026 um 05:46 UTCresolved

   This incident has been resolved.

1. 8. April 2026 um 19:50 UTCmonitoring

   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. 8. April 2026 um 22:16 UTCresolved

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

1. 6. April 2026 um 23:26 UTCinvestigating

   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. 7. April 2026 um 02:19 UTCmonitoring

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

3. 7. April 2026 um 03:34 UTCresolved

   This incident has been resolved.

1. 4. Dezember 2025 um 22:33 UTCmonitoring

   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. 5. Dezember 2025 um 01:56 UTCresolved

   This incident has been resolved.

1. 11. November 2025 um 12:33 UTCmonitoring

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

2. 11. November 2025 um 12:57 UTCresolved

   This incident has been resolved.

1. 31. Oktober 2025 um 18:17 UTCidentified

   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. 31. Oktober 2025 um 21:55 UTCidentified

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

3. 1. November 2025 um 12:28 UTCresolved

   This incident has been resolved.

1. 29. Oktober 2025 um 17:16 UTCinvestigating

   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. 29. Oktober 2025 um 21:43 UTCmonitoring

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

3. 29. Oktober 2025 um 22:18 UTCresolved

   This incident has been resolved.

1. 27. Oktober 2025 um 21:06 UTCidentified

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

2. 27. Oktober 2025 um 22:18 UTCresolved

   This incident has been resolved.

1. 24. Oktober 2025 um 16:17 UTCmonitoring

   We are processing a large backlog of data and detections may be delayed.

2. 24. Oktober 2025 um 21:53 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 16:38 UTCmonitoring

   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. 20. Oktober 2025 um 22:55 UTCresolved

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

1. 20. Oktober 2025 um 10:09 UTCmonitoring

   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. 20. Oktober 2025 um 10:31 UTCresolved

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

1. 15. Oktober 2025 um 21:20 UTCinvestigating

   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. 15. Oktober 2025 um 21:55 UTCidentified

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

3. 15. Oktober 2025 um 23:31 UTCmonitoring

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

4. 16. Oktober 2025 um 00:56 UTCresolved

   This incident has been resolved.

1. 18. September 2025 um 18:18 UTCidentified

   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. 18. September 2025 um 18:40 UTCresolved

   This incident has been resolved.

1. 10. September 2025 um 17:39 UTCidentified

   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. 10. September 2025 um 18:30 UTCresolved

   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.

1. 13. August 2025 um 20:49 UTCidentified

   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. 14. August 2025 um 19:02 UTCresolved

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

1. 12. August 2025 um 15:35 UTCinvestigating

   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. 12. August 2025 um 17:38 UTCresolved

   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.

1. 18. Juli 2025 um 16:31 UTCinvestigating

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

2. 18. Juli 2025 um 16:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 18. Juli 2025 um 16:53 UTCinvestigating

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

4. 18. Juli 2025 um 17:02 UTCidentified

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

5. 18. Juli 2025 um 18:44 UTCmonitoring

   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

6. 18. Juli 2025 um 19:46 UTCresolved

   This incident has been resolved.