Peering issue with Valve CSGO matchmaking servers ??

I have been playing competative matchmaking in CSGO (PC) for the past couple of weeks and the pings have been fine 20-50 on their servers. Now all of a sudden since yesterday the pings are 50-135 jumping constantly, Shows a solid 133 in game, and it is unplayable, like being on 56k again.

Is this a peering issue that has cropped up ? All my friends on other isps playing in the same game and server as me are getting normal low pings. Mine's just a solid 133-150. This has happened all of a sudden since yesterday.

Here is a screen shot.

http://img195.imageshack.us/img195/4659/btpeeringiss...

The servers are hosted in Luxembourg.

Here is a ping test to a Luxembourg IP address from me... Can people please tell me what they are getting ping wise to this address ?

195.46.252.19. Pt.lu resides at Entreprise des Postes et Telecommunications in Luxembourg.


Pinging 195.46.252.19. [195.46.252.19] with 32 bytes of data:
Reply from 195.46.252.19: bytes=32 time=118ms TTL=42
Reply from 195.46.252.19: bytes=32 time=118ms TTL=42
Reply from 195.46.252.19: bytes=32 time=111ms TTL=42
Reply from 195.46.252.19: bytes=32 time=142ms TTL=42
Reply from 195.46.252.19: bytes=32 time=119ms TTL=42




I ping everywhere else i can think of normally,

For instance


Pinging multiplay.co.uk [85.236.96.68] with 32 bytes of da
Reply from 85.236.96.68: bytes=32 time=15ms TTL=54
Reply from 85.236.96.68: bytes=32 time=16ms TTL=54
Reply from 85.236.96.68: bytes=32 time=16ms TTL=54
Reply from 85.236.96.68: bytes=32 time=15ms TTL=54

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

And...


Pinging multiplay.co.uk [85.236.96.68] with 32 bytes of da
Reply from 85.236.96.68: bytes=32 time=15ms TTL=54
Reply from 85.236.96.68: bytes=32 time=16ms TTL=54
Reply from 85.236.96.68: bytes=32 time=16ms TTL=54
Reply from 85.236.96.68: bytes=32 time=15ms TTL=54

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



Anyone else have the same problem ? OR does no one play csgo matchmaking on BT ?

Edited by DrDeath (Thu 20-Dec-12 22:53:19)

Pinging 195.46.252.19 with 32 bytes of data:
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42

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

In reply to a post by Chrysalis:

Pinging 195.46.252.19 with 32 bytes of data:
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42
Reply from 195.46.252.19: bytes=32 time=31ms TTL=42

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

Thanks for doing that.

This is really odd, I am on infinity just like you, but my ping times to lux are 130+, all other ips seems as normal nice and low.

How is it possible that we can take a different peering route there or something even though we are with he same ISP ?

As i said this has only happened since yesterday.


Here is a tracert to same address... Do you mind doing one too ? Thanks so much for your time!

Tracing route to www.pt.lu [195.46.252.19]
over a maximum of 30 hops:

1 46 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 8 ms 7 ms 7 ms 217.32.141.33
3 36 ms 12 ms 100 ms 217.32.141.62
4 10 ms 11 ms 21 ms 213.120.161.114
5 11 ms 10 ms 11 ms 31.55.164.249
6 11 ms 11 ms 11 ms 31.55.164.109
7 10 ms 10 ms 10 ms acc2-10GigE-0-0-0-5.bm.21cn-ipp.bt.net [10
248.202]
8 18 ms 15 ms 15 ms core2-te0-3-0-2.ealing.ukcore.bt.net [109.
8.148]
9 14 ms 14 ms 15 ms core2-pos5-0-0.telehouse.ukcore.bt.net [19
5.126]
10 120 ms 52 ms 211 ms t2as2-tge4-3.uk-lon1.eu.bt.net [166.49.214

11 15 ms 17 ms 48 ms 166-49-135-96.eu.bt.net [166.49.135.96]
12 14 ms 14 ms 15 ms 80.157.129.113
13 31 ms 31 ms 31 ms 194.25.6.82
14 30 ms 33 ms 35 ms 80.150.168.138
15 31 ms 30 ms 31 ms 213.135.251.239
16 31 ms 43 ms 53 ms 213.135.251.160
17 30 ms 30 ms 30 ms 213.166.61.126
18 110 ms 111 ms 111 ms www.pt.lu [195.46.252.19]
19 117 ms 116 ms 109 ms www.pt.lu [195.46.252.19]

Trace complete.

Appears to be ok for me.

Tracing route to www.pt.lu [195.46.252.19]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms BTHomeHub.home [192.168.1.2]
2 9 ms 9 ms 9 ms 217.32.141.4
3 9 ms 9 ms 9 ms 217.32.140.206
4 15 ms 15 ms 15 ms 217.41.216.154
5 14 ms 14 ms 14 ms 31.55.164.33
6 14 ms 14 ms 14 ms 31.55.164.107
7 14 ms 14 ms 15 ms acc1-10GigE-0-0-0-5.bm.21cn-ipp.bt.net [109.159.
248.74]
8 24 ms 22 ms 23 ms core2-te-0-13-0-4.ilford.ukcore.bt.net [109.159.
248.10]
9 19 ms 18 ms 18 ms core2-pos9-1.telehouse.ukcore.bt.net [194.74.65.
118]
10 19 ms 19 ms 19 ms t2as2-tge1-4.uk-lon1.eu.bt.net [166.49.214.129]

11 69 ms 20 ms 20 ms 166-49-135-96.eu.bt.net [166.49.135.96]
12 19 ms 19 ms 18 ms 80.157.129.113
13 39 ms 39 ms 38 ms f-ed6-i.F.DE.NET.DTAG.DE [62.156.131.246]
14 37 ms 37 ms 37 ms 80.150.168.138
15 38 ms 38 ms 37 ms 213.135.251.239
16 56 ms 34 ms 35 ms 213.135.251.160
17 34 ms 34 ms 34 ms 213.166.61.126
18 34 ms 34 ms 34 ms www.pt.lu [195.46.252.19]
19 34 ms 34 ms 34 ms www.pt.lu [195.46.252.19]

Trace complete.

As i try now, its normal again.

Seems like for me its bad at peak time and now its fine again.

I will see if it does the same thing tomorrow evening.

Odd that it seems to only be to Luxembourg i get bad pings at peak times... hmmm

Thank you very much for doing the tracerts and pings for me guys, ill update the thread tomorrow

In reply to a post by DrDeath:

Odd that it seems to only be to Luxembourg i get bad pings at peak times... hmmm

All the Amazon orders going out to their Luxemourg despatch depot and the day's despatch info coming back !

Edited by RobertoS (Fri 21-Dec-12 09:41:21)

More like it is going round the houses to avoid tax.

Well tonight it seems fine. Hopefully was just a temporary blip.