Selective latency issues

[#1]

Hi all,
CSGO matchmaking is giving me weird ping issues. There's nothing wrong with my connection, and I haven't changed anything, so it's either a plusnet problem or a valve problem.
My friends are having no issues, so I'm leaning toward the former.
Is this tracert normal? I repeated it.

Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:
  1    70 ms    97 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    28 ms    13 ms    16 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
  3    14 ms    14 ms    14 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.17
6]
  4    14 ms    13 ms    13 ms  xe-1-2-0.pcl-cr01.plus.net [212.159.0.208]
  5    14 ms    14 ms    13 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    24 ms    17 ms    16 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    13 ms    14 ms    14 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    15 ms    16 ms    15 ms  132.185.255.149
11    14 ms    13 ms    12 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]
Trace complete.
C:\Users\David>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:
  1    69 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    20 ms    13 ms    13 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
  3    14 ms    13 ms    13 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.17
6]
  4    13 ms    13 ms    13 ms  xe-1-2-0.pcl-cr01.plus.net [212.159.0.208]
  5    14 ms    13 ms    13 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    13 ms    13 ms    13 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    14 ms    17 ms    14 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    14 ms    14 ms    15 ms  132.185.255.149
11    13 ms    13 ms    13 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]
Trace complete.

Any ideas?

[#2]

Well... is this just a gaming issue? The BBC website isn't a game at any rate, and if there is a problem with my routing I'd like it fixed.
And do threads in here get the required attention? I haven't noticed many replies coming from non-gamers...

[#3]

Your opening question was about game pings which is why I moved it
There is nothing obviously wrong with your tracert other than the first hop - is that wireless - which router is it
This is mine - note I am interleaved hence the higher numbers
Tracing route to bbc.co.uk [212.58.246.103]
over a maximum of 30 hops:
 1    <1 ms    <1 ms    <1 ms  192.168.1.254
 2    42 ms    36 ms    32 ms  lo0-central10.pcl-ag04.plus.net [195.166.128.185]
 3    34 ms    38 ms    36 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.172]
 4    42 ms    48 ms    36 ms  xe-0-2-0.pcl-cr01.plus.net [212.159.0.204]
 5    36 ms    36 ms    34 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
 6    33 ms    34 ms    34 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
 7     *        *        *     Request timed out.
 8    33 ms    33 ms    33 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
 9    34 ms    33 ms    34 ms  132.185.255.165
10    34 ms    33 ms    33 ms  fmt-vip132.cwwtf.bbc.co.uk [212.58.246.103]
Trace complete.
However to the same IP address you have I get
C:\Users\Jim>tracert 212.58.244.18
Tracing route to fmt-vip72.telhc.bbc.co.uk [212.58.244.18]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.254
  2    35 ms    51 ms    38 ms  lo0-central10.pcl-ag04.plus.net [195.166.128.185]
  3    33 ms    32 ms    33 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.174]
  4    33 ms    32 ms    32 ms  xe-0-2-0.pcl-cr02.plus.net [212.159.0.206]
  5    35 ms    33 ms    34 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
  6    37 ms    38 ms    57 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  7    37 ms    38 ms    39 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    33 ms    34 ms    32 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11    35 ms    34 ms    32 ms  132.185.255.149
12    39 ms    41 ms    39 ms  fmt-vip72.telhc.bbc.co.uk [212.58.244.18]
Trace complete.
I am not sure why you are getting a different site at the BBC - I assume it must be your DNS lookup as I use Google

