Menu
Reply
  • 33
  • 0
  • 2
ianbrown313
Tuning in
374 Views
Message 31 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

@Kippies.

League of legends tracert

Stuck on hop 5 for 1 min at least.

Tracing route to 104.160.141.3 over a maximum of 30 hops

  1. 1 4 ms 3 ms 4 ms 192.168.0.1
    2 * * * Request timed out.
    3 15 ms 14 ms 16 ms renf-core-2b-xe-103-0.network.virginmedia.net [62.252.129.93]
    4 * * * Request timed out.
    5 * * * Request timed out.
    6     34 ms 21 ms 26 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
    7    23 ms 28 ms 26 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
    8 * * * Request timed out.
    9 * * * Request timed out.
    10  31 ms 33 ms 31 ms nl-ams04a-ri2-ae6-0.aorta.net [84.116.135.182]
    11  34 ms 33 ms 31 ms 213.46.182.2
    12 * * * Request timed out.
    13  39 ms 35 ms 32 ms 104.160.141.3

 

Wow. with updated WinMtr.

Tracing route to 185.60.112.157 over a maximum of 30 hops

1   1 ms 4 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3   12 ms 17 ms 15 ms renf-core-2b-xe-103-0.network.virginmedia.net [62.252.129.93]
4 * * * Request timed out.
5 * * * Request timed out.
6   27 ms 21 ms 30 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
7   26 ms 26 ms 29 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8   31 ms 26 ms 25 ms be6830.ccr22.lon01.atlas.cogentco.com [130.117.14.17]
9   27 ms 27 ms * be2870.ccr41.lon13.atlas.cogentco.com [154.54.58.173]
10 40 ms 35 ms 28 ms be12194.ccr41.ams03.atlas.cogentco.com [154.54.56.94]
11 * * 33 ms be2322.rcr21.b021535-1.ams03.atlas.cogentco.com [130.117.50.82]
12 * 32 ms * blizzard.demarc.cogentco.com [149.6.128.9]
13 * * * Request timed out.
14  32 ms 34 ms 31 ms 185.60.112.157

Wow 11.30 amWow 11.30 am

Final fantasy 14

Tracert and WinMtr

Tracing route to eu.square-enix.com [209.130.141.243]
over a maximum of 30 hops:

1 13 ms 6 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 14 ms 12 ms renf-core-2b-xe-103-0.network.virginmedia.net [62.252.129.93]
4 * * * Request timed out.
5 * * * Request timed out.
6 21 ms 21 ms 24 ms nrth-ic-1-ae1-0.network.virginmedia.net [62.254.42.218]
7 26 ms 26 ms 26 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 * * * Request timed out.
9 23 ms 27 ms 26 ms uk-lon01c-ri1-ae4-0.aorta.net [84.116.135.50]
10 26 ms 27 ms 41 ms 213.46.174.170
11 * * 29 ms ae-228-3604.edge3.London15.Level3.net [4.69.167.102]
12 33 ms 24 ms 21 ms ae-228-3604.edge3.London15.Level3.net [4.69.167.102]
13 33 ms 26 ms 24 ms gblx-level3-50g.London15.Level3.net [4.68.110.158]
14 31 ms 26 ms 38 ms eidos-vpn.gigabitethernet3-39.ar4.lon3.gblx.net [64.213.77.134]
15 34 ms 24 ms 23 ms 209.130.141.196
16 28 ms 28 ms 23 ms eu.square-enix.com [209.130.141.243]

ff14ff14

its happening with all games and xbox/ps4. games freeze 10 secs later comes back and im dead or 200 meters from where i was. some severe packet loss.

All the tracers where hanging from hop 5 onwards taking ages to get a response

 

 

0 Kudos
Reply
  • 33
  • 0
  • 2
ianbrown313
Tuning in
368 Views
Message 32 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

0 Kudos
Reply
  • 11
  • 0
  • 0
ScottishChamp
Tuning in
350 Views
Message 33 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

Is there a Mac alternative to win-mtr ? 

I did the below using Blizzards own service (for overwatch) but not sure if this is the same thing ?

