Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Made the switch due to having problems with gaming(CS:GO) on BT Infinity.
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Fibre Broadband
- :
- Made the switch due to having problems with gaming...
Made the switch due to having problems with gaming(CS:GO) on BT Infinity.
20-10-2015 9:52 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I've made the switch to Plusnet and will have the service switched over on the 30th of this month, but I was wondering if I'm going to see an improvement over BT Infinity. I play CS:GO competitive matchmaking which at the mo is basically unplayable because of lag/latency on the European servers. If you look at the traceroutes below you'll see the problem shows up when they hit either Telia or Valves network.
Telia seems to be the main problem. When I'm switched over to Plusnet will anything change with the routing or will these problems remain. Does anyone here on Plusnet play CS:GO competitive and if so, what has your experience been like lately? Playing CS:GO matchmaking right now on Infinity is like playing on 56k the latency is so bad, shot/kills delayed by what seems like 500ms along with deaths miles behind cover, dying to people that haven't even come round the corner yet and people moving a meter or so to a new position after Ive killed them.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Tracing route to 155.133.240.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 28 ms 48 ms 50 ms 217.41.217.77
5 14 ms 13 ms 13 ms 213.120.181.166
6 14 ms 14 ms 14 ms 213.120.180.173
7 15 ms 14 ms 14 ms 213.120.179.81
8 14 ms 13 ms 13 ms acc1-xe-0-1-3.sf.21cn-ipp.bt.net [109.159.251.83]
9 22 ms 23 ms 19 ms core2-te-0-13-0-10.ilford.ukcore.bt.net [109.159.251.183]
10 22 ms 23 ms 22 ms peer6-te0-9-0-13.telehouse.ukcore.bt.net [109.159.254.157]
11 21 ms 20 ms 20 ms 166-49-211-236.eu.bt.net [166.49.211.236]
12 19 ms 19 ms 19 ms 213.248.82.249
13 53 ms 35 ms 19 ms ldn-bb2-link.telia.net [62.115.138.156]
14 27 ms 26 ms 114 ms prs-bb2-link.telia.net [62.115.114.231]
15 27 ms 26 ms 38 ms prs-b5-link.telia.net [62.115.113.171]
16 33 ms 31 ms 33 ms valve-ic-157466-prs-b5.c.telia.net [213.248.88.166]
17 77 ms 70 ms 66 ms 155.133.240.1
Trace complete.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
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 12 ms 217.41.217.77
5 14 ms 13 ms 13 ms 213.120.181.238
6 14 ms 13 ms 13 ms 213.120.180.173
7 15 ms 14 ms 14 ms 213.120.179.81
8 14 ms 14 ms 13 ms acc1-xe2-1-2.sf.21cn-ipp.bt.net [109.159.255.161]
9 18 ms 18 ms 19 ms 217.32.170.18
10 18 ms 18 ms 18 ms peer2-et-10-3-0.faraday.ukcore.bt.net [62.6.201.199]
11 18 ms 18 ms 18 ms 213.137.183.100
12 * * * Request timed out.
13 * * * Request timed out.
14 43 ms 44 ms 43 ms 162-254-196-139.valve.net [162.254.196.139]
15 * * * Request timed out.
16 51 ms 49 ms 55 ms 162-254-197-128.valve.net [162.254.197.128]
17 * * * Request timed out.
18 57 ms 58 ms 59 ms gw.lux.valve.net [146.66.152.1]
Trace complete.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Tracing route to 146.66.158.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 12 ms 12 ms 217.41.217.77
5 13 ms 13 ms 13 ms 213.120.181.74
6 14 ms 14 ms 14 ms 213.120.180.173
7 14 ms 14 ms 14 ms 213.120.179.81
8 14 ms 13 ms 13 ms acc1-10GigE-9-3-0.sf.21cn-ipp.bt.net [109.159.251.95]
9 17 ms 17 ms 17 ms 217.32.170.0
10 18 ms 18 ms 18 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.195]
11 18 ms 18 ms 19 ms 213.137.183.100
12 * * * Request timed out.
13 * * * Request timed out.
14 43 ms 44 ms 43 ms 162-254-196-139.valve.net [162.254.196.139]
15 * * * Request timed out.
16 50 ms 50 ms 50 ms 162-254-197-128.valve.net [162.254.197.128]
17 * * * Request timed out.
18 69 ms 81 ms 100 ms 146.66.158.1
Trace complete.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Telia seems to be the main problem. When I'm switched over to Plusnet will anything change with the routing or will these problems remain. Does anyone here on Plusnet play CS:GO competitive and if so, what has your experience been like lately? Playing CS:GO matchmaking right now on Infinity is like playing on 56k the latency is so bad, shot/kills delayed by what seems like 500ms along with deaths miles behind cover, dying to people that haven't even come round the corner yet and people moving a meter or so to a new position after Ive killed them.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Tracing route to 155.133.240.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 28 ms 48 ms 50 ms 217.41.217.77
5 14 ms 13 ms 13 ms 213.120.181.166
6 14 ms 14 ms 14 ms 213.120.180.173
7 15 ms 14 ms 14 ms 213.120.179.81
8 14 ms 13 ms 13 ms acc1-xe-0-1-3.sf.21cn-ipp.bt.net [109.159.251.83]
9 22 ms 23 ms 19 ms core2-te-0-13-0-10.ilford.ukcore.bt.net [109.159.251.183]
10 22 ms 23 ms 22 ms peer6-te0-9-0-13.telehouse.ukcore.bt.net [109.159.254.157]
11 21 ms 20 ms 20 ms 166-49-211-236.eu.bt.net [166.49.211.236]
12 19 ms 19 ms 19 ms 213.248.82.249
13 53 ms 35 ms 19 ms ldn-bb2-link.telia.net [62.115.138.156]
14 27 ms 26 ms 114 ms prs-bb2-link.telia.net [62.115.114.231]
15 27 ms 26 ms 38 ms prs-b5-link.telia.net [62.115.113.171]
16 33 ms 31 ms 33 ms valve-ic-157466-prs-b5.c.telia.net [213.248.88.166]
17 77 ms 70 ms 66 ms 155.133.240.1
Trace complete.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
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 12 ms 217.41.217.77
5 14 ms 13 ms 13 ms 213.120.181.238
6 14 ms 13 ms 13 ms 213.120.180.173
7 15 ms 14 ms 14 ms 213.120.179.81
8 14 ms 14 ms 13 ms acc1-xe2-1-2.sf.21cn-ipp.bt.net [109.159.255.161]
9 18 ms 18 ms 19 ms 217.32.170.18
10 18 ms 18 ms 18 ms peer2-et-10-3-0.faraday.ukcore.bt.net [62.6.201.199]
11 18 ms 18 ms 18 ms 213.137.183.100
12 * * * Request timed out.
13 * * * Request timed out.
14 43 ms 44 ms 43 ms 162-254-196-139.valve.net [162.254.196.139]
15 * * * Request timed out.
16 51 ms 49 ms 55 ms 162-254-197-128.valve.net [162.254.197.128]
17 * * * Request timed out.
18 57 ms 58 ms 59 ms gw.lux.valve.net [146.66.152.1]
Trace complete.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Tracing route to 146.66.158.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 12 ms 12 ms 217.41.217.77
5 13 ms 13 ms 13 ms 213.120.181.74
6 14 ms 14 ms 14 ms 213.120.180.173
7 14 ms 14 ms 14 ms 213.120.179.81
8 14 ms 13 ms 13 ms acc1-10GigE-9-3-0.sf.21cn-ipp.bt.net [109.159.251.95]
9 17 ms 17 ms 17 ms 217.32.170.0
10 18 ms 18 ms 18 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.195]
11 18 ms 18 ms 19 ms 213.137.183.100
12 * * * Request timed out.
13 * * * Request timed out.
14 43 ms 44 ms 43 ms 162-254-196-139.valve.net [162.254.196.139]
15 * * * Request timed out.
16 50 ms 50 ms 50 ms 162-254-197-128.valve.net [162.254.197.128]
17 * * * Request timed out.
18 69 ms 81 ms 100 ms 146.66.158.1
Trace complete.
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Message 1 of 4
(1,009 Views)
3 REPLIES 3
Re: Made the switch due to having problems with gaming(CS:GO) on BT Infinity.
21-10-2015 12:00 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Hi you will get more or less the same with Plusnet the ping to the hops on the BT network are well within norms the higher latency lies out side of the BT network as you said when it hits Telia or Valve, even then it's not super high ie in the Hundreds but i guess for competitive gaming it may still be classed as to much I dunno i don't competitive game I play just for fun.
my trace to the servers are below and more or less the same as yours, sadly There is nothing BT or Plusnet can do about it as it's nothing to do with their networks, have you tried talking to Valve about it ?.
Tracing route to 155.133.240.1 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.254
2 13 ms 13 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 13 ms 13 ms 13 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 12 ms 13 ms 15 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 13 ms 13 ms 13 ms 195.99.126.96
6 13 ms 13 ms 13 ms core3-te0-2-0-18.faraday.ukcore.bt.net [109.159.249.1]
7 13 ms 13 ms 12 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.167]
8 14 ms 13 ms 12 ms 213.137.183.34
9 13 ms 13 ms 13 ms ldn-b3-link.telia.net [213.248.67.97]
10 14 ms 16 ms 13 ms ldn-bb2-link.telia.net [62.115.140.250]
11 20 ms 20 ms 20 ms prs-bb2-link.telia.net [80.91.246.177]
12 21 ms 21 ms 21 ms prs-b5-link.telia.net [62.115.138.127]
13 26 ms 26 ms 26 ms valve-ic-157466-prs-b5.c.telia.net [213.248.88.166]
14 71 ms 75 ms 61 ms 155.133.240.1
Trace complete.
Tracing route to 146.66.152.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 22 ms 12 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 13 ms 13 ms 13 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 13 ms 12 ms 12 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 13 ms 13 ms 13 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 13 ms 13 ms 13 ms linx.valve.net [195.66.226.130]
7 * * * Request timed out.
8 37 ms 36 ms 37 ms 162-254-196-139.valve.net [162.254.196.139]
9 * * * Request timed out.
10 44 ms 44 ms 43 ms 162-254-197-128.valve.net [162.254.197.128]
11 * * * Request timed out.
12 61 ms 60 ms 69 ms 146.66.152.1
Trace complete.
my trace to the servers are below and more or less the same as yours, sadly There is nothing BT or Plusnet can do about it as it's nothing to do with their networks, have you tried talking to Valve about it ?.
Tracing route to 155.133.240.1 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.254
2 13 ms 13 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 13 ms 13 ms 13 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 12 ms 13 ms 15 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 13 ms 13 ms 13 ms 195.99.126.96
6 13 ms 13 ms 13 ms core3-te0-2-0-18.faraday.ukcore.bt.net [109.159.249.1]
7 13 ms 13 ms 12 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.167]
8 14 ms 13 ms 12 ms 213.137.183.34
9 13 ms 13 ms 13 ms ldn-b3-link.telia.net [213.248.67.97]
10 14 ms 16 ms 13 ms ldn-bb2-link.telia.net [62.115.140.250]
11 20 ms 20 ms 20 ms prs-bb2-link.telia.net [80.91.246.177]
12 21 ms 21 ms 21 ms prs-b5-link.telia.net [62.115.138.127]
13 26 ms 26 ms 26 ms valve-ic-157466-prs-b5.c.telia.net [213.248.88.166]
14 71 ms 75 ms 61 ms 155.133.240.1
Trace complete.
Tracing route to 146.66.152.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 22 ms 12 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 13 ms 13 ms 13 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 13 ms 12 ms 12 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 13 ms 13 ms 13 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 13 ms 13 ms 13 ms linx.valve.net [195.66.226.130]
7 * * * Request timed out.
8 37 ms 36 ms 37 ms 162-254-196-139.valve.net [162.254.196.139]
9 * * * Request timed out.
10 44 ms 44 ms 43 ms 162-254-197-128.valve.net [162.254.197.128]
11 * * * Request timed out.
12 61 ms 60 ms 69 ms 146.66.152.1
Trace complete.
Message 2 of 4
(540 Views)
Re: Made the switch due to having problems with gaming(CS:GO) on BT Infinity.
21-10-2015 10:35 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I play CS:GO pretty much daily, although I'm not particularly good. My pings on euro servers average between 30 and 50ms.
As a test have you tried restricting the ping of the servers you search for when matchmaking? Open console in game and type in mm_dedicated_server_maxping 60 - replacing 60 with whatever max ping you want. Obviously if you go too low you may not find any games.
As a test have you tried restricting the ping of the servers you search for when matchmaking? Open console in game and type in mm_dedicated_server_maxping 60 - replacing 60 with whatever max ping you want. Obviously if you go too low you may not find any games.
Former Plusnet Staff member. Posts after 31st Jan 2020 are not on behalf of Plusnet.
Message 3 of 4
(540 Views)
Re: Made the switch due to having problems with gaming(CS:GO) on BT Infinity.
22-10-2015 6:52 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: Terranova667 Hi you will get more or less the same with Plusnet the ping to the hops on the BT network are well within norms the higher latency lies out side of the BT network as you said when it hits Telia or Valve, even then it's not super high ie in the Hundreds but i guess for competitive gaming it may still be classed as to much I dunno i don't competitive game I play just for fun.
my trace to the servers are below and more or less the same as yours, sadly There is nothing BT or Plusnet can do about it as it's nothing to do with their networks, have you tried talking to Valve about it ?.
Tracing route to 155.133.240.1 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 192.168.1.254
2 13 ms 13 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 13 ms 13 ms 13 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 12 ms 13 ms 15 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 13 ms 13 ms 13 ms 195.99.126.96
6 13 ms 13 ms 13 ms core3-te0-2-0-18.faraday.ukcore.bt.net [109.159.249.1]
7 13 ms 13 ms 12 ms peer2-et-9-3-0.faraday.ukcore.bt.net [62.6.201.167]
8 14 ms 13 ms 12 ms 213.137.183.34
9 13 ms 13 ms 13 ms ldn-b3-link.telia.net [213.248.67.97]
10 14 ms 16 ms 13 ms ldn-bb2-link.telia.net [62.115.140.250]
11 20 ms 20 ms 20 ms prs-bb2-link.telia.net [80.91.246.177]
12 21 ms 21 ms 21 ms prs-b5-link.telia.net [62.115.138.127]
13 26 ms 26 ms 26 ms valve-ic-157466-prs-b5.c.telia.net [213.248.88.166]
14 71 ms 75 ms 61 ms 155.133.240.1
Trace complete.
Tracing route to 146.66.152.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 22 ms 12 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 13 ms 13 ms 13 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 13 ms 12 ms 12 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 13 ms 13 ms 13 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 13 ms 13 ms 13 ms linx.valve.net [195.66.226.130]
7 * * * Request timed out.
8 37 ms 36 ms 37 ms 162-254-196-139.valve.net [162.254.196.139]
9 * * * Request timed out.
10 44 ms 44 ms 43 ms 162-254-197-128.valve.net [162.254.197.128]
11 * * * Request timed out.
12 61 ms 60 ms 69 ms 146.66.152.1
Trace complete.
Thanks for the info and doing the Trace routes. I have tried talking to valve about it, but as you might know, Valve aren't very good at talking back. After all the complains I've seen about it they still haven't even acknowledged the problem.
You're right in that the pings aren't overly high, but they aren't great for a competitive game either. The main problem is that valves EU West servers keep jumping up and down between 50 and 150 making the gameplay inconsistent.
This is a common problem though, especially to players in the UK so hopefully Valve will sort it out soon.
Quote from: Chris I play CS:GO pretty much daily, although I'm not particularly good. My pings on euro servers average between 30 and 50ms.
As a test have you tried restricting the ping of the servers you search for when matchmaking? Open console in game and type in mm_dedicated_server_maxping 60 - replacing 60 with whatever max ping you want. Obviously if you go too low you may not find any games.
Yeah I have my max ping set to 30 in my config file but I'm still lucky to see a ping below 60 in most games. Lowest I can ever get these days is 50 when I'm very lucky. But as I said above, it's not the ping that's shown that's the main problem, it's that the pings are always spiking between 50 and 150 but you don't see this on the in-game scoreboard. That's an average of your ping of a certain amount of time. You can see your real ping by typing 'ping' in console which for me is always around twice what is shown on the scoreboard.
Message 4 of 4
(540 Views)
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Fibre Broadband
- :
- Made the switch due to having problems with gaming...