[#4]

Hi mate, I too am getting lag in csgo all of a sudden. I am getting around 140 ping ingame, but through cmd prompt when pinging i only get 40ish. It's got to be a plus.net issue

[#5]

Ah, so there's nothing wrong with a couple of time-outs in a tracert?
No, my wireless is turned off and I'm connected on a short cable. Could it be my firewall slowing the initial ping request? I'm using bitdefender.
(Note that this can't be the cause of my matchmaking ping issues, as I've been using bitdefender since I built this pc over a month ago.)#
Router is a Thomson:
Product Name: TG585 v8
Software Release:      8.2.7.8

Quote from: zommy

Hi mate, I too am getting lag in csgo all of a sudden. I am getting around 140 ping ingame, but through cmd prompt when pinging i only get 40ish. It's got to be a plus.net issue

Someone on the steam forums was confident it was an ISP issue also. Funny that it only affects matchmaking... Funny and rather annoying 

[#6]

Yeah, it's only MM for some reason. I can play community servers without any lag now that you mention it..

[#7]

I've done some pathping's and I'm getting mega-loss to here:
195.166.128.186  (lo0-central10.pcl-ag05.plus.net)
and here:
4.69.148.225 (ae-7-7.car1.Luxembourg1.Leve13.net)
(Although now the Luxembourg one seems better. Plusnet one is still lost packet central.)

[#8]

To help you we need the servers IP address, join a match where you are expecting lag and from dos window[as you mentioned pathping you know how to] type netstat -nb and note the Established connection for the game.
Then you would run a pathping to that IP address to find out where the problem is.

[#9]

I'm not joining a server where I'm expecting lag, that would mean playing 30-40 minutes of ruined matchmaking!
The pathpings I already ran were to a valve MM server. If that plusnet hop isn't the problem then I have no clue what is.
*edit
Pinging 195.166.128.186 again now and I get near 100% loss. That's the same plusnet hop as before. It seems to respond to the first packet quite often, but then none of the others for 2 or 3 "pings" in a row.

[#10]

Just give us the IP address of a known laggy server, join one get the IP address and leave.  Without that IP address to test with, nothing can be done to see if its within PNs control or not.

[#11]

seeing as I have the exact same issue, please see the server stats below.
hostname: Valve CS:GO EU West Server (srcds144.134.18)
version : 1.34.7.6/13476 5949 secure 
udp/ip  : 146.66.158.163:27032
os      :  Linux
type    :  official dedicated
map    : de_nuke
Tracert below
  1    3 ms    3 ms    3 ms  192.168.1.254
  2    38 ms    29 ms    39 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
  3    30 ms    34 ms    40 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.16
2]
  4    31 ms    28 ms    29 ms  xe-10-0-0.pcl-cr02.plus.net [212.159.0.194]
  5    29 ms    30 ms    29 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    30 ms    28 ms    29 ms  xe-11-2-0.edge3.London2.Level3.net [212.187.201.
213]
  7    43 ms    42 ms    42 ms  ae-7-7.car1.Luxembourg1.Level3.net [4.69.148.225
]
  8    79 ms    80 ms    79 ms  212.73.249.30
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12  ^C
Please note that i normally get around 35-40 here and last night I was getting 140 (today only 80)

[#12]

Zommy as you can see slightly different routing to it as I am on a different gateway, but as expected its level3 handling the traffic to Europe, which is more than likely to be at fault.  If the high pings start on a plusnet node and continue out to the server then yes it is Plusnets fault, but if they start on level3 node then it is them.
Plusnet pay level3 to route the traffic to USA and Europe, but from what I have seen they can't get them to do anything about it

[#13]

Ok, so what do we do in this situation?
Do you raise a ticket with Level3 and get them to check their routing?

[#14]

146.66.159.25:27032
C:\Users\David>tracert 146.66.159.25
Tracing route to 146.66.159.25 over a maximum of 30 hops
  1    70 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    15 ms    18 ms    13 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
  3    13 ms    14 ms    13 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.17
8]
  4    13 ms    13 ms    13 ms  xe-1-2-0.pcl-cr02.plus.net [212.159.0.210]
  5    14 ms    13 ms    13 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    13 ms    13 ms    14 ms  xe-11-1-0.edge3.London2.Level3.net [212.187.201.
209]
  7    27 ms    34 ms    28 ms  ae-7-7.car1.Luxembourg1.Level3.net [4.69.148.225
]
  8  116 ms  116 ms  115 ms  212.73.249.30
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17    *        *        *    Request timed out.
18    *
If some third party isn't delivering on what plusnet has contracted them to do, that's certainly plusnet's problem, and not mine!
I'm not sure why this would only affect matchmaking servers, and not other servers in the EU (or indeed, other games). Also, aren't plenty of valve's MM servers in the uk?

[#15]

closest MM server is actually Luxenburg, nothing over here
I think the reason community servers dont have this lag is because they are actually based here in the UK therefore don't have the same route. I actually find that SOME arms race servers are fine. perhaps this is because I'm joining a server in vienna or stockholm.
But definitely a Plusnet issue. We shouldn't have to suffer. Plusnet pay them, they should deal with them and get this issue resolved. This won't just be affecting the two of us, i'm sure more will report this shortly.