I think the 20% ICMP packet loss on that Level3 router is probably just rate limiting. If it were dropping network traffic, it would be ~20% loss for each hop after it, as that traffic must implicitly pass through that server. Further, it would affect all traffic, not just Roll20. Trace route can really only diagnose network connection issues, not protocol problems. The fact that the reports show very little loss on the final hop means they are not having a problem connecting across the network to that particular server. I agree that the issue is completely outside the control of Roll20/Linode. It seems to be specific to the connection to Roll20, but it is probably really specific to the types of connections to Roll20 or the type of data being exchanged between Roll20 and the client browser. Somethings to consider: Some ISP/Router could be blocking higher ports that are specifically know to be used by certain viruses to communicate, but which also happen to be in the range of some of the secondary services roll20 employes, like Firebase. Some ISP/Router could have a problem with how it handles TCP Packet fragmentation and reassembly, mangling data packets the client depends on and causing it not to load properly. The TOR browser appears to fix this problem because it re-encodes the information and transfers it in a different way. If you could look at the traffic going through the TOR browser, you would see that it is not on the same port ( probably all on 443 ) and not the same size ( probably broken up into many small packets to pass through the encrypted tunnel ), and not following the same routes ( which probably has less of an effect on this data ). Your best bet is to contact your ISP and tell them exactly what problem you're having, and when it started. Try to get escalated to a higher level of support staff as quickly as possible ( ask for 2nd tier or 3rd tier support or whatever the local term is ). Make sure you tell them you are using a web based application with Javascript Sockets on multiple ports, and that the issue appears to only be affecting you and other users on your ISP's network (though really, it is probably affecting everyone in your regional network, for some definition of "region".)
