Server IPs will be changing

Started by Helen, Jan 30, 2020, 12:17 PM

Previous topic - Next topic

Helen

The IPs will be changing shortly (next few days?). My host is upgrading their hardware. I will post the new IPs here as soon as I know them.

Here is the text from my host:

As we mentioned a while back we are upgrading a lot of our servers over the coming months, well the time has come to move you onto brand new hardware. As part of this process we need to move you off of the server you are currently on to the new hardware. Unfortunately this will change your IP/Port which cannot be avoided. These moves will be taking place over the next few days, once you are moved you will receive an email with the new server details. All moves will where possible take place outside of peak hours.

New Mountain IP: 104.206.108.186:7777
(Still waiting for new island IP).
One of the Scriveners.

SBZ_Kimzter

Hi Helen, lost you for a few days. I found the server just now, but the ping is really high. Where is the new server located?

Helen

Still in Chicago (I just checked). Perhaps they just got the IP and the world routing tables are not updated yet. I hope it gets better for you. Seems the same to me at any rate, I have the same ping as before.
One of the Scriveners.

TheMartMan

I just played on the new server and UT said my ping was 50! My F6 ping was 106 - about what it was before.

SBZ_Kimzter

#4
My ut ping ranges from 100 to 200+ . the f6 shows 170 and higher. Its not too bad when no one else is there but where's the fun in that  :)  Sometimes my rockets appear behind me  when I shoot on the run.  It used to run really consistently from 75 to 100

Helen

#5
Open a command prompt. Type in this and press enter:

tracert 104.206.108.186

Sometimes the hops get messed up as the fastest path. See if any of the hops are diverting to europe or something. This sort of this eventually sorts itself out.

[edit]As per your question: Why do the routes get messed up
This is as I understand it, but I am probably off on a few counts.

It takes several hops to go from your PC to the server. Each hop knows which way to send your request based on information it has (routing tables). But IP locations change, so these routing tables will be out of date for a bit.

My guess is that the server's IP used to be somewhere else, and one of the hops between your pc and the server still has outdated information as to how to get to the IP.

Something like that.
One of the Scriveners.

SBZ_Kimzter

it times out on the second step. then it does two more steps and gets there at 80ms on the 4th one. but it timed out every time out of 6 tries

Helen

Aha, yes timing out is a pretty bad hop, and the culprit.
Since it is on the second hop, that means it is probably within your service provider's region, and you can report that hop to them, hoping that they will manually intervene to get it updated faster. You would submit them the trace route results.
One of the Scriveners.