TRACEROUTE:
traceroute to 81.99.228.188 (81.99.228.188), 15 hops max, 60 byte packets
1 5.42.188.5 (5.42.188.5) 0.621 ms 0.666 ms 0.865 ms
2 Blizzard (Blizzard) 1.220 ms 1.285 ms 1.332 ms
3 37.244.9.102 (37.244.9.102) 0.822 ms 0.862 ms 0.919 ms
4 24.105.31.19 (24.105.31.19) 8.753 ms 8.815 ms 8.888 ms
5 37.244.11.32 (37.244.11.32) 8.512 ms 8.577 ms 8.629 ms
6 62.115.145.216 (62.115.145.216) 9.046 ms 30.822 ms 30.803 ms
7 213.46.174.117 (213.46.174.117) 9.349 ms 9.355 ms 9.345 ms
8 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 15.721 ms 15.753 ms 15.742 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 renf-core-2a-ae5-0.network.virginmedia.net (62.254.84.46) 24.003 ms 23.992 ms 23.970 ms
15 * * *


14/03/2017 12:33:59 UTC
--------------------

TRACEROUTE:
traceroute to 81.99.228.188 (81.99.228.188), 15 hops max, 60 byte packets
1 5.42.168.5 (5.42.168.5) 0.719 ms 0.876 ms 1.159 ms
2 Blizzard (Blizzard) 0.955 ms 1.011 ms 1.033 ms
3 37.244.10.102 (37.244.10.102) 0.904 ms 0.963 ms 1.004 ms
4 24.105.31.31 (24.105.31.31) 6.904 ms 6.962 ms 7.026 ms
5 37.244.11.32 (37.244.11.32) 7.133 ms 7.321 ms 7.410 ms
6 62.115.145.216 (62.115.145.216) 7.248 ms 7.331 ms 7.316 ms
7 213.46.174.117 (213.46.174.117) 10.564 ms 10.590 ms 10.625 ms
8 brnt-ic-1-ae24-0.network.virginmedia.net (62.254.42.173) 10.048 ms 10.055 ms 10.052 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 renf-core-2a-ae5-0.network.virginmedia.net (62.254.84.46) 18.158 ms 18.185 ms 18.171 ms
15 * * *


14/03/2017 12:33:59 UTC
--------------------

MTR:
Start: Tue Mar 14 12:33:59 2017
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 5.42.188.5 0.0% 10 0.5 0.6 0.5 0.9 0.0
2.|-- Blizzard 0.0% 10 1.2 1.2 0.9 1.3 0.0
3.|-- 37.244.9.102 0.0% 10 0.8 0.9 0.7 1.3 0.0
4.|-- 24.105.31.19 0.0% 10 8.7 8.8 8.7 9.2 0.0
5.|-- 37.244.11.32 0.0% 10 8.6 8.8 8.5 10.0 0.3
6.|-- 62.115.145.216 0.0% 10 9.1 9.2 9.1 9.8 0.0
7.|-- 213.46.174.117 0.0% 10 9.3 9.6 9.3 11.7 0.7
8.|-- brnt-ic-1-ae24-0.network.virginmedia.net 0.0% 10 16.9 19.7 15.7 45.7 9.3
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- renf-core-2a-ae5-0.network.virginmedia.net 0.0% 10 24.1 24.4 24.0 25.1 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- cpc114536-irvi2-2-0-cust187.14-1.cable.virginm.net 20.0% 10 37.7 36.2 33.4 40.6 2.6


14/03/2017 12:33:59 UTC
--------------------

