Overview/Features/The Unified Map
The Unified MapPick two things.
Check the path.
The whole inventory on one screen, and the fastest way to run a check. Two searchable pickers, the ports you care about, and a result with the path drawn under it — no form to fill in, no syntax to remember.
Source and destination
Two searchable pickers, matching on name or address. Results are grouped under Hosts and Firewalls & devices — a firewall is a first-class thing on the map, not a gap between two hosts.
The ports to check
One row per check: a port, a protocol — TCP, UDP or ICMP — and a live result with round-trip time as it comes back. Add as many as the application needs.
Where it stopped
Open a finished row and you get the verdict, the round-trip time, and a path strip: source → hops → destination, with the firewall and layer-3 badges marked along it.
Two views of the same estate
List groups hosts into cards by type and cluster. Map draws the canvas graph — scroll to zoom, drag to pan, click a hub to focus. Below 62% it collapses groups into count bubbles so a large fleet still reads.
Filtered by what things are
Chips for Kubernetes, Docker, VMs, cloud and firewalls, each with a live count — and counters for how many hosts are online, down, or not yet reached. Unchecked means unknown, never down. AWS, Azure and Google Cloud are built in; add any other cloud by name, colour and region, and its services join the map as ordinary hosts under that colour.
It tells you when a pair crosses worlds
Select a source on-premise and a destination in a cloud, and the panel flags it as a cross-environment pair — and marks an observed VPN tunnel when there is one. That is the hybrid path, called out rather than left for you to notice.
Turn a check into a standing rule
A result you want to keep watching becomes a connectivity rule with one click, or goes to history as a recorded job. An ad-hoc question becomes something that gets re-checked.