PingMesh: Finding What the Network Actually Delivered

In this demo, Selector PingMesh continuously checks whether devices and applications across a distributed enterprise network can reach each other, measuring latency, packet loss, and jitter. The walkthrough covers four views:

• Active PingMesh shows 14 agents in colocation sites, points of presence, and the cloud testing each other continuously.
• Site health scores every site the agents test, so a struggling site stands out.
• Agent connectivity and the packet loss trend show every agent testing toward a site, with loss over time for each one.
• Path detail and the traceroute widget break a single agent-to-site path into loss, latency, and the hops each sample took.

The demo widens the time range to the previous night, where Site-E in Oak Springs sits at the bottom of the health range. All ten agents testing toward the site hit 100 percent packet loss at 3:24 and recovered together at 6:23, which points to the site itself as the source. Following the path from the Falcon agent shows latency holding at about 48 milliseconds before the outage and returning to the same level afterward. Traceroute samples taken before and after the outage follow the same hops, while the sample taken during the outage stops at Router-SW-01, confirming the route never changed. The incident record explains the rest: an area-wide power outage took Site-E offline, and a DHCP issue delayed full recovery until 6:23. With PingMesh data and the incident record side by side, the team knows which site failed, when it failed, and why.