MTR:
Start: Tue Mar 14 12:33:59 2017
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1.|-- 5.42.168.5 0.0% 10 0.5 0.6 0.5 0.9 0.0
2.|-- Blizzard 0.0% 10 1.1 1.2 1.0 1.3 0.0
3.|-- 37.244.10.102 0.0% 10 0.8 0.8 0.8 1.0 0.0
4.|-- 24.105.31.31 0.0% 10 6.8 6.9 6.8 6.9 0.0
5.|-- 37.244.11.32 0.0% 10 6.8 6.7 6.6 6.8 0.0
6.|-- 62.115.145.216 0.0% 10 19.0 14.0 7.2 22.1 7.1
7.|-- 213.46.174.117 0.0% 10 7.5 7.6 7.5 7.6 0.0
8.|-- brnt-ic-1-ae24-0.network.virginmedia.net 0.0% 10 10.1 15.5 10.1 24.4 5.7
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- renf-core-2a-ae5-0.network.virginmedia.net 0.0% 10 18.2 18.3 18.1 18.6 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- cpc114536-irvi2-2-0-cust187.14-1.cable.virginm.net 20.0% 10 30.1 30.4 29.3 32.1 0.8


14/03/2017 12:33:59 UTC
--------------------

 

0 Kudos
Reply
  • 8.29K
  • 515
  • 2.3K
Superuser
Superuser
335 Views
Message 34 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

LOL going to be a hard one to track down going by the results so far.

Reading on a basic level there's a couple of hops in the local infrastructure that seem to spike in latency- read through the

bst,avg,wst on the MTR's

But the pattern is only evident on BQM's

looking at that as a "bigger picture" it may well be a QOS issue- as the NTP trace is following the BQM trace its a fair assumption (but a guess) that everythings queuing instead of being prioritised at the CMTS.

Staff have replied and allocated it across to the correct team- its still likely to be a while before we hear back though. Ill keep pushing it and if anyone else has similair issues can they post a BQM and where they are (general area ONLY, nothing identifiable) and Ill collate and pass it upline.

Thanks

 


  • 3.09K
  • 36
  • 591
Ignition
Trouble shooter
320 Views
Message 35 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

The guy with the NTP issue is in Derby, everyone else seems to be in Ayrshire.

I'm going with either a problem on a router or switch that's aggregating connections in Ayrshire, or a fibre optic cable in need of cleaning of connections or replacement.

BQM and NTP are not using the same stuff. One is ICMP, the other UDP, neither should be impacted by QoS as there shouldn't be any that runs all the time.

0 Kudos
Reply
  • 9
  • 0
  • 3
Callywallyalvin
Tuning in
310 Views
Message 36 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

Same packet loss/ latency spike issue over last 10 days.
North Ayrshire

I could not be happier seeing this post getting some traction.
Been enjoying the VM customer care merrygoround for about 10 days now.
Due to receive a SH3 today in the hopes the issue was my SH1

Started off with Fifa 17 pro clubs ( multiple connections/ 10 players) constant lagging resulting in disconnections from matches at same time as VM customer team mate while others in the party remain.
It's gotten so bad now we are struggling to hold a conversation on Xbox live party without being disconnected.

Doesn't take an expert to work out from this forum it's a faulty piece of VM equipment in our area needing repaired.

I'm now running a quality monitor also and will post results tomorrow
0 Kudos
Reply
  • 23
  • 0
  • 5
ncguk
On our wavelength
299 Views
Message 37 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

Hello - guy with the NTP issue in Derby here. Here's a couple of screengrabs of traceroutes to ntt.com and virginmedia.com. I'm no doctor, but I'm going to go ahead and say they're not ideal.

Screen Shot 2017-03-14 at 2.18.54 pm.pngScreen Shot 2017-03-14 at 2.18.29 pm.png

0 Kudos
Reply
  • 33
  • 0
  • 2
ianbrown313
Tuning in
287 Views
Message 38 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

ncgcuk no offense mate this is a local post for ayrshire your better making a seperate thread
0 Kudos
Reply
  • 33
  • 0
  • 2
ianbrown313
Tuning in
287 Views
Message 39 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

Callywally

i already recieved the SH3 on saturday made no noticeable difference.
  • 23
  • 0
  • 5
ncguk
On our wavelength
276 Views
Message 40 of 139
Flag for a moderator

Re: Dreadful Packet Loss - Ongoing issue that is not going to go away VM!

Nowhere in this thread does it say it's a local thread for local people, and I posted on page 2 about my poor gaming ping and how it also affects NTP. I've posted traceroutes now, as the more information given the better the chances of solving the problem, be it in Ayrshire, Derby or flipping Mars.