[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85

[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20

Thank you Enmasse!

Thank you for rising my ping over 300 now i can finally enjoy the game!

Well at least now i don't get dc the only thing i can do now is have some hope that my problem somehow will be solved before the leveling event today ;_;

Comments

  • edited November 2017
    FWIW... it doesn't look like they actually changed anything on their side. It's still routed through Zayo, and the servers themselves are still returning about the same ping. If you post your traceroute to diag.enmasse.com, most likely we'll find the culprit somewhere along the route.
  • That's always my ping
  • @counterpoint

    You know, I see stuff like this forum post so often. If so many people are having ping/performance issues, eventually we have to stop looking for faults on the players end and admit there is something going majorly wrong on Tera's side.
  • tisnotmetisnotme ✭✭✭✭
    @LegateTR
    Yet agree , as it's not like them that have the problem at similar time are using the same route to get to tera so why look there at all seeing we all have an under ideal line to the game thru our own independent ISP provider that never had any problems
    Like the one the Aussies recently had with the under water cable being severed or the Brasilian one where the provider had problems too
  • Actually my problem started when they changed to Zayo this improved the gameplay experience for some but made it worst to others also i said my ping is over 300 not 300 (goes from 300 to 600 wich is literally unplayable) i already tested other games online and everything is working fine i have problems only with Tera
  • edited November 2017
    LegateTR wrote: »
    @counterpoint

    You know, I see stuff like this forum post so often. If so many people are having ping/performance issues, eventually we have to stop looking for faults on the players end and admit there is something going majorly wrong on Tera's side.

    I'm not saying it's a fault "on the players end" -- it's a fault in the route, which is in between. If you follow forums for other MMOs these days, this a very common issue right now covering multiple different backbones/providers/server locations/etc. (Even if you personally are only having the problem with TERA, that are other people who are only having the problem with FFXIV, or BnS, or BD, and on and on. You'll see the same sorts of posts in their forums too.)

    In order to fix the problem, the only way is to isolate the actual root cause and try to get that escalated. The only way to do that traceroutes from as many people as possible. Again, this isn't because I'm trying to pass the blame, or deflect fault away from TERA/EME or whatever... it's the root cause of the issue. The only way anyone can even hope to get the issue solved is to pinpoint exactly which nodes are causing the problem.


    Edit: As a point of reference, here's my traceroute at the moment. I'm fortunate to not have any major issues en-route right now, but it could easily change at any time.

    6 29 ms 29 ms 37 ms 100ge9-2.core2.chi1.he.net [184.105.80.5]
    7 29 ms 39 ms 28 ms 100ge5-2.core1.chi1.he.net [184.105.81.98]
    8 49 ms 29 ms 31 ms mfnx-as6461.10gigabitethernet1-8.core1.chi1.he.net [216.66.77.218]
    9 30 ms 37 ms 35 ms ae17.cr2.ord2.us.zip.zayo.com [64.125.31.82]
    10 67 ms 36 ms 34 ms ae0.mpr2.ord6.us.zip.zayo.com [64.125.22.129]
    11 33 ms 33 ms 33 ms ae3.mpr1.ord5.us.zip.zayo.com [64.125.28.206]
    12 33 ms 33 ms 33 ms 64.125.186.90
    13 32 ms 33 ms 33 ms 208.67.49.180
  • tisnotmetisnotme ✭✭✭✭
    Any chance you've done a trace rout check and sent to them ?
    I don't know how to read them but counter point does if you also would like him to look over it and show what's going on
  • CatservantCatservant ✭✭✭✭
    What Counterpoint said. Our internet backbone needs a lot of work. The more data EME has, the more successfully they can yell at the providers and hopefully shame them into action.
  • It's not the backbone that needs work sadly, it's the politics. Everywhere there's a grey area, people on both sides try to take everything they can, and it leaves situations like this where neither provider is willing to pay to upgrade their peering server so it just sucks and dies, basically.
  • LesbianViLesbianVi ✭✭✭✭✭
    You are so welcomed
Sign In or Register to comment.