It is quite possible for ISPs to have misconfigured their routes. Until latency service levels are more common then I wouldn’t bother with them.Īs for getting action from an ISP, a graph doesn’t add anything that is better than the time data (in milliseconds). I’ve not seen a user who gets a service level for latency except for commercial users who pay a premium or pay a lot more in total for that SLA (Service Level Agreement). And even on bandwidth it is nominal not actual bandwidth with limited or no service guarantees even on connection uptime because ISP service tends to be on a best effort basis.
Why measure network latency when most ISP’s sell broadband connections based on bandwidth rather than latency.
I’m specifically thinking of the many bandwidth management features that have been requested.Ī list of more useful features would be long and would also include: the ability to export all GlassWire statistics, user specified time periods, etc. I don’t think that this is a worthwhile feature to pursue when much more useful features are yet to be implemented in GlassWire.
Pingplotter sale software#
This doesn’t address other latency issues such as a misconfigured or defective software or devices. To be precise we should be talking about “network latency” including e.g. I don’t think that GlassWire should have ISP monitoring of network latency … full-stop or as near to it as I can think of.
0 kommentar(er)
