Sometimes we use Netpath to show that a slowness is likely server or application based, not the network path between a user and a server.
We also use it to keep track of connections to Microsoft (O365, Skype, Teams), and a few other SAAS.
Note: We were able to find the cause of the red-marked area, and correct the issue fairly quickly.
We started with "any Windows PC" but soon found that discarded laptops were unstable things that you really need a user in front of all the time, to press OK & turn it off and on. We've gone for virtual WS2016 servers around the globe. They are dedicated to running NetPath traces and WPM transactions. We've got a bunch of them and we check paths and user experience from many sources to many targets. It's such an eye-opener.
NetPath provides the information that allows us to hold the intermediate ISP's or WAN providers' feet to the fire for poor performance / oversubscription. We can show them exactly what hops suddenly have 1000% latency increases during the business day, when those performance delays begin, when they end, etc. There's no dodging the NetPath bullet--we use it to show why baseline performances change.
It's also ridiculously easy and helpful to show the status of O365 resources and latency to get to them.
And it's a sweet tool for Before/After displays of performance changes when we fail over to alternate WAN paths, or upgrade from one service provider to another, or from one technology to a different one.
NetPath simply rocks as a historical and real time tool for showing path changes, remote resource availability, and latency--all in one graph. It's truly the picture that says a thousand words about network performance.
We have redundant VPN tunnels to a cloud service for DB traffic. we are currently using NetPath for a visual representation as to what router is being currently used when the tunnel goes down.
I have used NetPath with clients. It can really save your bacon.
I had a customer that could not connect to their cloud service and the provider told them that it was their network as no other users were experiencing. When I checked NetPath I found that on Friday they connected to the provider via a single router connection. On Saturday they added a redundant connection and the one path was responding, but he new one was not. When the customer shared that with the provider they sheepishly said "Oh, yes, we did make that change on Saturday and will have to have an update applied."
Without NetPath this would have been a long fruitless battle.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.