We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Page 1 of 3 1 2 3 LastLast
Results 1 to 25 of 51
  1. #1
    Join Date
    Apr 2007
    Posts
    473

    New ISP Routes in Place

    Hi all,

    So after some work between our team and our vendors we managed to get a secondary ISP circuit in place last Friday. This new circuit should be sending those of you who have been running into routing problems since the move onto a faster more direct circuit reducing packet loss and increasing the speed of your connection to our servers.

    We still have one more change to the other circuit to make so that we have two working at this upgraded capacity, but I would like to hear if you are seeing any improvements over the past weekend and also into this weekend so that we know if these efforts are making a difference.

    You can respond here or if you are in game, the /bug form has been updated to take more specific performance related data to help us in our investigations. Just choose Performance Issues/ Lag in the "Bug Category" and Lag or Performance in "Type of bug" to get the performance specific fields.

    Note: Please be aware this is just a fix for those who were seeing routing issues since the move so if seen it will be seen in general gameplay. Improvement work in PvMP regions and Minas Tirith and Pelennor fields are game code changes and will be in Update 18, which will be on Bullroarer again this weekend. If you would like to give feedback on those improvements, please do so in the Bullroarer forums. Neither this change nor, the work so far in Beta are our final efforts on the performance issues, we are still working on some other leads internally that we will push into the appropriate channel once they are proven out. We are listening to all of the feedback we are getting and continue to work on all the areas of concern in a multi-prong effort.

    Thank you,
    Vyvyanne

  2. #2
    Quote Originally Posted by Vyvyanne View Post
    Hi all,
    but I would like to hear if you are seeing any improvements over the past weekend and also into this weekend so that we know if these efforts are making a difference.
    Still the same 0.3-0.8% Loss
    No improvements for me.

  3. #3
    Join Date
    Jun 2011
    Posts
    2,583
    Glad to hear you're still working on lag issues, although it would be good to see some dev interaction on the Bullroarer forums with regard to content, as well as the positive interaction regarding lag.

  4. #4
    same

    Still the same 0.2-0.5% Loss
    ... No improvements for me.

    Wed 03/23/2016
    09:20 AM
    Tracing route to gls.lotro.com [198.252.160.30]
    over a maximum of 30 hops:
    0 [173.225.7.183]
    1 host-173-225-7-1.madisoncounty.net [173.225.7.1]
    2 10.1.10.1
    3 wsip-72-214-202-205.ks.ks.cox.net [72.214.202.205]
    4 100.122.224.136
    5 nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
    6 41.te4-1.tsr1.lga3.us.voxel.net [208.122.44.73]
    7 internap.lga5.us.voxel.net [173.231.161.70]
    8 border1.pc1-bbnet1.nyj001.pnap.net [216.52.95.9]
    9 turbine-14.border1.nyj001.pnap.net [70.42.39.234]
    10 * * *
    Computing statistics for 225 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

    1 5ms 0/ 100 = 0% 0/ 100 = 0% host-173-225-7-1.madisoncounty.net [173.225.7.1]
    0/ 100 = 0% |
    2 2ms 0/ 100 = 0% 0/ 100 = 0% 10.1.10.1
    0/ 100 = 0% |
    3 5ms 0/ 100 = 0% 0/ 100 = 0% wsip-72-214-202-205.ks.ks.cox.net [72.214.202.205]
    0/ 100 = 0% |
    4 5ms 0/ 100 = 0% 0/ 100 = 0% 100.122.224.136
    0/ 100 = 0% |
    5 --- 100/ 100 =100% 100/ 100 =100% nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
    0/ 100 = 0% |
    6 60ms 0/ 100 = 0% 0/ 100 = 0% 41.te4-1.tsr1.lga3.us.voxel.net [208.122.44.73]
    0/ 100 = 0% |
    7 52ms 0/ 100 = 0% 0/ 100 = 0% internap.lga5.us.voxel.net [173.231.161.70]
    0/ 100 = 0% |
    8 57ms 0/ 100 = 0% 0/ 100 = 0% border1.pc1-bbnet1.nyj001.pnap.net [216.52.95.9]
    0/ 100 = 0% |
    9 53ms 0/ 100 = 0% 0/ 100 = 0% turbine-14.border1.nyj001.pnap.net [70.42.39.234]

    Trace complete.
    Last edited by blindboy; Mar 23 2016 at 03:35 PM.

  5. #5
    Quote Originally Posted by Vyvyanne View Post
    Improvement work in PvMP ... are game code changes and will be in Update 18, which will be on Bullroarer again this weekend.
    A note of caution, I would not be saying this. What you have done is not improvement work in pvmp in the areas that matter and will only serve to antagonize the pvmp'ers, unfortunately.
    Phrasing! Doesn't anybody do phrasing anymore?

  6. #6
    Join Date
    Apr 2007
    Posts
    473
    For those of you that are still seeing loss, please when you have a chance do a /bug for performance and provide us the detail on your ISP route. This information is critical for us to be able to work with our vendors on correcting the issues that remain outstanding with the ISPs. Thank you!

  7. #7
    Quote Originally Posted by Vyvyanne View Post
    For those of you that are still seeing loss, please when you have a chance do a /bug for performance and provide us the detail on your ISP route. This information is critical for us to be able to work with our vendors on correcting the issues that remain outstanding with the ISPs. Thank you!
    Tracing route to gls.lotro.com [198.252.160.30]
    over a maximum of 30 hops:

    1. <1 ms <1 ms <1 ms 192.168.0.1
    2. 1 ms 1 ms 1 ms broadband-46-188-25-2.2com.net [46.188.25.2]
    3. 1 ms 1 ms 1 ms juni-vl-187-ecmp-m9.setel.ru [80.253.16.193]
    4. 1 ms 1 ms 1 ms 77.94.164.185
    5. 2 ms 1 ms 1 ms 6-1-5.bear1.Russia2.Level3.net [213.242.122.141]
    6. * * * Request timed out.
    7. * 141 ms * ae-2-3601.ear1.Washington12.Level3. net [4.69.148.45]
    8. 140 ms 140 ms 140 ms CenturyLink-Level3.Washington12.Level3.net [4.68.63.82]
    9. 136 ms 136 ms 135 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
    10. 136 ms 136 ms 136 ms 206.103.215.50
    11. 130 ms 130 ms 131 ms 63.236.3.130
    12. * * * Request timed out.
    13. 130 ms 130 ms 130 ms 198.252.160.30
    14. 130 ms 130 ms 130 ms 198.252.160.30

    Trace complete.

    It always timed out at:
    ae-2-3601.ear1.Washington12.Level3. net [4.69.148.45]
    CenturyLink-Level3.Washington12.Level3.net [4.68.63.82]
    198.252.160.30
    Last edited by Siddharta; Mar 23 2016 at 10:11 AM.

  8. #8

    traced

    Tracing route to 198.252.160.30 over a maximum of 30 hops


    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 8 ms 7 ms 7 ms 10.170.2.1
    3 8 ms 7 ms 11 ms gateway2-pc4-tv13blocal1.tv13.ptd.net [216.144.187.126]
    4 2690 ms 3164 ms 3227 ms 6-2-5.ear3.NewYork1.Level3.net [4.28.130.45]
    5 12 ms 11 ms 11 ms ae-1-51.edge3.NewYork2.Level3.net [4.69.138.196]


    6 11 ms 12 ms 12 ms ae-1-51.edge3.NewYork2.Level3.net [4.69.138.196]


    7 14 ms 14 ms 12 ms jfk-brdr-04.inet.qwest.net [63.146.26.5]
    8 154 ms 219 ms 202 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
    9 16 ms 14 ms 13 ms 206.103.215.50
    10 12 ms 11 ms 13 ms 63.236.3.130
    11 * * * Request timed out.
    12 28 ms 13 ms 12 ms 198.252.160.30
    13 12 ms 11 ms 13 ms 198.252.160.30


    Trace complete.

  9. #9
    Quote Originally Posted by Tom58 View Post
    Tracing route to 198.252.160.30 over a maximum of 30 hops


    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 8 ms 7 ms 7 ms 10.170.2.1
    3 8 ms 7 ms 11 ms gateway2-pc4-tv13blocal1.tv13.ptd.net [216.144.187.126]
    4 2690 ms 3164 ms 3227 ms 6-2-5.ear3.NewYork1.Level3.net [4.28.130.45]
    5 12 ms 11 ms 11 ms ae-1-51.edge3.NewYork2.Level3.net [4.69.138.196]


    6 11 ms 12 ms 12 ms ae-1-51.edge3.NewYork2.Level3.net [4.69.138.196]


    7 14 ms 14 ms 12 ms jfk-brdr-04.inet.qwest.net [63.146.26.5]
    8 154 ms 219 ms 202 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
    9 16 ms 14 ms 13 ms 206.103.215.50
    10 12 ms 11 ms 13 ms 63.236.3.130
    11 * * * Request timed out.
    12 28 ms 13 ms 12 ms 198.252.160.30
    13 12 ms 11 ms 13 ms 198.252.160.30


    Trace complete.
    144 ms is fine tracing from Brazil?

  10. #10
    Quote Originally Posted by Vyvyanne View Post
    For those of you that are still seeing loss, please when you have a chance do a /bug for performance and provide us the detail on your ISP route. This information is critical for us to be able to work with our vendors on correcting the issues that remain outstanding with the ISPs. Thank you!
    I'm still having the same issues, i opened a ticket as required and I hope that it will be answered.

  11. #11
    Join Date
    Jun 2010
    Posts
    6,835
    My ISP made some changes on their end that has affected my connection. This happened before you made your changes, though. From those changes, I've gotten consistent loss of 0.1% to 5%. I will see if today's changes make any difference.

    Today's trace route:
    Code:
      1     2 ms     1 ms     1 ms  my machine
      2     *        *        *     Request timed out. my gateway
      3    15 ms    14 ms    15 ms  dtr03mntval-tge-0-6-1-1.mntv.al.charter.com [96.34.75.101] my ISP
      4    15 ms    15 ms    26 ms  crr01ledsal-bue-101.leds.al.charter.com [96.34.79.196]
      5    21 ms    21 ms    21 ms  crr01sghlga-bue-200.sghl.ga.charter.com [96.34.78.18]
      6    29 ms    27 ms    24 ms  bbr01atlnga-bue-3.atln.ga.charter.com [96.34.2.70]
      7    25 ms    24 ms    26 ms  bbr02atlnga-bue-7.atln.ga.charter.com [96.34.0.25] my ISP's internet exchange to the backbone
      8    23 ms    24 ms    24 ms  be4074.ccr41.atl04.atlas.cogentco.com [38.122.46.69] my ISP's regular backbone, but it isn't as good as Telia's, which is the backup
      9    23 ms    24 ms    53 ms  be2848.ccr42.atl01.atlas.cogentco.com [154.54.6.117]
     10    36 ms    34 ms    34 ms  be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
     11    35 ms    37 ms    34 ms  be2657.ccr41.iad02.atlas.cogentco.com [154.54.31.110]
     12    45 ms    39 ms    49 ms  qwest.iad02.atlas.cogentco.com [154.54.11.130] Cogent's internet exchange with Qwest and is much less efficient than Telia (more hops)
     13    39 ms    53 ms    41 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2] Qwest's hand off to the internet exchange connecting the NJ data center
     14    61 ms    51 ms    54 ms  206.103.215.50
     15    46 ms    47 ms    46 ms  63.236.3.130
     16     *        *        *     Request timed out.
     17    43 ms    44 ms    53 ms  198.252.160.30
     18    42 ms    41 ms    43 ms  198.252.160.30
    Okay, the update that I have shows little change over the past week. When pathping quit working, I found Win MTR and here are a couple of samples from that program.
    Code:
    |---------------------------------------------------------------------------------------------|
    |                                       WinMTR statistics                                     |
    |                        Host                -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
    |---------------------------------------------------|------|------|------|------|------|------|
    |                                192.168.1.1 -    0 |   55 |   55 |    1 |    1 |    4 |    2 |
    |                      No response from host -  100 |   11 |    0 |    0 |    0 |    0 |    0 |
    |dtr03mntval-tge-0-6-1-1.mntv.al.charter.com -    0 |   55 |   55 |   10 |   18 |   47 |   27 |
    |    crr01ledsal-bue-101.leds.al.charter.com -    0 |   55 |   55 |   12 |   18 |   44 |   26 |
    |    crr01sghlga-bue-200.sghl.ga.charter.com -    0 |   55 |   55 |   20 |   27 |   54 |   21 |
    |      bbr01atlnga-bue-3.atln.ga.charter.com -    0 |   55 |   55 |   21 |   32 |   63 |   35 |
    |      bbr02atlnga-bue-7.atln.ga.charter.com -    0 |   55 |   55 |   22 |   32 |   58 |   30 |
    |      be4074.ccr41.atl04.atlas.cogentco.com -    0 |   55 |   55 |   22 |   29 |   55 |   23 |
    |      be2848.ccr42.atl01.atlas.cogentco.com -    0 |   55 |   55 |   22 |   28 |   55 |   34 |
    |      be2113.ccr42.dca01.atlas.cogentco.com -    0 |   55 |   55 |   33 |   41 |   64 |   37 |
    |      be2657.ccr41.iad02.atlas.cogentco.com -    0 |   55 |   55 |   32 |   41 |   68 |   40 |
    |             qwest.iad02.atlas.cogentco.com -    7 |   43 |   40 |   36 |   47 |   90 |   38 |
    |                 ewr-cntr-11.inet.qwest.net -   11 |   39 |   35 |   41 |   46 |   62 |   46 |
    |                             206.103.215.50 -   11 |   39 |   35 |   40 |   57 |  174 |   45 |
    |                               63.236.3.130 -   15 |   34 |   29 |   40 |   47 |   82 |   41 |
    |                      No response from host -  100 |   11 |    0 |    0 |    0 |    0 |    0 |
    |                             198.252.160.30 -   20 |   31 |   25 |    0 |   49 |   69 |   45 |
    |___________________________________________________|______|______|______|______|______|______|
       WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
    
    |---------------------------------------------------------------------------------------------|
    |                                       WinMTR statistics                                     |
    |                        Host                -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
    |---------------------------------------------------|------|------|------|------|------|------|
    |                                192.168.1.1 -    0 |  107 |  107 |    1 |    2 |   17 |    2 |
    |                      No response from host -  100 |   22 |    0 |    0 |    0 |    0 |    0 |
    |dtr03mntval-tge-0-6-1-1.mntv.al.charter.com -    0 |  107 |  107 |   12 |   19 |   49 |   19 |
    |    crr01ledsal-bue-101.leds.al.charter.com -    0 |  107 |  107 |   12 |   19 |   45 |   17 |
    |    crr01sghlga-bue-200.sghl.ga.charter.com -    0 |  107 |  107 |   19 |   27 |   53 |   23 |
    |      bbr01atlnga-bue-3.atln.ga.charter.com -    0 |  107 |  107 |   22 |   33 |   53 |   29 |
    |      bbr02atlnga-bue-7.atln.ga.charter.com -    0 |  107 |  107 |   23 |   32 |   63 |   28 |
    |      be4074.ccr41.atl04.atlas.cogentco.com -    0 |  107 |  107 |   22 |   31 |   63 |   27 |
    |      be2848.ccr42.atl01.atlas.cogentco.com -    0 |  107 |  107 |   22 |   29 |   63 |   27 |
    |      be2113.ccr42.dca01.atlas.cogentco.com -    0 |  107 |  107 |   32 |   41 |   68 |   38 |
    |      be2657.ccr41.iad02.atlas.cogentco.com -    0 |  107 |  107 |   32 |   41 |   67 |   33 |
    |             qwest.iad02.atlas.cogentco.com -    4 |   96 |   93 |   35 |   46 |   75 |   46 |
    |                 ewr-cntr-11.inet.qwest.net -    8 |   84 |   78 |   39 |   51 |  182 |   46 |
    |                             206.103.215.50 -    9 |   80 |   73 |   40 |   53 |  208 |   46 |
    |                               63.236.3.130 -    4 |   96 |   93 |   43 |   50 |   71 |   47 |
    |                      No response from host -  100 |   22 |    0 |    0 |    0 |    0 |    0 |
    |                             198.252.160.30 -    8 |   84 |   78 |   41 |   50 |   83 |   41 |
    |___________________________________________________|______|______|______|______|______|______|
       WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
    Last edited by cdq1958; Mar 28 2016 at 10:58 AM. Reason: update
    "No sadder words of tongue or pen are the words: 'Might have been'." -- John Greenleaf Whittier
    "Do or do not. There is no try." -- Yoda
    On planet Earth, there is a try.
    Indeed, in a world and life full of change, the only constant is human nature (A is A, after all :P).
    We old vets need to keep in mind those who come after us.

  12. #12
    from 0.8% to 5.0% Loss at times (especially in the moors)...

    Code:
    Rastreando a rota para gls.lotro.com [198.252.160.30]
    com no máximo 30 saltos:
    
      1     7 ms     3 ms     3 ms  192.168.0.1
      2    39 ms    21 ms    33 ms  b3d2c001.virtua.com.br [179.210.192.1]
      3    24 ms    19 ms    16 ms  c91120c2.virtua.com.br [201.17.32.194]
      4    45 ms    24 ms    16 ms  c911229d.virtua.com.br [201.17.34.157]
      5    29 ms    22 ms    22 ms  c9110007.virtua.com.br [201.17.0.7]
      6    16 ms    22 ms    37 ms  embratel-T0-2-0-0-uacc03.rjoen.embratel.net.br [201.30.79.9]
      7   137 ms    22 ms   153 ms  200.244.216.2
      8   132 ms   129 ms   141 ms  ebt-BP1224-intl04.mianap.embratel.net.br [200.230.251.130]
      9   142 ms   138 ms   138 ms  ae52.edge1.Miami2.Level3.net [4.59.240.117]
     10   154 ms     *      135 ms  ae-1-51.edge2.Miami2.Level3.net [4.69.138.77]
     11   139 ms   145 ms   136 ms  ae-1-51.edge2.Miami2.Level3.net [4.69.138.77]
     12   142 ms   135 ms   135 ms  nap-brdr-01.inet.qwest.net [63.146.26.137]
     13   156 ms   144 ms   173 ms  ewr-cntr-11.inet.qwest.net [205.171.17.2]
     14   139 ms   140 ms   139 ms  206.103.215.50
     15   157 ms   149 ms   155 ms  63.236.3.130
     16     *        *        *     Esgotado o tempo limite do pedido.
     17   132 ms   134 ms   133 ms  198.252.160.30
     18   136 ms   133 ms   133 ms  198.252.160.30

  13. #13
    I'm still crashing in MT. Also crash when travelling to Bree from MT.

  14. #14
    Join Date
    Oct 2012
    Posts
    3,057
    Quote Originally Posted by Vyvyanne View Post
    Hi all,

    You can respond here or if you are in game, the /bug form has been updated to take more specific performance related data to help us in our investigations. Just choose Performance Issues/ Lag in the "Bug Category" and Lag or Performance in "Type of bug" to get the performance specific fields.

    Thank you,
    Vyvyanne
    Since the data centre move I've been seeing packet loss every evening UK time. During the day, it's fine, very rarely see any. So I thought I'd give using the new bug report a go this evening and, having found the correct fields on the bug form, followed the instructions to go to the support site and then did the pathping thing as described. Not sure it's working.

    This is a Tracert

    Tracing route to gls.lotro.com [198.252.160.30]
    over a maximum of 30 hops:

    1 40 ms 78 ms 90 ms cpc64768-burn7-2-0-gw.10-1.cable.virginm.net [82.22.182.1]
    2 8 ms 9 ms 9 ms manc-core-2b-ae3-2092.network.virginmedia.net [82.8.210.157]
    3 * * * Request timed out.
    4 * * * Request timed out.
    5 11 ms 11 ms 15 ms nrth-bb-1b-ae1-0.network.virginmedia.net [62.254.42.218]
    6 16 ms 16 ms 15 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
    7 * * * Request timed out.
    8 89 ms 85 ms 88 ms 84.116.140.174
    9 88 ms 85 ms 87 ms us-nyc01b-ri2-et-4-1-0-0.aorta.net [84.116.135.114]
    10 87 ms 88 ms 86 ms 63-235-40-165.dia.static.qwest.net [63.235.40.165]
    11 91 ms 90 ms 89 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
    12 87 ms 89 ms 87 ms 206.103.215.50
    13 86 ms 84 ms 82 ms 63.236.3.130
    14 * * * Request timed out.
    15 86 ms 95 ms 90 ms 198.252.160.30
    16 89 ms 89 ms 87 ms 198.252.160.30

    And this is what Pathping gives

    Tracing route to gls.lotro.com [198.252.160.30]
    over a maximum of 30 hops:
    0 removed 'cos it's my computer
    1 cpc64768-burn7-2-0-gw.10-1.cable.virginm.net [82.22.182.1]
    2 manc-core-2b-ae3-2092.network.virginmedia.net [82.8.210.157]
    3 * * *
    Computing statistics for 50 seconds...
    Source to Here This Node/Link
    Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
    0 Me again
    0/ 100 = 0% |
    1 27ms 0/ 100 = 0% 0/ 100 = 0% cpc64768-burn7-2-0-gw.10-1.cable.virginm.net [82.22.182.1]
    0/ 100 = 0% |
    2 8ms 0/ 100 = 0% 0/ 100 = 0% manc-core-2b-ae3-2092.network.virginmedia.net [82.8.210.157]

    Doesn't really get very far or tell us much about what's going on, I feel.

  15. #15
    it was good until today, my game started to crash every 1 min and i can't play anymore.
    Creeps:
    Deathlyheals - R14 defiler | Deadlyline - R10 Warg
    Freeps - FullyWrecked
    #BringT2cBack

  16. #16
    Join Date
    Apr 2011
    Posts
    5,982
    Haven't gotten in game, but I'm not sure if I was having routing problems anyway.

    I did want to ask, though, since you mention it... when is BR opening again? I'm not sure how many companies observe Good Friday, but I was wondering if Turbine does and if that means BR will be opened a day early.
    R5 105 GRD Marevayave - Leader of Riddermarked For Death
    R8 115 MNS Fayah/115 LM Siennah/115 HNT Dinenol/115 RK Dhurik
    115 CHN Alachas/85 CPT Dinfaerien/61 BUR Dhax/115 WDN Godoric
    R9 115 MNS Fayeh (alt Wilya) - Lonely Mountain Band @ Landroval

  17. #17
    Join Date
    Jun 2011
    Posts
    1,773
    Quote Originally Posted by Vyvyanne View Post
    the /bug form has been updated
    I was putting in a /bug report on a non performance issue (a light damage legacy not buffing light damage on guard belt) but as I hit send the window just hung so I'm not sure it was sent and perhaps other /bugs reports aren't getting through with this recent code change.

    Mac


    Update: I got the email acknowledging the /bug report just doesn't exit the form nicely.
    Last edited by Macdui; Mar 23 2016 at 08:54 PM.

  18. #18
    As I see most of the people posting tracert results are, I am also having a time out in the exact same place:

    10 47 ms 44 ms 43 ms 63.236.3.130
    11 * * * Request timed out.
    12 45 ms 44 ms 43 ms 198.252.160.30
    Lord of the Rings Online (Since Alpha F&F)
    Every class at 120
    Asheron's Call (1999-2017) - Ling Mei

  19. #19
    From Chicago:


    Tracing route to 198.252.160.30 over a maximum of 30 hops

    1 <1 ms <1 ms 1 ms 192.168.1.1
    2 2 ms 1 ms 1 ms 192.168.0.1
    3 12 ms 10 ms 12 ms d53-64-1-136.nap.wideopenwest.com [64.53.136.1]
    4 15 ms 17 ms 10 ms dynamic-76-73-171-57.knology.net [76.73.171.57]
    5 13 ms 11 ms 13 ms 76-73-164-105.knology.net [76.73.164.105]
    6 25 ms 11 ms 12 ms 76-73-164-65.knology.net [76.73.164.65]
    7 14 ms 11 ms 13 ms static-76-73-191-224.knology.net [76.73.191.224]
    8 13 ms 13 ms 16 ms dynamic-75-76-35-10.knology.net [75.76.35.10]
    9 12 ms 11 ms 11 ms dynamic-75-76-35-6.knology.net [75.76.35.6]
    10 17 ms 11 ms 13 ms xe-7-2-0.edge4.Chicago3.Level3.net [4.53.98.41]
    11 12 ms 12 ms 15 ms chp-brdr-03.inet.qwest.net [63.146.27.17]
    12 709 ms 33 ms 32 ms ewr-cntr-11.inet.qwest.net [205.171.17.2]
    13 34 ms 32 ms 33 ms 206.103.215.50
    14 34 ms 40 ms 32 ms 63.236.3.130
    15 * * * Request timed out.
    16 57 ms 33 ms 35 ms 198.252.160.30
    17 36 ms 33 ms 33 ms 198.252.160.30

    Trace complete.

  20. #20
    I'm wondering about this lag problem (skill lag, loot opening delays, rubberbanding, etc).

    While doing PvE quests, I'm seeing this lag only on Eastern Gondor (Lossarnach, Pelennor, MT) while all the other areas, especially pre-Rohan are totally fine. If the lag problem is due ISP routing, why don't we see issues in other areas? We are still logged to same server, session is the same and even the time is more or less the same. Yet again, lagging starts only when you enter this problematic area.

    Same thing for the crashes, btw. I spent quite some time in older areas working on various deeds and didn't see a single crash. When coming back to MT I got crash in 30 min.

  21. #21
    Join Date
    Aug 2011
    Posts
    59
    Quote Originally Posted by Vyvyanne View Post
    For those of you that are still seeing loss, please when you have a chance do a /bug for performance and provide us the detail on your ISP route. This information is critical for us to be able to work with our vendors on correcting the issues that remain outstanding with the ISPs. Thank you!
    I only had routing issues from time to time not regularly in the last couple of weeks I did an traclet anyway.
    Here is the result (I'm from Europe):

    Routenverfolgung zu gls.lotro.com [198.252.160.30]
    über maximal 30 Hops:

    1 1 ms 1 ms <1 ms 10.0.0.138
    2 * * * Zeitüberschreitung der Anforderung.
    3 18 ms 37 ms 18 ms 195.3.77.13
    4 227 ms 305 ms 208 ms 195.3.118.149
    5 31 ms 31 ms 31 ms lg2-1171.as8447.a1.net [195.3.64.6]
    6 47 ms 31 ms 31 ms xe-1-2-0.mpr1.fra4.de.above.net [80.81.194.26]
    7 108 ms 108 ms 109 ms ae27.cs1.fra9.de.eth.zayo.com [64.125.30.254]
    8 108 ms 108 ms 109 ms ae0.cs1.fra6.de.eth.zayo.com [64.125.29.54]
    9 108 ms 108 ms 108 ms ae2.cs1.ams17.nl.eth.zayo.com [64.125.29.59]
    10 108 ms 108 ms 109 ms ae0.cs1.ams10.nl.eth.zayo.com [64.125.29.80]
    11 108 ms 113 ms 155 ms ae6.cs2.lga5.us.eth.zayo.com [64.125.29.77]
    12 108 ms 109 ms 108 ms ae27.cr2.lga5.us.zip.zayo.com [64.125.30.253]
    13 109 ms 109 ms 108 ms ae1.cr1.lga5.us.zip.zayo.com [64.125.29.37]
    14 109 ms 108 ms 109 ms ae11.mpr3.lga7.us.zip.zayo.com [64.125.20.14]
    15 109 ms 109 ms 109 ms 128.177.168.190.IPYX-072053-ZYO.zip.zayo.com [128.177.168.190]
    16 110 ms 108 ms 108 ms border1.pc2-bbnet2.nyj001.pnap.net [216.52.95.73]
    17 109 ms 109 ms 109 ms turbine-14.border1.nyj001.pnap.net [70.42.39.234]
    18 * * * Zeitüberschreitung der Anforderung.
    19 110 ms 110 ms 109 ms 198.252.160.30
    20 110 ms 109 ms 110 ms 198.252.160.30

    Ablaufverfolgung beendet.

  22. #22
    Join Date
    Apr 2007
    Posts
    473
    Quote Originally Posted by Forodir View Post
    I'm wondering about this lag problem (skill lag, loot opening delays, rubberbanding, etc).

    While doing PvE quests, I'm seeing this lag only on Eastern Gondor (Lossarnach, Pelennor, MT) while all the other areas, especially pre-Rohan are totally fine. If the lag problem is due ISP routing, why don't we see issues in other areas? We are still logged to same server, session is the same and even the time is more or less the same. Yet again, lagging starts only when you enter this problematic area.

    Same thing for the crashes, btw. I spent quite some time in older areas working on various deeds and didn't see a single crash. When coming back to MT I got crash in 30 min.
    What you are describing is not due to the ISP issues others in this thread are seeing. What you are describing is the client memory size issue that was particularly noticed with the release of the new regions in Update 17 (MT and Pelennor in particular). Reducing the memory load of those regions will take a client update which we are working on in Update 18 to reduce the general memory requirements of those regions as well as the new regions in Update 18.

  23. #23
    Quote Originally Posted by Vyvyanne View Post
    What you are describing is not due to the ISP issues others in this thread are seeing. What you are describing is the client memory size issue that was particularly noticed with the release of the new regions in Update 17 (MT and Pelennor in particular). Reducing the memory load of those regions will take a client update which we are working on in Update 18 to reduce the general memory requirements of those regions as well as the new regions in Update 18.
    Thanks for the update Vyvyanne.

    I thought there was some relation since when creating a bug report of lag issues, I was asked to report those network statistics along with the bug report (which I did). For the memory issue, is there a problem where the client cannot utilize all the system memory available? Or do we hit limitations of 32-bit client? Having a high tech system with plenty of system memory doesn't seem to help here.

  24. #24
    Join Date
    Jun 2010
    Posts
    6,835
    Quote Originally Posted by Anjuli View Post
    As I see most of the people posting tracert results are, I am also having a time out in the exact same place:

    10 47 ms 44 ms 43 ms 63.236.3.130
    11 * * * Request timed out.
    12 45 ms 44 ms 43 ms 198.252.160.30
    Since routers can be set to drop ICMP, that hop isn't a problem. When you get that timed out at a hop and all subsequent ones, then that hop is possibly a problem. Nevertheless, one must be cautious when analyzing a traceroute and try to get other concurrent data that uses a different internet protocol to confirm the existence of a problem. What that trace is saying is that the last router is responding to ICMP with a 44 millisecond round trip time, on average.

    That's another thing. One should always expect jitter given that equipment failure and load balancing rules make the route packets take vary. The internet is a packet switched, store and forward communication network. Dropped packets make the two hosts exchange messages that get the dropped packets resent if the data integrity requires it. That is a cause of lag.
    "No sadder words of tongue or pen are the words: 'Might have been'." -- John Greenleaf Whittier
    "Do or do not. There is no try." -- Yoda
    On planet Earth, there is a try.
    Indeed, in a world and life full of change, the only constant is human nature (A is A, after all :P).
    We old vets need to keep in mind those who come after us.

  25. #25
    1 1 ms <1 ¬? <1 ¬? KEENETIC_GIGA [192.168.1.1]
    2 1 ms 2 ms 1 ms 213.219.200.227
    3 3 ms 1 ms 1 ms 213.219.200.225
    4 2 ms 1 ms 1 ms ae3.mbr1.msk1.ip.di-net.ru [213.248.3.70]
    5 2 ms 1 ms 1 ms m9-cr03-ae9.993.msk.stream-internet.net [212.188.44.169]
    6 5 ms 2 ms 3 ms m9-cr04-be13.77.msk.stream-internet.net [212.188.42.105]
    7 10 ms 9 ms 9 ms bor-cr03-be2.78.spb.stream-internet.net [212.188.28.113]
    8 45 ms 38 ms 40 ms anc-cr01-be1.78.ff.stream-internet.net [212.188.29.93]
    9 45 ms 44 ms 44 ms ffm-b7-link.telia.net [213.248.104.253]
    10 42 ms 40 ms 40 ms ffm-bb2-link.telia.net [80.91.249.106]
    11 127 ms 197 ms 128 ms nyk-bb2-link.telia.net [62.115.139.15]
    12 129 ms 130 ms 129 ms nyk-b5-link.telia.net [213.155.131.139]
    13 130 ms 128 ms 128 ms internap-ic-305784-nyk-b5.c.telia.net [213.248.66.102]
    14 128 ms 127 ms 128 ms border1.pc2-bbnet2.nyj001.pnap.net [216.52.95.73]
    15 130 ms 128 ms 127 ms turbine-14.border1.nyj001.pnap.net [70.42.39.234]
    16 * * * Request timed out.
    17 133 ms 129 ms 137 ms 198.252.160.30
    18 134 ms 129 ms 129 ms 198.252.160.30

 

 
Page 1 of 3 1 2 3 LastLast

Posting Permissions

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

This form's session has expired. You need to reload the page.

Reload