Routing variations between servers

[Scorch_]

Back in November I purchased a single core vps in Denver in order host a quake live server for the small group of people I play with, everyone at the time pinged well enough aside from 2 or 3 people who were getting a poor connection and frequent ping spikes. At the time I chalked it up to poor routing on their end and since they didn't make much of a fuss about the issue I left it alone.

Recently another member of our group purchased a server in the same location and it seems to have fixed most of the routing problems people were having, I at first thought they were using a different host which would explain why people were getting better routing, but after doing a trace route on the server it turns out that its an nfo server.

So this stumped me since I would think two servers in the same location would route about the same, the only thing I could think of is that since I was on the single core package maybe what I thought was a routing issue was a hardware issue or my server was getting low priority for bandwidth.

In an attempt to fix this I decide to upgrade to the two core package thinking that at the very least I could rule out hardware being the issue, after upgrading and restarting the server it seems to be only worse with serval people including my self having connection issues. I'm kinda at a loss now though I think my routing issues might be separate from the issues that were happening prior to the upgrade since I'm currently routing poorly to both servers.

Any information or help fixing this would be greatly appreciated.

[kraze]

We can definitely take a look at the inbound and outbound routing here, but we'll need you to open a request with us via the "help" tab in your control panel. If possible please have the users who are seeing issues run inbound MTRs and include those along with their home IP in the request.