Static IP?

[#1]

@Kali_ffs 

latency could be a result if an underlining issue with your connection. Have you performed any testing?

What hosts are you having issues with?

[#2]

Sorry Dan busy busy busy,

Tried tracert looks like a problem with one specific server which i never had before...

C:\Users\Beast>tracert 74.91.125.204

Tracing route to c-74-91-125-204.premium-chicago.nfoservers.com [74.91.125.204]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 9 ms 8 ms 8 ms 195.166.130.249
3 9 ms 9 ms 9 ms gi2-23-442.ptn-gw02.plus.net [84.93.253.75]
4 9 ms 9 ms 9 ms core1-BE1.colindale.ukcore.bt.net [195.99.125.132]
5 9 ms 10 ms 10 ms core5-hu0-3-0-15.faraday.ukcore.bt.net [109.159.252.132]
6 9 ms 10 ms 9 ms 166-49-209-132.gia.bt.net [166.49.209.132]
7 11 ms 10 ms 11 ms 166-49-209-131.gia.bt.net [166.49.209.131]
8 11 ms 11 ms 11 ms be3487.ccr41.lon13.atlas.cogentco.com [154.54.60.5]
9 80 ms 79 ms 79 ms be2099.ccr31.bos01.atlas.cogentco.com [154.54.82.34]
10 80 ms 79 ms 80 ms be3599.ccr21.alb02.atlas.cogentco.com [66.28.4.237]
11 102 ms 101 ms 101 ms be2878.ccr21.cle04.atlas.cogentco.com [154.54.26.129]
12 109 ms 108 ms 109 ms be2717.ccr41.ord01.atlas.cogentco.com [154.54.6.221]
13 98 ms 99 ms 98 ms be2765.ccr41.ord03.atlas.cogentco.com [154.54.45.18]
14 96 ms 95 ms 96 ms cogent.e9.router1.chicago.nfoservers.com [64.74.97.254]
15 108 ms 108 ms 108 ms c-74-91-125-204.premium-chicago.nfoservers.com [74.91.125.204]

C:\Users\Beast>tracert 208.167.243.170

Tracing route to 208.167.243.170.choopa.net [208.167.243.170]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 9 ms 8 ms 8 ms 195.166.130.249
3 9 ms 9 ms 9 ms gi2-23-442.ptn-gw02.plus.net [84.93.253.75]
4 9 ms 9 ms 10 ms core1-BE1.colindale.ukcore.bt.net [195.99.125.132]
5 11 ms 12 ms 11 ms peer7-et-0-0-1.telehouse.ukcore.bt.net [62.172.103.158]
6 9 ms 9 ms 9 ms 166-49-214-194.gia.bt.net [166.49.214.194]
7 78 ms 97 ms 78 ms ixp1-ae-0.us-nyh.gia.bt.net [166.49.208.92]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 79 ms 79 ms 78 ms 208.167.243.170.choopa.net [208.167.243.170]

Trace complete.

The server with the time out requests is not the problem, it's the first one, the problem 'hops' highlighted in red. These are the main two i use and never had issues as consistent as i do now before the switch to static...

When my friends who live in Germany, Spain and the Netherlands connect, they have better ping than me...How? 

The only thing i can think of is that their connections take a better route, which is why i believe the static IP is in some way to blame, when it was dynamic the location, though not accurate, would show Catshill area, consistently. Now with static it, though not accurate, it shows Chester, consistently, this is why i ask. Something has gone on, wrong, who knows.....?

Thanks for your time

[#3]

Hi @Kali_ffs 

I also have a static IP address, using MTR I tested both servers. (My setup Hub Two in bridge mode TP-Link router)

74.91.125.204

208.167.243.170

So my response time for 74.91.125.204 is slightly longer, 208.167.243.170 is inline with yours.

Perhaps someone with a dynamic IP can check?

Dan 

[#4]

74.91.125.204
Testing on a server in NL, timings aren't that much different
Less hops, but the last 4 are all over 90ms .
Testing on a server in the states, it's still above 50ms.

208.167.243.170 are much inline.

So not sure there is an issue with PN here.

[#5]

Well, thanks for testing and taking the time to verify things. Not sure what's gone on my end, but it all changed after I renewed my contract and the goodwill gesture of the static ip was implemented.
Maybe I should get them to switch back to dynamic and put up with the random address flips, or move to Spain

Cheers again...