[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
Thank you for your insight. Taking the time to learn about this more, this is also definitely one of the possible theories. Allow me to play the Devil's Advocate.
It's just that this "primetime" is so variable in length but seems to be rather punctual to when it begins (e.g. the 21st had high latency for roughly 4 hours starting dead-on at 7PM EST while the 20th had about 1 hour instead starting nearly at the same time for me). Considering this is a Sunday and a Monday, your theories of servers getting overloaded starting nearly at the same time but ending at different times sounds a bit off. You're literally suggesting people in California got off work ~4PM and simultaneously used their internet that uses Zayo's routing service for one hour on a SUNDAY.
Of course, there is definitely the possibility of coincidence and please keep in mind I'm taking your words with a grain of salt. Please also note that this "spike in latency and packet loss" starts almost at the same time on top of the hour every day for many individuals which causes additional suspicion that it's not really overload that's happening, but something much more controversial.
Yep. Yesterday the latency started on time at 7 PM EST and continued until exactly 11:05 PM EST (as shown in my screenshot). I hear that Zayo was removed temporarily quite recently which is when you might have had no problems (I share the same experience), so there's that as well.
When Zayo was off I was lagging way worse, being in middle-east ( I know [filtered] place to live, trust me tried to get out
While I sympathize with those of you who are playing from another Continent, the issue at hand is that Zayo is useless for those of us in NA and seems to be only causing problems for us. My ping is literally the same to chicago whether Zayo is on or off. But the only thing Zayo has been ensuring is this amazing 1000+ ping spikes between 6-9/10 PM CST.
I thought EME is NA publisher. Shouldn't their priority be the NA player base?
While I also sympathize with you as well, please note that from the Middle-East, pings of 150-200 to Chicago is fairly normal (considering EU players have roughly 100). Zayo is helping you guys, but making it impossible for some of us to play in the East Coast at specific times.
Again I have nothing against you, but if you're demanding to have a smoother experience on a server not specifically designed to serve you, I would retaliate and comment that you should consider joining other servers instead.
Just to be clear, "something more controversial" like what exactly? This is an issue hitting nodes from various routing providers in all sorts of locations. The best thing I can think of, if there's a specific root cause for hitting at exactly a given time, is that one of the botnet scripts is timed to go off at that time (7pm EST is 0:00 UTC). As far as TERA is concerned, if you're on an unimpacted route, you can be online at 7pm EST and see absolutely no change in server performance. It all depends on your provider and location. But the fact that it's route-driven rules out any particular problem in the client or on the server itself.
DDoS, Zayo's infrastructure dying or just heavy traffic.
Since you mentioned it always happening at the same time, it made sense that it is a botnet. As much as that goes though, why do people outside of NA with completely no relation to Zayo itself have a better ping?
My theory is that the botnet itself utilised Comcast and various Internet providers in NA. Routing within the region and outside the region have different paths to the datacenter. What if the cable route for people that are affected are the same ones being hit by the script?
The ping plotted is the step right before Zayo, which usually is what we can say as the bridge. ISPs need to use this bridge to route to the routing provider in order to send to the intended party. If Zayo only affects some parties, it isnt Zayo at fault but the point before it. That point is (still) completely out of EME's control even if said point is still owned by Zayo.
As for why the other provider caused problems for people outside of NA, it is because the provider never really supported routes outside of NA to begin with.
To think about it though, it is not the first time I talked about servers getting packet loss midroute. Is EME to blame? No. Is Zayo to blame? No. Is Comcast to blame? As much as it seemed to be the cause, no. The fault is in the hackers that caused everything to begin with.
Lag spikes that I've never experienced only came after the triple drop.
it's been how long now and they still haven't said a single word about this?
Do they really want their comcast player base to just stop playing the game or what?
@Denommenator @Spacecats @DonkeyProphet ... At least post some updates about what you're doing on this forever lag in peak hours issue, FFS.
So actually for the last ~5 days or so, they're routing the traffic over Savvis instead of Zayo. It seems to be better for some and worse for others. But, they did switch to another backbone to see what would happen. I guess see if it's better for you or not.
Bit of an update, I logged in to get my bonuses and such as normal and... 130ms ping. Which shouldn't all that bad but MAN my UI was lagging something fierce. I run on a machine with an overclocked i5 3570K and a GTX 960. Not to mention I was on the North Docks, so no hardware bottlenecks there. The packet loss through this routing service must be insane for me to be seeing that much UI lag. O.o
What ISP are you on and what general area are you connecting from? Can you post your traceroute (excluding the first few hops)?
Can confirm that it's been much better for me lately. No timely lag like before. Only new-patch/dreamstorm lag, but that's expected.
I'm on Charter Communications in Eastern Washington at the moment, although I am in the process of moving to Western Washington, at which point I'll be on Comcast (Eugh).
Aaaaaaaaand here's the pingplotter.