[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
Anyone still experience the increase of ping pass couple of weeks?
everyone i seem to talk to was having issues with ping recently, standard ping for me is usually 75-89, but when i enter a dungeon it goes from 75-110. but now im just at 110-130 pass week now, i thought it was just the storm coming in but apparently everyone is having this 20-40 ping jump that i've talked to. and i have yet to see EME or even a recent form post for this.
anyone know whats going on?
anyone know whats going on?
2
Comments
Basically anytime during "peak hours" you'll see ping spikes with delays ranging from small increase to in the thousands.
EME of course says there's nothing they can do or are willing to do? Either way it's been this way since October.
Sorry friend get used to it or move on to another game.
We complained about it and got a month of elite for free. Nothing fixed. Usual band aid solution.
Sucks to need a vpn now, and single server connection/vpn's don't go as low 150 for me.
Iv been playing since CBT. my ping used to be 30. 2014 was 50. 2016 was 75. Now with the ping spikes or servers right out freezing up for seconds at a time I'm lucky to ever see green ping. and I Iive on the east coast.
that is my thread about what is happening to me
There is a separate issue with ping spikes, but if your median ping has gone up, it's almost certainly routing-related.
1. Press Start and type "cmd" and press enter
2. In the Command Prompt window that appears type "tracert diag.enmasse.com"
3. Either take a screenshot of the resulting window, or use the "Mark" feature from the right-click menu (Ctrl+M) to copy/paste. You can skip the first few lines.
For example:
4 20 ms 20 ms 20 ms ae54.bar2.Toronto1.Level3.net [4.28.138.21]
5 * * * Request timed out.
6 33 ms 33 ms 33 ms 63-235-41-149.dia.static.qwest.net [63.235.41.149]
7 33 ms 33 ms 33 ms 63.146.26.106
8 33 ms 33 ms 33 ms cr1-xe-9-2-1.jfk2.savvis.net [206.28.99.165]
9 45 ms 47 ms 305 ms cr1-te-0-1-0-1.chd.savvis.net [206.28.100.233]
10 45 ms 45 ms 45 ms hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
11 46 ms 45 ms 46 ms 64.37.205.6
12 45 ms 45 ms 45 ms 208.67.49.180
If you look at my traceroute here, you can see something's not looking good at hop 9 (which a junction between New York and Chicago, long before it gets to EME's hosting provider).
With the amount of issues people (especially on Comcast) had on their previous backbone, Zayo, this was actually the better of the two -- even if it impacted your own average ping time.