2 ms·
Even though it lets you see network issues there sadly isn't always a way to fix them. One time I reported an issue and I was told that the issue was with my IS
by charcircuit 5y ago
Even though it lets you see network issues there sadly isn't always a way to fix them. One time I reported an issue and I was told that the issue was with my ISP despite having many people test and and using both residential and from within a data center. I was also told that my 60ms of ping between San Jose and Los Angeles was due to overhead of running it from a virtual machine. Despite having the ticket open for months it went nowhere and I eventually just found a different company to host my servers who didn't have routing issues.
- steelegbr 5y agoSpot on. It gets messier when a failure in a T1 carrier between your CDN and a customer is causing issues. Neither of you (nor possibly even the CDN) has the power to fix it. Well, other than bypass the CDN and hope the traffic passes through different peers. On the up side, MTR is indeed a useful tool for finding the issue.