How to Automatically Run Reachability Checks on Every Network Change
Blog post from OpsMill
Infrahub’s Graph Traversal capability introduces Reachability Checks, which automatically evaluate whether proposed network changes preserve required paths between specified sources and destinations while avoiding prohibited transit points. The feature is designed to address limitations of custom Python-based topology validation, which can become difficult to maintain, may overlook undocumented policies, and often cannot assess changes made by other teams after a script runs. Infrahub models devices, sessions, zones, and tenants as a live graph, allowing checks to run against a proposed change in its branch and reveal the network state expected after merging. Authorized operators can create rules through a UI by defining endpoints, path depth and quantity limits, required transits, and forbidden transits, while engineers can view rule results and violations but may be restricted from editing rules through role-based access controls. Proposed changes are marked as passing or failing, with merge behavior determined by organizational policy, and the checks can support impact analysis, dependency mapping, security and compliance validation, capacity planning, path redundancy, and hop-count requirements.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Observability | 1 | 4,205 | 834 | 202 | -6% |
| Real-time | 1 | 6,566 | 1,497 | 249 | +1% |
| Zero Trust | 1 | 259 | 93 | 30 | +1% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.