I really do appreciate it. Is there any way Fly could detect this? I know geo IP isn’t perfect but it seems like it could help you track this stuff by allowing you to compare edge location to the users location.
There probably is a good way to do this. Do you have thoughts on things we should do here? We have a code footprint in every region (and also in like 6 off-platform regions on other providers) for doing this kind of monitoring, and we're probably not putting it to the most effective use we can. Ideas would be most welcome.
This idea might be a bit too naive but it seems like it could help
1) Record the IP address and edge of connecting clients
2) Use an IP API to determine the rough location and ISP of clients based on their IP
3) Spatially query the edge closest to each client and graph/log serious mismatches (>x miles off)
4) Cast the spells required to route offending ISP better
5) See if the data improves :)
For example, the IAD edge would record that I connected from San Diego via Cox Communications. My closest edge geographically is LAX so that's ~2500 miles of excess travel!
Traces and ISP involved are in there. Thanks for looking into it!
Edit: I just double checked and it's still the same route to the east coast as posted in the thread