AnsweredAssumed Answered

Routing issues to Valve game servers

Question asked by juicebag on Sep 28, 2013
Latest reply on Sep 28, 2013 by [shaw]ali

One of the games I play is Counter Strike: Global Offensive, and as of late, I have noticed huge issues with the routing to most of the Valve supplied servers. A lot of these servers tend to be in Virginia, which I would normally ping around 80-90 to, being from southern Alberta.

 

As of late, I have noticed that my ping will be relatively low and stable, up until the point where there is any action going on in the game. At which point my ping will spike upwards of 200, making it virtually unplayable. I have done some traceroutes when ever this issue has presented its self. Here's the most recent:

 

 

 

Tracing route to 208.78.166.125 over a maximum of 30 hops


  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2     *        *        *     Request timed out.

  3    16 ms    13 ms    25 ms  64.59.131.241

  4    14 ms    15 ms    13 ms  rc2so.cg.shawcable.net [66.163.71.53]

  5    31 ms    31 ms    31 ms  66.163.75.226

  6    81 ms    88 ms    82 ms  66.163.78.58

  7    85 ms    78 ms    79 ms  rx0as-bellsouth.vx.shawcable.net [66.163.64.34]

  8    82 ms    79 ms    79 ms  208.78.167.3

  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     *        *        *     Request timed out.

19     *        *        *     Request timed out.

20     *        *        *     Request timed out.

21     *        *        *     Request timed out.

22     *        *        *     Request timed out.

23     *        *        *     Request timed out.

24     *        *        *     Request timed out.

25     *        *        *     Request timed out.

26     *        *        *     Request timed out.

27     *        *        *     Request timed out.

28     *        *        *     Request timed out.

29     *        *        *     Request timed out.

30     *        *        *     Request timed out.

 

Trace complete.

 

 

 

This is just the most recent one, often times the time out's are scattered throughout the entire trace, and not just at the end.

 

Any help on the issue would be greatly appreciated! Thanks

 

Outcomes