120M ESO gaming problem

cymap · 28-02-2015, 20:00

Hi all, this week started having serious latency problems playing eso , just done this Tracert and wondered if someone could perhaps see the problem and maybe what I can do about it.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Mark>tracert 206.80.46.186

Tracing route to 206-80-46-186-compute-ag2-ash01.opsourcecloud.net [206.80.46.18
6]
over a maximum of 30 hops:

1 7 ms 7 ms 6 ms 10.188.80.1
2 8 ms 19 ms 9 ms bagu-core-2a-xe-120-0.network.virginmedia.net [8
0.2.12.65]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 11 ms 8 ms leed-bb-1c-ae1-0.network.virginmedia.net [62.254
.42.234]
7 18 ms 23 ms 16 ms 62.252.224.238
8 95 ms 96 ms 101 ms ae5-xcr1.nyk.cw.net [195.2.25.22]
9 85 ms 85 ms 85 ms ae-36.r06.nycmny01.us.bb.gin.ntt.net [128.241.2.
153]
10 103 ms 88 ms 84 ms ae-2.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.1
48]
11 91 ms 94 ms 90 ms ae-9.r22.asbnva02.us.bb.gin.ntt.net [129.250.2.1
49]
12 92 ms 91 ms 90 ms ae-44.r06.asbnva02.us.bb.gin.ntt.net [129.250.6.
113]
13 89 ms 88 ms 88 ms xe-0-7-0-13.r06.asbnva02.us.ce.gin.ntt.net [168.
143.105.98]
14 95 ms 91 ms 89 ms 168-143-80-38-compute-ag1-ash01.opsourcecloud.ne
t [168.143.80.38]
15 89 ms 89 ms 88 ms 206-80-46-186-compute-ag2-ash01.opsourcecloud.ne
t [206.80.46.186]

Trace complete.

lardboy · 28-02-2015, 21:37

I've also started experiencing high latency and long ping spikes this week.

I'm wondering if the P2P throttling might be effecting our connections to the game servers again.

I'm not sure what address you did a traceroute to but my results to the game servers are below -

Pinging 159.100.232.177 with 32 bytes of data:
Reply from 159.100.232.177: bytes=32 time=116ms TTL=49
Reply from 159.100.232.177: bytes=32 time=116ms TTL=49
Reply from 159.100.232.177: bytes=32 time=116ms TTL=49
Reply from 159.100.232.177: bytes=32 time=112ms TTL=49

Ping statistics for 159.100.232.177:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 116ms, Average = 115ms

Tracing route to 159.100.232.177 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.126.144.1
3 8 ms 7 ms 7 ms nott-core-2a-ae12-1246.network.virginmedia.net [62.255.231.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 15 ms 20 ms 29 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
9 15 ms 15 ms 29 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
10 18 ms 24 ms 16 ms 80.150.170.5
11 118 ms 120 ms 115 ms 217.239.44.14
12 115 ms 114 ms 117 ms 193.159.226.18
13 115 ms 113 ms 115 ms ns99.rookdns.com [195.122.154.4]
14 118 ms 116 ms * 159.100.232.177
15 120 ms 116 ms 116 ms 159.100.232.177

Trace complete.

Pinging 159.100.232.24 with 32 bytes of data:
Reply from 159.100.232.24: bytes=32 time=113ms TTL=49
Reply from 159.100.232.24: bytes=32 time=114ms TTL=49
Reply from 159.100.232.24: bytes=32 time=112ms TTL=49
Reply from 159.100.232.24: bytes=32 time=112ms TTL=49

Ping statistics for 159.100.232.24:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 114ms, Average = 112ms

Tracing route to 159.100.232.24 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 7 ms 7 ms 10.126.144.1
3 8 ms 9 ms 7 ms nott-core-2a-ae12-1249.network.virginmedia.net [62.255.231.45]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 15 ms 14 ms 16 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
9 16 ms 15 ms 16 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
10 17 ms 17 ms 16 ms 80.150.170.5
11 * 119 ms 116 ms 217.239.45.230
12 111 ms 112 ms 110 ms 193.159.226.18
13 114 ms 114 ms 112 ms ns99.rookdns.com [195.122.154.4]
14 112 ms 112 ms 115 ms 159.100.232.24

Trace complete.

cymap · 28-02-2015, 21:44

Yeah it seems I get similar results to you with that ip. I just want to know is it virgin side or ESO . The time outs seem to be between virgin but would like someone to confirm.

tracert 159.100.232.177

Tracing route to 159.100.232.177 over a maximum of 30 hops

1 5 ms 7 ms 7 ms 10.188.80.1
2 9 ms 8 ms 7 ms bagu-core-2a-xe-120-0.network.virginmedia.net [8
0.2.12.65]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 15 ms 13 ms 20 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254
.42.90]
8 13 ms 13 ms 14 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162
]
9 14 ms 13 ms 12 ms 80.150.170.5
10 111 ms 110 ms 112 ms 217.239.45.206
11 111 ms 108 ms 108 ms 193.159.226.18
12 113 ms 109 ms 109 ms ns99.rookdns.com [195.122.154.4]
13 109 ms 110 ms 111 ms 159.100.232.177

Trace complete.

General Maximus · 28-02-2015, 22:57

I wouldn't worry about it atm, Ingi said there is a major saturation fault at the core of VM's network and they are working on it so I imagine it will be fixed by lunchtime tomorrow.

lardboy · 01-03-2015, 02:03

I really think this is something to do with the P2P throttling.

Testing again outside of the throttling period and ping in game is about 60 down from close to 200 earlier in the day.

Test results on the same IPs as before are -

Pinging 159.100.232.177 with 32 bytes of data:
Reply from 159.100.232.177: bytes=32 time=50ms TTL=49
Reply from 159.100.232.177: bytes=32 time=50ms TTL=49
Reply from 159.100.232.177: bytes=32 time=54ms TTL=49
Reply from 159.100.232.177: bytes=32 time=49ms TTL=49

Ping statistics for 159.100.232.177:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 54ms, Average = 50ms

Tracing route to 159.100.232.177 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.126.144.1
3 7 ms 7 ms 7 ms nott-core-2a-ae12-1246.network.virginmedia.net [62.255.231.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 20 ms 14 ms 15 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
9 17 ms 16 ms 16 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
10 16 ms 19 ms 16 ms 80.150.170.5
11 32 ms 32 ms 58 ms 217.239.44.14
12 38 ms 33 ms 32 ms 193.159.226.18
13 32 ms 31 ms 33 ms ns99.rookdns.com [195.122.154.4]
14 32 ms 30 ms 32 ms 159.100.232.177

Trace complete.

Pinging 159.100.232.24 with 32 bytes of data:
Reply from 159.100.232.24: bytes=32 time=42ms TTL=49
Reply from 159.100.232.24: bytes=32 time=43ms TTL=49
Reply from 159.100.232.24: bytes=32 time=52ms TTL=49
Reply from 159.100.232.24: bytes=32 time=48ms TTL=49

Ping statistics for 159.100.232.24:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 52ms, Average = 46ms

Tracing route to 159.100.232.24 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 8 ms 6 ms 10.126.144.1
3 18 ms 9 ms 7 ms nott-core-2a-ae12-1249.network.virginmedia.net [62.255.231.45]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 19 ms 16 ms 14 ms popl-bb-1b-ae0-0.network.virginmedia.net [62.254.42.90]
9 16 ms 15 ms 15 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
10 16 ms 16 ms 17 ms 80.150.170.5
11 29 ms 28 ms 27 ms 217.239.45.230
12 29 ms 27 ms 27 ms 193.159.226.18
13 28 ms 27 ms 29 ms ns99.rookdns.com [195.122.154.4]
14 29 ms 29 ms 27 ms 159.100.232.24

Trace complete.

qasdfdsaq · 01-03-2015, 05:18

Quote:

Originally Posted by cymap

Yeah it seems I get similar results to you with that ip. I just want to know is it virgin side or ESO .

Neither. Your traceroutes are perfectly normal and show no issues whatsoever.

Quote:

The time outs seem to be between virgin but would like someone to confirm.

Intermediate timeouts are irrelevant. There are no timeouts to your actual destination.

---------- Post added at 05:18 ---------- Previous post was at 05:17 ----------

Quote:

Originally Posted by General Maximus

I wouldn't worry about it atm, Ingi said there is a major saturation fault at the core of VM's network and they are working on it so I imagine it will be fixed by lunchtime tomorrow.

None of the traceroutes posted so far show any signs of saturation anywhere. Rather the opposite, they seem to show unusually low saturation and perfect consistency.

The only issue appears to be they're tracing to US servers. Could be an anycast address that is getting routed wrong.

AbraXuS · 01-03-2015, 16:03

Hey i'm having the same issue after a quick google search i found this thread.

I made a post on the ESO forums.

http://forums.elderscrollsonline.com...rrible-latency

Anyone any ideas?

General Maximus · 01-03-2015, 16:22

funny how everyone seems to be saying they are with Virgin and you haven't got any Infinity/PlusNet etc on there.

toytown · 01-03-2015, 17:10

I have issues playing League Of Legends between 7pm and 11:30pm on my VirginMedia connection. Yet as soon as i connect using a VPN, then my latency drops from 150ms to 25ms in game. However pinging gmail.com and other addresses from VM all seem to be low.

cymap · 01-03-2015, 20:13

Well it seems to be a Virgin problem as 1 guy on eso forums has tethered his 3 phone and ran the game and the problem has stopped. So who do we need to contact??

qasdfdsaq · 02-03-2015, 04:24

Quote:

Originally Posted by General Maximus

funny how everyone seems to be saying they are with Virgin and you haven't got any Infinity/PlusNet etc on there.

Obviously at other timeserver it's just BT customers having problems and you haven't gotany VM on there we wouldn't be aware of it to begin with.

pip08456 · 02-03-2015, 14:13

Got to agree with qas here.

I see gaming problems on the BT help site and nothing related on here or Virgin's one and visa versa.

Different routing by ISP's etc, etc.

toytown · 03-03-2015, 14:40

Quote:

Originally Posted by lardboy

I really think this is something to do with the P2P throttling.

I'm pretty sure it is, my ICMP pings to the game servers are always super low (20-40ms). But to the same IP address, my in game 'ping' (non icmp) is typically 90-170ms, during peak hours. Also, my ingame ping is pretty stable it doesnt bounce around, almost like it's being throttled with a static delay attached to it.

Using a VPN completely removes the problem.

qasdfdsaq · 04-03-2015, 23:45

Are you sure you are actually pinging the specific node you are connected to at that exact time? If so it ought to be reported to VM, they're usually quite good at dealing with these sorts of false detections... eventually.

toytown · 05-03-2015, 11:46

Quote:

Originally Posted by qasdfdsaq

Are you sure you are actually pinging the specific node you are connected to at that exact time? If so it ought to be reported to VM, they're usually quite good at dealing with these sorts of false detections... eventually.

Yes, its the only IP address that is sending and receiving any data every second whilst im monitoring it. VM do normally fix this, but this is the 3rd or 4th time I've mentioned this over the last 2 years, so I've just learnt to have to suck it up and deal with it. It's a shame i have to resort to a VPN to actually have a proper working service

League Of Legends outputs network logs every 10,000 packets, including the in game ping, so its really easy to go back over previous games and see the average ping through the match. Below is the difference a VPN is making during peak hours for 1 of those games.
Untitled-2.jpg