[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
Comments
Now i have a 250ms or more.
why?
im from mexico and i played with 90 - 120 ms... now so hard to play with crazy ping and anybody is connected to my net
All the "best".
also, so much lag everywhere, the game is unplayable.
Actually as someone who has followed this for a few weeks now, they did say there was an issue with Zayo's backbone and based on my own tracerts, it's pretty close to their server (somewhere between NYC and Chicago). Most players from Europe will get routed onto that pipeline if they do not VPN around it. Here is Zayo's network map: http://www.zayo.com/solutions/global-network/
Here's my latest tracert:
IP: 208.67.49.180
Date/Time: 9/30/2016 7:48:12 AM - 9/30/2016 7:58:12 AM
Hop Sent PL% Min Max Avg Host Name / [IP]
1 40 0 3.08 5.47 3.40 *
2 40 0 8.63 13.29 10.37 *
3 40 0 10.16 20.01 11.76 *
4 40 0 9.16 14.41 11.56 *
5 40 0 15.12 51.87 17.71 nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
6 40 0 15.05 31.88 17.60 68.105.31.102 [68.105.31.102]
7 40 0 15.11 24.29 17.32 ae2.cr1.lga5.us.zip.zayo.com [64.125.31.213]
8 40 0 33.38 57.28 43.61 ae27.cs1.lga5.us.eth.zayo.com [64.125.30.250]
9 40 0 32.77 80.35 38.62 ae3.cs1.ord2.us.eth.zayo.com [64.125.29.209]
10 40 0 32.62 54.25 35.52 ae27.cr1.ord2.us.zip.zayo.com [64.125.30.243]
11 40 0 32.71 49.73 34.55 ae9.mpr1.ord11.us.zip.zayo.com [64.125.24.106]
12 40 0 32.48 55.44 35.69 ae4.mpr1.ord5.us.zip.zayo.com [64.125.24.94]
13 40 0 33.07 62.08 37.08 64.125.186.90 [64.125.186.90]
14 40 0 32.69 38.89 34.97 diag.enmasse.com [208.67.49.180]
The bolded are problematic, that's a good tracert I've seen those nodes spike to over 150ms ping. My girlfriend also has issues with latency and disconnects in SWTOR, and when I run a tracert to their servers...
IP: 159.153.92.28
Date/Time: 9/30/2016 8:06:08 AM - 9/30/2016 8:16:08 AM
Hop Sent PL% Min Max Avg Host Name / [IP]
1 41 0 3.08 5.51 3.34 *
2 41 0 8.69 30.30 11.43 *
3 41 0 10.39 28.84 12.63 *
4 41 0 9.70 15.17 11.44 *
5 41 0 15.16 22.24 17.15 nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
6 41 0 14.76 26.72 17.43 68.105.31.102 [68.105.31.102]
7 41 0 15.25 21.53 17.17 ae2.cr1.lga5.us.zip.zayo.com [64.125.31.213]
8 41 0 16.54 28.99 18.86 ae1.cr2.lga5.us.zip.zayo.com [64.125.29.38]
9 41 0 22.50 48.23 25.41 ae27.cs2.lga5.us.eth.zayo.com [64.125.30.252]
10 41 0 22.47 77.35 28.30 ae4.cs2.dca2.us.eth.zayo.com [64.125.29.31]
11 41 0 22.59 39.30 25.99 ae27.cr2.dca2.us.zip.zayo.com [64.125.30.249]
12 41 7 22.68 45.15 25.36 ae1.er2.iad10.us.zip.zayo.com [64.125.20.122]
13 41 0 22.72 57.28 27.48 64.125.199.190.t00673-02.above.net [64.125.199.190]
14 41 0 22.47 28.80 24.75 159.153.92.69 [159.153.92.69]
15 41 0 23.08 53.73 27.06 159.153.92.28 [159.153.92.28]
Looks to me like Zayo has an issue somewhere in their network between White Plains, NY (64.125.31.213) and Washington D.C. and that is causing a cascade of issues along their network in the Mid Atlantic region.
I'm not saying this is the cause of everyone's problem, but it is the cause of MINE, and likely everyone living in Europe and connecting over the Atlantic. They are getting jammed into the firestorm as well as anyone living in the Mid Atlantic region and New England region.
Run your own tracerts and determine where the problem lies before you start pointing the finger.
Still today for me the same, zayo dropping packets. My guess is the whole support structure at troubleshooting network issues at EME is based entirely on placing blame on player's side because if issue is found on their end they have no action plan and we're just more or less told to deal with it until their mega ISP can somehow sort out their nonsense because nothing they can really do. Which is more or less what they're saying which is pretty poorly handled from a company's responsibility to their customers standpoint.
It's akin to us as players saying "my computer is fine, so its your fault," when the fault may as well lie with out ISP, but since we as indivuals can do nothing about our ISP's performance, we try to look elsewhere to blame. So essentially all EME's responses have been "our computers are fine, so its you" failing to look at the intermediary which servers 'their computers' to 'our computers'. In the end many people take these paths to your servers, not the other way around, so there at least needs to be some accountability on their end. Because if everyone's ISP is subject to being blame, by the inclusive property of EME being a part of everyone, their end can very well be to blame, even if its not 'their servers' exactly.
And its not like I don't know how this works, I've been a paying player for 4 years. I didn't just try this game last week and said I'm lagging with no history.
Did you ever consider that neither you, your ISP, EME or EME's ISP is to blame? That there is actually another party involved in that interaction that is neither directly connected to you nor EME?
If you want something to blame, place the blame on the decentralized, hierarchal structure of the internet. It has left all the users; you, me, even EME; without any way to directly redress problems we experience with it. In this particular case, EME has to go through the same process we would, complain to their ISP and then wait for their ISP to complain to Zayo.