ITAM / CMDB

Blast Radius

See which assets, services, and people would be affected if something fails or changes, so Alex can approve maintenance windows with confidence.

Real-world scenario

Alex Kim · VP of IT at Bluewave Labs

Alex is asked to sign off on decommissioning an aging Redis instance. Before approving, he runs blast radius on cache-prod-02 to see which APIs and engineers lose session state.

Before you begin

  • CMDB relationships linked for the asset you are analyzing
  • ITAM access to open asset detail or relationship graph views

Overview

Blast radius extends the relationship graph with impact-oriented traversal. Instead of browsing all connections equally, you see what would break or degrade if the focal asset went offline or underwent a disruptive change.

Alex uses it for executive go/no-go decisions. Maya runs it during incidents to prioritize communication. Carlos validates completeness before major cutovers.

When to use blast radius

  • Planning server maintenance or decommissioning
  • Assessing outage impact during active incidents
  • Validating CMDB completeness before major infrastructure changes
  • Prioritizing relationship linking for high-criticality assets

Viewing impact

  1. 1

    Start from an asset or the relationship graph

    Open blast radius from a server, domain, or device detail page, or switch from graph view when you already have context.

  2. 2

    Review impacted assets by type

    WorkVerge groups downstream dependents: servers, domains, devices, employees, and vendor subscriptions in the impact zone.

  3. 3

    Check coverage before you commit

    If the CMDB health score is low, treat missing nodes as a gap, link relationships before relying on the view for a production change window.

  4. 4

    Share results with stakeholders

    Export or screenshot the visualization for change advisory boards. Pair with WorkVie AI for a plain-language executive summary.

Blast radius for cache-prod-02 at Bluewave Labs

  • Servers affected: prod-api-01, prod-api-02, worker-queue-01
  • Domains at risk: api.workverge.ai, app.workverge.ai
  • Employees impacted: 34 engineers with active sessions
  • Vendor tie-in: AWS ElastiCache subscription

Incomplete CMDB = under-reported impact

Blast radius is only as accurate as your relationships. A CMDB health score below 70 may hide dependents that were never linked. Run a cleanup sprint, or ask WorkVie AI for unlinked neighbors, before you rely on this view for a production change window.

WorkVie AI blast radius

Prefer a narrative summary for leadership? Ask WorkVie AI to compute and explain blast radius in plain language. The agent traverses the same CMDB relationships and returns impacted servers, services, employees, and downstream dependencies you can paste into a change ticket.

See AI Blast Radius for example queries like "What is the blast radius if prod-api-01 goes down?"

Related articles