Carbon Black Outage History

Carbon Black is up right now

Carbon Black had 13 outages in the last 2 years totaling 641h 57m of downtime — averaging 0.5 incidents per month.

There were 13 Carbon Black outages since April 23, 2026 totaling 641h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.broadcom.com/services/carbon-black

Major June 3, 2026

Issues with Alarms Affecting all Application Nodes

Detected by Pingoru
Jun 03, 2026, 05:00 PM UTC
Resolved
Jun 05, 2026, 06:18 AM UTC
Duration
1d 13h
Timeline · 2 updates
  1. investigating Jun 03, 2026, 05:00 PM UTC

    Broadcom Engineering is investigating issues with alarms, including but not limited to: - Errors in the UI when loading certain data in the Alarm Summary, Alarm Console, or Alarm Detail pages - Network Path, Web Path, and Monitoring Point information not populating properly in alarms We are investigating the issue and will post updates here.

  2. investigating Jun 03, 2026, 07:51 PM UTC

    We have implemented a fix and we are monitoring the situation

Read the full incident report →

Major May 29, 2026

Carbon Black - Endpoint Standard - Customers may be experiencing failures with the Cloud Analysis Service

Detected by Pingoru
May 29, 2026, 02:24 PM UTC
Resolved
Jun 01, 2026, 05:48 PM UTC
Duration
3d 3h
Timeline · 2 updates
  1. investigating May 29, 2026, 02:45 PM UTC

    We have identified the cause of the issue and have implemented a fix. We will now monitor the service for stability and provide updates as soon as new information becomes available.

  2. resolved Jun 01, 2026, 05:48 PM UTC

    We have monitored the service for stability and this incident shall now be closed.

Read the full incident report →

Major May 10, 2026

Production-EU-003 Unavailable

Detected by Pingoru
May 10, 2026, 01:31 AM UTC
Resolved
May 12, 2026, 08:48 PM UTC
Duration
2d 19h
Timeline · 1 update
  1. investigating May 10, 2026, 01:43 AM UTC

    We have identified the cause of the issue and have implemented a fix. We will now monitor the service for stability and provide updates as soon as new information becomes available.

Read the full incident report →

Major May 9, 2026

Non-Production-US-001 Performance Degradation

Detected by Pingoru
May 09, 2026, 03:30 PM UTC
Resolved
May 12, 2026, 08:38 PM UTC
Duration
3d 5h
Timeline · 1 update
  1. investigating May 09, 2026, 03:30 PM UTC

    ​​We have identified performance degradation issues for Automic SaaS Non-Production-US-001. To address the issue, customers are required to restart the affected agent as soon as possible. We will provide updates as more information becomes available.

Read the full incident report →

Major May 8, 2026

CloudHealth: Delayed Reports and Assets collection

Detected by Pingoru
May 08, 2026, 04:50 AM UTC
Resolved
May 11, 2026, 08:49 PM UTC
Duration
3d 15h
Timeline · 1 update
  1. investigating May 08, 2026, 09:45 AM UTC

    We are pleased to share that asset collection and data processing has been resumed. We will now monitor the service for stability and provide updates as soon as new information becomes available.

Read the full incident report →

Major May 8, 2026

Availability Zone (use1-az4) Impacted

Detected by Pingoru
May 08, 2026, 02:02 AM UTC
Resolved
May 10, 2026, 12:49 AM UTC
Duration
1d 22h
Timeline · 1 update
  1. resolved May 10, 2026, 12:49 AM UTC

    All customer SDDC environments in Availability Zone use1-az4 within the US-EAST-1 Region are now fully functional and operating within SLO.

Read the full incident report →

Major May 5, 2026

Cloud SWG: DNS Errors for .de Domains

Detected by Pingoru
May 05, 2026, 10:18 PM UTC
Resolved
May 06, 2026, 06:38 PM UTC
Duration
20h 20m
Timeline · 2 updates
  1. investigating May 05, 2026, 11:32 PM UTC

    We are seeing DNS failure rate back to normal. Based on our tests, the DNS queries are working fine for the .de hostnames. We will now monitor the service for stability and provide updates as soon as new information becomes available.

  2. resolved May 06, 2026, 06:38 PM UTC

    We have monitored the service for stability and this incident shall now be closed.

Read the full incident report →