[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until services are transferred. Our Service Moving Info page is now live here: https://bit.ly/tera_service_moving

FYI: Network Routing Experiment in Progress

2

Comments

  • My ping is now at 400-500ms. I did the tracert, and its giving me the 'request timed out' all the way.
    That's strange.. Because i can still log into the game and do the ghillie..
    Is it weird if i say that the chat is also laggy? I could write something, press enter, do one brawler's rotation and only then the message would appear in the chat.

    :dizzy:
  • JerichowJerichow ✭✭✭✭
    Back down to my normal ~40ms ping vs the 100-200ms for the last couple weeks. Sad to see there isn't a 'middle ground' option that puts most people ~60-80ms ping so nobody gets shafted too hard.

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 14 ms 14 ms 17 ms 96.120.116.141
    3 7 ms 6 ms 7 ms 68.85.200.165
    4 8 ms 7 ms 7 ms 68.86.233.58
    5 10 ms 11 ms 10 ms 68.86.233.93
    6 20 ms 20 ms 23 ms 68.86.94.81
    7 34 ms 28 ms 24 ms 68.86.83.50
    8 38 ms 39 ms 40 ms 216.207.8.189
    9 39 ms 38 ms 39 ms 205.171.93.70
    10 39 ms 39 ms 39 ms 216.33.94.118
    11 41 ms 40 ms 41 ms 64.37.205.6
    12 40 ms 39 ms 39 ms 208.67.48.14
    13 41 ms 40 ms 39 ms 208.67.48.14
    14 39 ms 40 ms 40 ms 208.67.49.36
  • Jerichow wrote: »
    Back down to my normal ~40ms ping vs the 100-200ms for the last couple weeks. Sad to see there isn't a 'middle ground' option that puts most people ~60-80ms ping so nobody gets shafted too hard.

    There is a better answer.. move tera to a better data center :smile:
  • My ping, has always been a stable 40...now suddenly it's shooting up to 2000 MS, I mean even when I play on EU I get 120 MS....2000 MS....It was so bad that my game completely crashed when trying to use my mount.
  • Oh god, I'm actually getting ping back to 60-90 like it was during CBT /OBT paid to play days. Ever since then until now, average about 100-140 ping. I now have a reason to come back and yolo IMS que again. West Coast.
  • edited November 2018
    DHEE5KW5FP wrote: »
    My ping, has always been a stable 40...now suddenly it's shooting up to 2000 MS, I mean even when I play on EU I get 120 MS....2000 MS....It was so bad that my game completely crashed when trying to use my mount.

    Assuming it's still happening, could you post your traceroute as noted in the OP as well, just to get a sense of where the problem is?

    My ping is now at 400-500ms. I did the tracert, and its giving me the 'request timed out' all the way.
    That's strange.. Because i can still log into the game and do the ghillie..
    Is it weird if i say that the chat is also laggy? I could write something, press enter, do one brawler's rotation and only then the message would appear in the chat.

    :dizzy:

    It's consistent with the problem you noted anyway. If you can't even ping to the first hop, it may be a broader issue. I was speaking to someone the other day who was having nearly 500ms on all hops after their own LAN, so it was definitely a bigger problem in that case. You can also try pinging diag.enmasse.com to see what that shows.
  • It's consistent with the problem you noted anyway. If you can't even ping to the first hop, it may be a broader issue. I was speaking to someone the other day who was having nearly 500ms on all hops after their own LAN, so it was definitely a bigger problem in that case. You can also try pinging diag.enmasse.com to see what that shows.

    9 | chp-brdr-03.inet.qwest.net[67.14.8.194] | 248 ms
    10 | hr3-et-1-1-0.ch3.savvis.net[216.33.94.118] | 249 ms
    11 | N/A | Request Timed Out
    12 | N/A | Request Timed Out
    13 | N/A | Request Timed Out
    14 | 208.67.49.36 | 249 ms

    I did the ping, this the highest i got. Not anywhere near 500ms.
    Then again, 150-250ms is still playable to me.
    It cant be graphic or fps, because before this, all works well. Even before and after the new ui came out.
    And what's really bothering me is that, i never had problem with savvis before this. I'm pretty sure i'm also among those who complained about zayo... Could it possible that turning off zayo may or may not created a bottleneck of some sort?
    :sweat:

  • Tracing route to diag.enmasse.com [208.67.49.36]
    over a maximum of 30 hops:

    1 4 ms 2 ms 2 ms 192.168.1.254
    2 68 ms 39 ms 36 ms 99.163.244.1
    3 30 ms 38 ms 25 ms 71.152.214.57
    4 * * * Request timed out.
    5 39 ms 33 ms 46 ms 12.83.79.41
    6 58 ms 99 ms 60 ms 12.122.132.197
    7 34 ms 34 ms 50 ms 63.146.26.217
    8 38 ms 32 ms 30 ms 216.33.94.118
    9 30 ms 70 ms 138 ms 64.37.205.6
    10 129 ms 53 ms 57 ms 208.67.48.14
    11 34 ms 35 ms 48 ms 208.67.48.14
    12 30 ms 29 ms 51 ms 208.67.49.36


    From Indianapolis Indiana.
  • edited November 2018
    DHEE5KW5FP wrote: »
    From Indianapolis Indiana.
    In your case, I really question why the second hop is so high -- that should be right in your neighbourhood, unless you're using a VPN or something. The fact that the second hop is just as high as the final hop is odd.

    Could it possible that turning off zayo may or may not created a bottleneck of some sort?
    Probably not, but it's still weird that your in-game display is that much higher than the traceroute. (It's normal for it to be a bit higher but not double.) Are you playing with a gaming VPN or anything? It could be something like that is making it worse, and only impacting the game and not showing up on a regular trace.

    You can also try traceroute to the two servers 208.67.49.50 and 208.67.49.51 but not you won't be able to go all the way to the end (it'll timeout at the last hops because of ping being firewall blocked).
  • DHEE5KW5FP wrote: »
    From Indianapolis Indiana.
    In your case, I really question why the second hop is so high -- that should be right in your neighbourhood, unless you're using a VPN or something. The fact that the second hop is just as high as the final hop is odd.

    Could it possible that turning off zayo may or may not created a bottleneck of some sort?
    Probably not, but it's still weird that your in-game display is that much higher than the traceroute. (It's normal for it to be a bit higher but not double.) Are you playing with a gaming VPN or anything? It could be something like that is making it worse, and only impacting the game and not showing up on a regular trace.

    You can also try traceroute to the two servers 208.67.49.50 and 208.67.49.51 but not you won't be able to go all the way to the end (it'll timeout at the last hops because of ping being firewall blocked).

    Yeah I don't know why it's being a Psycho I don't use a VPN or anything never had a need for them. Everything was working fine until I decided to do my black friday Tera shopping LOL. I've always been stable at 40 MS So I have no idea what is going on.
  • Idk about anyone one else but my ping has been worse lately. I usually run with 50-90 ping but it’s been on a constant 130+ which is killing me cause not used to this delay in skills. Smh
  • TrialMacameauTrialMacameau Does it matter ? cuz DDOSing is a crime punishable of Prison ✭✭✭
    edited November 2018
    Tracing route to diag.enmasse.com [208.67.49.36]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms TrialMacameau.TrialMacameau [142.217.80.1]
    2 32 ms 10 ms 9 ms 142-217-64-1.telebecinternet.net [142.217.64.1]
    3 8 ms 8 ms 8 ms 207-164-139-34.telebecinternet.net [207.164.139.34]
    4 16 ms 16 ms 16 ms 207.35.49.197
    5 22 ms 23 ms 25 ms tcore4-montreal02_1-14-0-0.net.bell.ca [64.230.91.20]
    6 17 ms 16 ms 18 ms bx1-montreal02_hundredgige0-2-0-0.net.bell.ca [64.230.91.125]
    7 16 ms 16 ms 16 ms ix-ae-10-0.tcore1.w6c-montreal.as6453.net [66.198.96.9]
    8 24 ms 24 ms 24 ms if-ae-12-2.tcore1.mtt-montreal.as6453.net [64.86.31.26]
    9 29 ms 24 ms 25 ms if-ae-0-2.tcore2.mtt-montreal.as6453.net [216.6.115.90]
    10 24 ms 24 ms 24 ms if-ae-5-2.tcore2.n0v-new-york.as6453.net [64.86.226.58]
    11 23 ms 24 ms 24 ms if-ae-2-2.tcore1.n0v-new-york.as6453.net [216.6.90.21]
    12 24 ms 23 ms 23 ms jfk-brdr-04.inet.qwest.net [63.235.41.97]
    14 41 ms 42 ms 41 ms hr3-et-1-1-0.ch3.savvis.net [216.33.94.118]
    15 41 ms 40 ms 40 ms 64.37.205.6
    16 50 ms 49 ms 49 ms 208.67.48.14
    17 41 ms 41 ms 49 ms 208.67.48.14
    18 91 ms 41 ms 41 ms 208.67.49.36

    Trace complete.

    Tracing route to 208.67.49.50 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms TrialMacameau.TrialMacameau [142.217.80.1]
    2 9 ms 8 ms 8 ms 142-217-64-1.telebecinternet.net [142.217.64.1]
    3 9 ms 8 ms 8 ms 207-164-139-34.telebecinternet.net [207.164.139.34]
    4 16 ms 15 ms 16 ms 207.35.49.197
    5 18 ms 18 ms 18 ms tcore4-montreal02_1-14-0-0.net.bell.ca [64.230.91.20]
    6 16 ms 16 ms 16 ms bx1-montreal02_hundredgige0-2-0-0.net.bell.ca [64.230.91.125]
    7 17 ms 17 ms 17 ms ix-ae-10-0.tcore1.w6c-montreal.as6453.net [66.198.96.9]
    8 30 ms 33 ms 32 ms if-ae-12-2.tcore1.mtt-montreal.as6453.net [64.86.31.26]
    9 25 ms 26 ms 27 ms if-ae-0-2.tcore2.mtt-montreal.as6453.net [216.6.115.90]
    10 24 ms 24 ms 24 ms if-ae-5-2.tcore2.n0v-new-york.as6453.net [64.86.226.58]
    11 24 ms 23 ms 23 ms if-ae-2-2.tcore1.n0v-new-york.as6453.net [216.6.90.21]
    12 24 ms 24 ms 23 ms jfk-brdr-04.inet.qwest.net [63.235.41.97]
    14 41 ms 42 ms 47 ms hr3-et-1-1-0.ch3.savvis.net [216.33.94.118]
    15 40 ms 40 ms 112 ms 64.37.205.6

    Trace complete.

    Tracing route to 208.67.49.51 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms TrialMacameau.TrialMacameau [142.217.80.1]
    2 17 ms 35 ms 8 ms 142-217-64-1.telebecinternet.net [142.217.64.1]
    3 9 ms 8 ms 8 ms 207-164-139-34.telebecinternet.net [207.164.139.34]
    4 17 ms 16 ms 16 ms 207.35.49.197
    5 17 ms 18 ms 19 ms tcore4-montreal02_1-14-0-0.net.bell.ca [64.230.91.20]
    6 17 ms 17 ms 18 ms bx1-montreal02_hundredgige0-2-0-0.net.bell.ca [64.230.91.125]
    7 16 ms 16 ms 62 ms ix-ae-10-0.tcore1.w6c-montreal.as6453.net [66.198.96.9]
    8 70 ms 24 ms 35 ms if-ae-12-2.tcore1.mtt-montreal.as6453.net [64.86.31.26]
    9 24 ms 25 ms 25 ms if-ae-0-2.tcore2.mtt-montreal.as6453.net [216.6.115.90]
    10 24 ms 24 ms 25 ms if-ae-5-2.tcore2.n0v-new-york.as6453.net [64.86.226.58]
    11 24 ms 24 ms 23 ms if-ae-2-2.tcore1.n0v-new-york.as6453.net [216.6.90.21]
    12 24 ms 24 ms 24 ms jfk-brdr-04.inet.qwest.net [63.235.41.97]
    14 42 ms 41 ms 40 ms hr3-et-1-1-0.ch3.savvis.net [216.33.94.118]
    15 40 ms 40 ms 40 ms 64.37.205.6

    Trace complete.

    Seems Savvis is stable for me, Couple of Hiccups but seems stable
  • Rastreando a rota para diag.enmasse.com [208.67.49.36]
    com no máximo 30 saltos:

    1 <1 ms <1 ms <1 ms 192.168.0.1
    2 1 ms 1 ms 1 ms 10.255.10.100
    3 2 ms 1 ms 1 ms 10.255.10.1
    4 5 ms 1 ms 1 ms 201.48.155.2
    5 20 ms 28 ms 18 ms 168.197.21.221
    6 36 ms 38 ms 23 ms 168.197.21.129
    7 18 ms 24 ms 26 ms 170.84.32.6
    8 120 ms 120 ms 120 ms 168.197.23.189
    9 121 ms 120 ms 121 ms 213.248.97.148
    10 122 ms 122 ms 122 ms 62.115.118.163
    11 116 ms 118 ms 116 ms 80.239.195.142
    12 * * * Esgotado o tempo limite do pedido.
    13 149 ms 148 ms 148 ms 216.33.94.118
    14 149 ms 154 ms 150 ms 64.37.205.6
    15 149 ms 149 ms 149 ms 208.67.48.14
    16 150 ms 150 ms 148 ms 208.67.48.14
    17 158 ms 158 ms 157 ms 208.67.49.36
  • NopiNopi ✭✭✭✭✭
    Not sure if these are still any meaningful at this day an hour, but here we go.

    1 4 ms 3 ms 3 ms 192.168.0.1
    2 * * * Request timed out.
    3 14 ms 16 ms 17 ms 10.2.2.213
    4 13 ms 18 ms 18 ms 10.65.13.10
    5 19 ms 16 ms 15 ms 24.171.212.97
    6 13 ms 13 ms 14 ms 24.171.212.49
    7 13 ms 15 ms 18 ms 24.171.212.25
    8 53 ms 52 ms 52 ms 63.245.90.162
    9 53 ms 50 ms 97 ms 69.79.100.30
    10 80 ms 76 ms 76 ms 213.46.182.17
    11 82 ms 78 ms 78 ms 63.235.40.105
    12 98 ms 102 ms 108 ms 67.14.8.190
    13 101 ms 103 ms 100 ms 216.33.94.118
    14 100 ms 135 ms 104 ms 64.37.205.6
    15 99 ms 99 ms 100 ms 208.67.48.14
    16 103 ms 108 ms 102 ms 208.67.48.14
    17 102 ms 100 ms 100 ms 208.67.49.36

    This is from the Caribbean on a 50mb cable network. No VPN, computer directly wired to modem. No other applications using bandwidth at the moment of the test.
Sign In or Register to comment.