Sorry - not trying to be negative - would love to be enlightened if there is something that I am missing!
I work as a network admin for a large UK internet service provider and hosting company, troubleshooting network faults can be very interesting when your actually on the same network, obviously your not getting a true perspective that matches an 'off net' client issue.
Most of the routers/servers that I manage and have access to are also 'on net', so while they do supply the tools I need, they still aren't really giving me an accurate view.
So I have my own servers dotted around the internet, but logging into them takes time etc, I just find it easier and faster to open my browsers bookmark and type in the destination.
Finally I can also give other people access to the service, such as clients, other network admins or anyone really, even you :)
Good luck, as I said - I don't want to be negative, just puzzled by this.
I realise that the tool wont match everyones requirements, to be honest I made it for me and what I use it for, if other people find it useful thats a bonus! Also if I can improve it to match what people want that's even better.
A client reports an issue that some of their website visitors are having packet loss/reachability issues, however the network I am working on has 3 transit providers, which means 3 different ways into the network.
I can certainly do a trace route from my machine or routers to their clients (if i know their IP) but that's only showing me the outbound route, I am still none the wiser as to which route they are trying to get in via.
By using multiple off-net trace routes I can probably enter my core network over each of the 3 transit providers. Looking at these results I should be able to see if there are any obvious issues with incoming traffic.
It's certainly not going to work every time, however it will give me a better view as to what's going on.
Just need to do some more coding, and then find a few cheap VPSs to get it live.
Wasn't quite expecting that much traffic :)