Fortigate firewalls have a performance sla that you can setup between two wans. Allows you to track ping time, jitter and bandwidth. It’s one of the ways it test for fail over. I use it to keep my isp honest. Looking at you charter, bag of dicks they are.
Check out the smokeping_prober. It generates high resolution histogram data that you can use to compare different paths.
EDIT: I really don't want this post to turn into a debate about the merits of doing this, I just want to discuss tools that are out there that could do this.
Too bad. ICMP echo requests to a local anycast server don't tell you anything about the service or a provider's ability to handle those connections.
As a small ISP, I would like to know what your goal is here, or at least what you hope to discover.
I just wanted to collect a range of endpoints for common services and get some data to compare, especially to see if there's anything egregious. For example, on AT&T fiber I get 11ms to Blizzard's east coast servers, but on my other fiber connection it's 77ms.
It's all moot anyway, I don't think I'm going to stay with the smaller company. I have to pay $5 extra a month just to get a public IP on my router, otherwise I'm NATd somewhere upstream. Then it turned out they couldn't make IPV6 work anymore because switching me to a static IP turned off DHCP and they don't have support for static IPV6 yet. Anyway it's kind of shit show. The icing on the cake is when I got a billing email from them showing that they're running billing software that went extinct 15 years ago (Rodopi if you're familiar, I couldn't believe it, worked with it myself back in 2002).
For example, on AT&T fiber I get 11ms to Blizzard's east coast servers, but on my other fiber connection it's 77ms.
Ah, interesting. We switched transit providers a year ago and noticed a big improvement in routing efficiency. Small providers are usually at the mercy of their upstream peers unless they can build their own backbone links to an IX.