Results 1 to 4 of 4

Thread: Unplayable Packet Loss

  1. #1
    Basic Member
    Join Date
    Jul 2013
    Posts
    6

    Unplayable Packet Loss

    After reading quite a few threads here, as well as other places, about people with unplayable packet loss I felt the need to bring a lot of that information together into one place.

    Things that seem to be common among people with this issue:
    1. Problem starts after a new patch has been applied
    2. Problem is intermittent throughout the game, starting at around 2-3 minute mark and lasting until disconnect
    3. Most people who have this problem have stable, high-speed internet
    4. When ping tests and network stress tests are used, there are no issues with the client network or connection to anything except the steam DOTA2 server group (found here: http://bgp.he.net/AS32590#_prefixes)


    I have taken some screen caps of the problem in action on my steam profile here: (http://steamcommunity.com/profiles/7...4/screenshots/)

    You can notice through the net_graph that my average ping is 60-75 when the packet loss problem is not occurring. A ping test from where I am located (Florida) to California results in 0 packet loss (http://www.pingtest.net/result/83894461.png).

    The obvious thought is to tracert to steams servers and see where the problem is.

    When a tracert to an East Coast server (I am east coast) I receive this:

    C:\Users\ITS>tracert 208.78.165.70

    Tracing route to 208.78.165.70 over a maximum of 30 hops

    1 <1 ms <1 ms 19 ms launchmodem [192.168.1.254]
    2 8 ms 11 ms 6 ms adsl-74-178-50-1.gnv.bellsouth.net [74.178.50.1]

    3 14 ms 18 ms 11 ms 12.81.80.42
    4 10 ms 10 ms 15 ms 12.81.80.22
    5 14 ms 35 ms 13 ms 12.81.104.128
    6 26 ms 10 ms 10 ms 12.81.28.13
    7 12 ms 19 ms 16 ms 74.175.192.206
    8 17 ms 17 ms 301 ms cr2.ormfl.ip.att.net [12.122.106.70]
    9 261 ms 31 ms 16 ms cr81.fldfl.ip.att.net [12.122.1.46]
    10 28 ms 30 ms 14 ms fldfl01jt.ip.att.net [12.122.81.25]
    11 19 ms 19 ms 20 ms 192.205.36.170
    12 18 ms 19 ms 18 ms be-12-cr01.miami.fl.ibone.comcast.net [68.86.82.
    122]
    13 29 ms 32 ms 289 ms pos-0-13-0-0-cr01.56marietta.ga.ibone.comcast.ne
    t [68.86.89.25]
    14 67 ms 44 ms 46 ms he-0-4-0-0-cr01.ashburn.va.ibone.comcast.net [68
    .86.89.153]
    15 48 ms 44 ms 72 ms be-17-pe04.ashburn.va.ibone.comcast.net [68.86.8
    4.230]
    16 52 ms 41 ms 44 ms as32590.ashburn.va.ibone.comcast.net [173.167.56
    .170]
    17 63 ms 49 ms 50 ms 208.78.167.3
    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.


    However, when I go to tracert a West Coast Server. It resolves with no issues.

    C:\Users\ITS>tracert 192.69.97.62

    Tracing route to 192-69-97-62.valve.net [192.69.97.62]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms launchmodem [192.168.1.254]
    2 7 ms 7 ms 7 ms adsl-74-178-50-1.gnv.bellsouth.net [74.178.50.1]

    3 12 ms 10 ms 10 ms 12.81.80.42
    4 11 ms 32 ms 22 ms 12.81.80.22
    5 22 ms 28 ms 17 ms 12.81.105.48
    6 16 ms 14 ms 15 ms 12.81.28.13
    7 10 ms 22 ms 13 ms 74.175.192.14
    8 20 ms 24 ms 17 ms cr2.ormfl.ip.att.net [12.122.106.70]
    9 23 ms 20 ms 36 ms cr81.fldfl.ip.att.net [12.122.1.46]
    10 16 ms 23 ms 26 ms fldfl01jt.ip.att.net [12.122.81.25]
    11 20 ms 18 ms 27 ms 192.205.36.170
    12 24 ms 32 ms 18 ms be-13-cr01.miami.fl.ibone.comcast.net [68.86.82.
    126]
    13 62 ms 54 ms 63 ms pos-3-12-0-0-cr01.dallas.tx.ibone.comcast.net [6
    8.86.88.125]
    14 78 ms 87 ms 90 ms pos-2-8-0-0-cr01.denver.co.ibone.comcast.net [68
    .86.85.217]
    15 119 ms 97 ms 97 ms pos-0-9-0-0-cr01.seattle.wa.ibone.comcast.net [6
    8.86.88.66]
    16 95 ms 97 ms 97 ms be-15-pe03.seattle.wa.ibone.comcast.net [68.86.8
    3.6]
    17 * * * Request timed out.
    18 100 ms 174 ms 117 ms 192-69-99-225.valve.net [192.69.99.225]
    19 102 ms 101 ms 113 ms 192-69-99-243.valve.net [192.69.99.243]
    20 103 ms 135 ms 99 ms 192-69-97-62.valve.net [192.69.97.62]

    Trace complete.


    Thoughts? Opinions? I'm exhausted from testing this all night but I will be back later to update with more material I've found about people and packet loss.

  2. #2
    Basic Member
    Join Date
    Jul 2013
    Posts
    6
    Okay. Quick post here but after some testing I have fixed the issue. It seems that not only is this server based, but it is based on login information.

    I had previously been doing all my testing on my main account (Aeb Froman) but late last night I dropped out of a game due to this packet loss and was placed in low prio.

    So I decided to go back to testing this issue and wanted to see if matchmaking in different servers made a difference. So I logged into my other account and joined matchmaking. I experienced NO problems. I tried multiple servers with multiple options and none of them gave me the packet loss problem. I then created test lobbies and found that the issue was completely resolved.

    I then went back to my main account and created test lobbies (thinking that perhaps the issue had been solved while I was switching accounts) and the issue was back in full swing.


    If anyone else can test this and let me know if they have experienced the same thing that would be greatly appreciated. I have no clue why certain accounts would get the problem while others do not, especially considering they are coming from the same IP. But perhaps this is a credential or account based issue on valves end?
    Last edited by AebFroman; 07-19-2013 at 06:36 AM. Reason: words

  3. #3
    its possible. ill try it out and let u know. in the meanwhile can u tell me which dowload region (steam settings) are both of ur account set to.

  4. #4
    Basic Member
    Join Date
    Jul 2013
    Posts
    6
    Both are set to USE-Miami. I thought it could have been that as well so I changed them both to USE-Atlanta for a few days and had no change. Newest patch fixed this problem for me. I can now play on both accounts without packet loss.
    Last edited by AebFroman; 07-27-2013 at 11:49 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •