cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
303 Views
Message 1 of 2

BT Can you identify the reason for this?

I'm confident now that this isn't a fault of BT, but someone needs to look into this. Other ISP's have looked into this and verified it isn't a problem on their end and said there is nothing further they can do about it.

 

The problem is higher pings and extremely weird latency to Valves official Matchmaking servers in both CS:GO and Dota 2. This could affect other games from other companies but these are the two I know about for sure.

 

While playing CS:GO on any official Matchmaking servers (community servers are fine), like many people from many locations in the EU on a few different ISP's (although the majority seem to be from the UK and many on BT) I'm experiencing high pings, 2 to the 3 times what they were a few months ago. Pings are also very inconsistent and actual gameplay has the feeling of playing with 200-300ms ping regardless of ping. This is on every single EU Matchmaking server but EU West servers are affected the most.

 

I'm taking here about delays between kills, dieing way around corners and generally a horrible experience when compared to how the game was before these problems started. It's literally unplayable.

 

Now, get this. If I play through a Russian VPN using Hotspot Shield, my pings drop to as low as in the 30s from as high as triple digits and the 'weird lag' i mentioned is completely gone.

 

If I play through a UK VPN the problems remain.

 

If I play through a Swedish VPN the ping is a bit lower, but still relatively inconsistent and the 'weird lag' is back.

 

There is definitely something wrong here, but who is to blame? There has to be a routing issue somewhere that needs to be looked into that the customer has no ability to do. Noone is taking the blame for this problem, not ISP's and not Valve and as far as I know, noone in between.

 

All in all, routing myself via Russia is giving me a much much much better quality experience. Who'da thunk it?

 

Even if this is not a fault of BT, surely they should be able to reroute traffic somehow to avoid the problem, at least until it's fixed (if ever, it's been close to a year now for me).

 

Here are some pings to Luxembourg/EU west connected normally and through VPNs and a tracert connected normally.

 

Ping connected normally

 

 

ping -n 20 146.66.152.1

Pinging 146.66.152.1 with 32 bytes of data:
Reply from 146.66.152.1: bytes=32 time=89ms TTL=47
Reply from 146.66.152.1: bytes=32 time=72ms TTL=47
Reply from 146.66.152.1: bytes=32 time=73ms TTL=47
Reply from 146.66.152.1: bytes=32 time=65ms TTL=47
Reply from 146.66.152.1: bytes=32 time=72ms TTL=47
Reply from 146.66.152.1: bytes=32 time=69ms TTL=47
Reply from 146.66.152.1: bytes=32 time=74ms TTL=47
Reply from 146.66.152.1: bytes=32 time=65ms TTL=47
Reply from 146.66.152.1: bytes=32 time=78ms TTL=47
Reply from 146.66.152.1: bytes=32 time=89ms TTL=47
Reply from 146.66.152.1: bytes=32 time=88ms TTL=47
Reply from 146.66.152.1: bytes=32 time=75ms TTL=47
Reply from 146.66.152.1: bytes=32 time=87ms TTL=47
Reply from 146.66.152.1: bytes=32 time=73ms TTL=47
Reply from 146.66.152.1: bytes=32 time=73ms TTL=47
Reply from 146.66.152.1: bytes=32 time=95ms TTL=47
Reply from 146.66.152.1: bytes=32 time=62ms TTL=47
Reply from 146.66.152.1: bytes=32 time=94ms TTL=47
Reply from 146.66.152.1: bytes=32 time=106ms TTL=47
Reply from 146.66.152.1: bytes=32 time=65ms TTL=47

Ping statistics for 146.66.152.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 106ms, Average = 78ms

 

Tracert connected normally

 

 

tracert 146.66.152.1

