[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

Recent Server Stability Issues

1202123252637

Comments

  • Without zayo 70ms no packet loss. Down from 130 with occasional packet loss.
    Feelsamazingman
  • WTS a lot of lag
  • Horrible weekend so far. I'm experiencing 300-400ms now, compared to my usual 220-240ms before this Black Friday shenanigan.
  • CezzareCezzare ✭✭✭
    edited November 2016
    I've had ping spikes the whole weekend, in dungeons I would get 600 to 4000ms peaks during fights, it's the same with the open world zones, it's not like I spend a lot on EMP but I'm kinda glad I didn't buy an elite voucher this weekend since who knows when will the latency problems be adressed in a more efficient way.
  • natianatia ✭✭✭
    edited November 2016
    I've been having ping problems since the beginning of this patch. Used to have 40-60 ms, now it's a pretty constant 100+ but does go back down to my normal "green" ping at times, then other times spiking to 300/400. Also getting a lot of frames freezing, not sure why.
    I did a traceroute and it seems I'm not routing through Zayo, which seems to be the cause of a lot of people's ping spikes here. :o But I'm in NA tho, in Canada.

    Tracing route to 208.67.49.145 over a maximum of 30 hops

    5 160 ms 82 ms 71 ms xe-3-3-0.chi12.ip4.gtt.net [141.136.105.33]
    6 1264 ms 623 ms 305 ms centurylink-gw.ip4.gtt.net [173.205.63.230]
    7 37 ms 183 ms 48 ms 205.139.192.161
    8 2141 ms 2123 ms 246 ms hr2-te-12-0-1.elkgrovech3.savvis.net [204.70.198.82]
    9 532 ms 32 ms 54 ms 208.67.49.145

    If it's still like this, I'm sure many people won't be able to enjoy the 30man raid coming out in like 2 days ):
  • So yeah its not just people outside of NA being affected negatively because of zayo being off, its NA people as well. Some NA people I've talked to have had slightly higher ping then usual as well. So using the alternative to zayo is not the solution.
  • Well , isnt it possible to have a different routing for SEA and other regions? So in that way you guys go through a different routing and SEA Players can use the zayo servers? Cause currently Most of us are at 450ping and very unstable, but when the zayo servers are on , we get around 240-270 and its pretty stable
  • It would be really nice if what owen's asking is possible, and for the Eropean region as well.

    I'm still getting ping that's constantly spiking between 400 and 700, sometimes even over 1k, and crashing in dungeons. I tried using a vpn, but the ping remained the same, I just didn't crash, though maybe that was just a coincidence.

    I was even stupid enough to buy emp during the weekend sale, because I thought that Zayo will be turned back on after a few days, the same way it happened 2 weeks ago, but apparently I was wrong, since I still have this unplayable ping instead of my usual, stable 150.
    It's really getting annoying.
  • AGAIN!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  • IT WAS GOOD LAST WEEK NOW IT'S AGAIN A ****** :rage:
  • It seems like certain players experience the issue and others don't. Then later it's switched where the players who were experiencing the issue earlier, don't have any issue and others who weren't having the issue before, now have it. Since last week Wednesday, I had no issues at all all week. I hope I didn't jynx myself but yeah before Wednesday of thanksgiving week, I was getting a lot of ping spikes as well for like the prior 6-7 days.
  • the problem appears to be on savvis now
This discussion has been closed.