41–47 of 47 posts
I love more tooling and attention given to latency . Throughput gets the attention but latency is what drives a high quality experience
I would not expect the latency for handling ttl expired packets to be very strongly correlated with the latency for forwarded traffic, unless exceptional conditions.
I love more tooling and attention given to latency . Throughput gets the attention but latency is what drives a high quality experience
I would not expect the latency for handling ttl expired packets to be very strongly correlated with the latency for forwarded traffic, unless exceptional conditions.
Traceroute isn't real, or: Whoops! Everyone Was Wrong Forever: https://gekk.info/articles/traceroute.htm
didn't work for me at all. auto-detected my IPv4 addy, but my tracert to google.com went over IPv6. I'm pretty skeptical about being able to geolocate router interfaces from IP addresses, so I was curious about the output. My expectations were low but they were too high. Oh well.
For IPv4, the geolocation information is quite limited (city-level) so if you live close to a major data center, you'll have a distance of 0 on the map.
Still, seeing the routes on the map is kind of fun. I don't think it provides anything useful in terms of troubleshooting that mtr doesn't provide already, but there's a fun novelty to see your traces on a map like in a 90s hacker movie.
The calls to the ipinfo.io API are blocked by Firefox Enhanced Tracking Protection. No results for Location or ISP without turning that off.
I work for IPinfo. I did not know that our site was blocked by Firefox Enhanced Tracking Protection. Not sure what I can do here. The project takes the IP addresses you have provided from your traceroute and gets the information related to them from our website using a frontend HTTP call.
Should be noted that IPInfo doesn't get blocked with tracking protection set to "standard". Users have to set tracking protection to "strict" to run into this issue. When they do this, they get warned that this setting may break sites.
I don't think Mozilla/Disconnect will make an exception because privacy-infringement is a potential risk with a service like yours if used by malicious websites. I wouldn't put too much effort into this, the people affected by this are a fraction of a fraction of the general web audience and they've already seen a warning that websites may break because of their choice.
Earlier quoted context omitted.
I work for IPinfo. I did not know that our site was blocked by Firefox Enhanced Tracking Protection. Not sure what I can do here. The project takes the IP addresses you have provided from your traceroute and gets the information related to them from our website using a frontend HTTP call.
Enhanced Tracking Protection is using the Disconnect domain list. ipinfo.io is listed in services-relay.json and mdl-services-relay.info, which I believe makes the Disconnect.me product route requests to these domains through their proxies to prevent IP fingerprinting. Should be noted that IPInfo doesn't get blocked with tracking protection set to "standard". Users have to set tracking protection to "strict" to run i…