Tracing route to gw.lux.valve.net [146.66.152.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  BThomehub.home [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    13 ms    13 ms    13 ms  217.41.217.77
  5    14 ms    14 ms    13 ms  213.120.181.74
  6    13 ms    13 ms    14 ms  217.41.169.61
  7    13 ms    14 ms    14 ms  217.41.169.107
  8    13 ms    13 ms    13 ms  acc1-10GigE-2-1-3.sf.21cn-ipp.bt.net [109.159.255.163]
  9    17 ms    19 ms    17 ms  217.32.170.16
 10    17 ms    17 ms    16 ms  peer2-et-8-3-0.faraday.ukcore.bt.net [62.6.201.197]
 11    17 ms    16 ms    17 ms  213.137.183.96
 12    19 ms    20 ms    19 ms  linx.valve.net [195.66.226.130]
 13     *        *        *     Request timed out.
 14    43 ms    42 ms    42 ms  162-254-196-139.valve.net [162.254.196.139]
 15     *        *        *     Request timed out.
 16    49 ms    49 ms    49 ms  162-254-197-128.valve.net [162.254.197.128]
 17     *        *        *     Request timed out.
 18    86 ms    70 ms    90 ms  gw.lux.valve.net [146.66.152.1]

Trace complete.

 

Ping connected through Russian VPN using Hotspot Shield (Much lower pings. In game 'weird lag/latency' is completely gone).

 

ping -n 20 146.66.152.1

Pinging 146.66.152.1 with 32 bytes of data&colon;
Reply from 146.66.152.1: bytes=32 time=58ms TTL=60
Reply from 146.66.152.1: bytes=32 time=46ms TTL=60
Reply from 146.66.152.1: bytes=32 time=45ms TTL=60
Reply from 146.66.152.1: bytes=32 time=46ms TTL=60
Reply from 146.66.152.1: bytes=32 time=44ms TTL=60
Reply from 146.66.152.1: bytes=32 time=51ms TTL=60
Reply from 146.66.152.1: bytes=32 time=56ms TTL=59
Reply from 146.66.152.1: bytes=32 time=53ms TTL=60
Reply from 146.66.152.1: bytes=32 time=58ms TTL=59
Reply from 146.66.152.1: bytes=32 time=51ms TTL=59
Reply from 146.66.152.1: bytes=32 time=56ms TTL=60
Reply from 146.66.152.1: bytes=32 time=44ms TTL=59
Reply from 146.66.152.1: bytes=32 time=47ms TTL=59
Reply from 146.66.152.1: bytes=32 time=49ms TTL=59
Reply from 146.66.152.1: bytes=32 time=46ms TTL=60
Reply from 146.66.152.1: bytes=32 time=48ms TTL=60
Reply from 146.66.152.1: bytes=32 time=49ms TTL=59
Reply from 146.66.152.1: bytes=32 time=39ms TTL=60
Reply from 146.66.152.1: bytes=32 time=54ms TTL=60
Reply from 146.66.152.1: bytes=32 time=42ms TTL=60

Ping statistics for 146.66.152.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 58ms, Average = 49ms

Ping connected through Swedish VPN using Hotspot Shield (Much lower pings. In game 'weird lag/latency' remains).

 

ping -n 20 146.66.152.1

Pinging 146.66.152.1 with 32 bytes of data&colon;
Reply from 146.66.152.1: bytes=32 time=39ms TTL=59
Reply from 146.66.152.1: bytes=32 time=39ms TTL=60
Reply from 146.66.152.1: bytes=32 time=54ms TTL=60
Reply from 146.66.152.1: bytes=32 time=43ms TTL=59
Reply from 146.66.152.1: bytes=32 time=44ms TTL=59
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=42ms TTL=59
Reply from 146.66.152.1: bytes=32 time=41ms TTL=59
Reply from 146.66.152.1: bytes=32 time=51ms TTL=59
Reply from 146.66.152.1: bytes=32 time=39ms TTL=60
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=59ms TTL=59
Reply from 146.66.152.1: bytes=32 time=42ms TTL=60
Reply from 146.66.152.1: bytes=32 time=44ms TTL=60
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=41ms TTL=60
Reply from 146.66.152.1: bytes=32 time=51ms TTL=59
Reply from 146.66.152.1: bytes=32 time=58ms TTL=60

Ping statistics for 146.66.152.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 59ms, Average = 46ms

Ping connected through Netherlands VPN using Hotspot Shield (Lower pings. In game 'weird lag/latency' is there sometimes, sometimes not depending on the server).

 

ping -n 20 146.66.152.1

Pinging 146.66.152.1 with 32 bytes of data&colon;
Reply from 146.66.152.1: bytes=32 time=72ms TTL=59
Reply from 146.66.152.1: bytes=32 time=50ms TTL=60
Reply from 146.66.152.1: bytes=32 time=51ms TTL=60
Reply from 146.66.152.1: bytes=32 time=55ms TTL=59
Reply from 146.66.152.1: bytes=32 time=52ms TTL=60
Reply from 146.66.152.1: bytes=32 time=55ms TTL=59
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=54ms TTL=60
Reply from 146.66.152.1: bytes=32 time=55ms TTL=60
Reply from 146.66.152.1: bytes=32 time=49ms TTL=60
Reply from 146.66.152.1: bytes=32 time=46ms TTL=60
Reply from 146.66.152.1: bytes=32 time=65ms TTL=60
Reply from 146.66.152.1: bytes=32 time=46ms TTL=59
Reply from 146.66.152.1: bytes=32 time=65ms TTL=60
Reply from 146.66.152.1: bytes=32 time=65ms TTL=60
Reply from 146.66.152.1: bytes=32 time=47ms TTL=60
Reply from 146.66.152.1: bytes=32 time=50ms TTL=60
Reply from 146.66.152.1: bytes=32 time=51ms TTL=59
Reply from 146.66.152.1: bytes=32 time=55ms TTL=59
Reply from 146.66.152.1: bytes=32 time=46ms TTL=60

Ping statistics for 146.66.152.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 72ms, Average = 53ms

Ping connected through German VPN using Hotspot Shield (Lower pings. In game 'weird lag/latency' is there sometimes, sometimes not depending on the server).

 

ping -n 20 146.66.152.1

Pinging 146.66.152.1 with 32 bytes of data&colon;
Reply from 146.66.152.1: bytes=32 time=71ms TTL=57
Reply from 146.66.152.1: bytes=32 time=59ms TTL=57
Reply from 146.66.152.1: bytes=32 time=50ms TTL=57
Reply from 146.66.152.1: bytes=32 time=73ms TTL=57
Reply from 146.66.152.1: bytes=32 time=54ms TTL=57
Reply from 146.66.152.1: bytes=32 time=63ms TTL=57
Reply from 146.66.152.1: bytes=32 time=73ms TTL=57
Reply from 146.66.152.1: bytes=32 time=68ms TTL=57
Reply from 146.66.152.1: bytes=32 time=55ms TTL=57
Reply from 146.66.152.1: bytes=32 time=65ms TTL=57
Reply from 146.66.152.1: bytes=32 time=71ms TTL=57
Reply from 146.66.152.1: bytes=32 time=70ms TTL=57
Reply from 146.66.152.1: bytes=32 time=83ms TTL=57
Reply from 146.66.152.1: bytes=32 time=62ms TTL=57
Reply from 146.66.152.1: bytes=32 time=63ms TTL=57
Reply from 146.66.152.1: bytes=32 time=70ms TTL=57
Reply from 146.66.152.1: bytes=32 time=57ms TTL=57
Reply from 146.66.152.1: bytes=32 time=62ms TTL=57
Reply from 146.66.152.1: bytes=32 time=57ms TTL=57
Reply from 146.66.152.1: bytes=32 time=61ms TTL=57

Ping statistics for 146.66.152.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 83ms, Average = 64ms

 Ping connected through British VPN using Hotspot Shield (Pings around the same as being connected normally. In game 'weird lag/latency' remains).

 

ping -n 20 146.66.152.1

Pinging 146.66.152.1 with 32 bytes of data&colon;
Reply from 146.66.152.1: bytes=32 time=70ms TTL=55
Reply from 146.66.152.1: bytes=32 time=70ms TTL=55
Reply from 146.66.152.1: bytes=32 time=63ms TTL=55
Reply from 146.66.152.1: bytes=32 time=71ms TTL=55
Reply from 146.66.152.1: bytes=32 time=67ms TTL=55
Reply from 146.66.152.1: bytes=32 time=60ms TTL=55
Reply from 146.66.152.1: bytes=32 time=69ms TTL=55
Reply from 146.66.152.1: bytes=32 time=69ms TTL=55
Reply from 146.66.152.1: bytes=32 time=62ms TTL=55
Reply from 146.66.152.1: bytes=32 time=74ms TTL=55
Reply from 146.66.152.1: bytes=32 time=60ms TTL=55
Reply from 146.66.152.1: bytes=32 time=62ms TTL=55
Reply from 146.66.152.1: bytes=32 time=61ms TTL=55
Reply from 146.66.152.1: bytes=32 time=80ms TTL=55
Reply from 146.66.152.1: bytes=32 time=64ms TTL=55
Reply from 146.66.152.1: bytes=32 time=66ms TTL=55
Reply from 146.66.152.1: bytes=32 time=75ms TTL=55
Reply from 146.66.152.1: bytes=32 time=75ms TTL=55
Reply from 146.66.152.1: bytes=32 time=74ms TTL=55
Reply from 146.66.152.1: bytes=32 time=71ms TTL=55

Ping statistics for 146.66.152.1:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum = 80ms, Average = 68ms

 

0 Ratings
1 REPLY 1
Highlighted
Contributor
211 Views
Message 2 of 2

Re: BT Can you identify the reason for this?

I think you need to ask Valve not BT

0 Ratings