I have since, I dont know actually, but for certainly 6 months had latency issues at home with Rift.
Mostly I have a latency in the range of 220-300 ms.
I have contacted my isp to see if they could see why, but helpfulness of the support is a rare mutation not seen with many in that position.
Getting me to restart my equipment, exchange cables and what not..
To the point, I bet you (if any reads this) is better amongst the things I am about trying to explain.
First I had to see what IP Rift has, so I did a netstat -b, and found rift_x64.exe pointing to 185.163.113.14
After this I have done tracert to that IP and found this information.
The IP adress in the end 185.xxx is some RIPE databas in Qatar.. which is not in the trace done at work, as seen here in under.@Home 06:30 "220 ms"
Tracing route to 185.163.113.14 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms TUF-AX6000-B598 [192.168.50.1]
2 3 ms 2 ms 2 ms 100.65.132.1
3 3 ms 3 ms 3 ms 172.18.65.38
4 4 ms 4 ms 3 ms 172.16.0.232
5 8 ms 4 ms 4 ms osab-sthlm-kn7-border.internetbolaget.nu [185.176.246.13]
6 3 ms 2 ms 2 ms ibs-kn7-core01.internetbolaget.nu [185.176.246.12]
7 2 ms 3 ms 2 ms ibs-tc-core01.internetbolaget.nu [185.176.246.14]
8 2 ms 2 ms 2 ms h246-1.internetbolaget.nu [185.176.246.1]
9 3 ms 2 ms 9 ms ibs-tc-core01.internetbolaget.nu [185.176.246.0]
10 25 ms 25 ms 25 ms as56886.ix.dataix.eu [178.18.224.66]
11 110 ms 110 ms 110 ms 185.100.209.57
12 120 ms 120 ms 120 ms 185.100.209.73
13 122 ms 122 ms 123 ms 185.100.211.163
14 120 ms 120 ms 120 ms 10.11.30.242
15 * * * Request timed out..
On my first tracert above the last five ip-adresses, Qatar (185.xx) and the usa one (10.xxx) the will all be there even when my game has a good day and gives me a low latency (one day a week or so). So its not the whole truth that its all to blame but I guess its a big turd of the latency issue.@Work, 32 ms
Tracing route to 185.163.113.14 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms router.asus.com [192.168.1.1]
2 20 ms 3 ms 2 ms gw2-no193.tbcn.telia.com [81.224.87.1]
3 6 ms 5 ms 5 ms u-b-rer2-link.se.telia.net [81.228.80.251]
4 5 ms 5 ms 5 ms vs-b-c1-link.se.telia.net [81.228.78.52]
5 * 4 ms * hy-c1-link.se.telia.net [81.228.82.80]
6 * * * Request timed out.
7 5 ms 4 ms 4 ms sto-b2-link.ip.twelve99.net [62.115.123.170]
8 8 ms 5 ms 6 ms sto-bb2-link.ip.twelve99.net [62.115.140.216]
9 * * * Request timed out.
10 3 ms 3 ms 4 ms imperva-ic-377668.ip.twelve99-cust.net [62.115.55.191]
11 * * * Request timed out.
One can think it should travel about the same route from a-b, not take some turn round the globe.
Is it anything I should try before I call my dear IPS again.
My neighbour have the same result as I have with his tracert to this ip..
//Little Me, Ray
