[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
Comcast Lag Spikes
Has anyone with Comcast been spiking quite heavily around this time for the past several days? I know a few others on MT told me the same but was wondering if anyone else from other servers have been experiencing the same spikes.
0
Comments
Row 4 -- 9ms 9ms 12ms
Row 6 -- 20ms 19ms 22ms
Row 12 -- 45ms 41ms 41ms
I wasn't in game at the time, so I don't know if lag was occurring. Sometimes it doesn't last long, other times feels like 10 minutes or more.
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Users\myname>tracert 208.67.49.145
Tracing route to 208.67.49.145 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.0.0.1
2 7 ms 9 ms 7 ms 96.120.67.193
3 9 ms 9 ms 9 ms 68.85.184.41
4 9 ms 11 ms 8 ms te-0-5-0-5-ar01.chartford.ct.hartford.comcast.net [68.85.37.197]
5 13 ms 15 ms 14 ms he-1-12-0-0-ar01.needham.ma.boston.comcast.net [162.151.53.145]
6 36 ms 21 ms 22 ms be-7015-cr02.newyork.ny.ibone.comcast.net [68.86.90.217]
7 19 ms 19 ms 21 ms hu-0-15-0-0-pe03.111eighthave.ny.ibone.comcast.net [68.86.84.250]
8 18 ms 19 ms 19 ms ae2.er2.lga5.us.zip.zayo.com [64.125.13.205]
9 21 ms 22 ms 21 ms ae5.cr2.lga5.us.zip.zayo.com [64.125.21.82]
10 88 ms * 46 ms ae27.cs2.lga5.us.eth.zayo.com [64.125.30.252]
11 42 ms 41 ms * ae3.cs2.ord2.us.eth.zayo.com [64.125.29.213]
12 41 ms 43 ms 42 ms ae27.cr2.ord2.us.zip.zayo.com [64.125.30.245]
13 40 ms 41 ms 42 ms ae0.mpr2.ord6.us.zip.zayo.com [64.125.22.129]
14 42 ms 41 ms 40 ms ae3.mpr1.ord5.us.zip.zayo.com [64.125.28.206]
15 44 ms 41 ms 48 ms 208.67.49.145
Trace complete.
C:\Users\myname>
Seems like an issue at Zayo in New York City on the backend before it heads to Chicago. It so happens that my own connection is following the same path and I see the same thing at that hop right now.
Hopefully others can post their traceroutes to see if everyone has that in common.
This isn't the first time but it happened beginning of ninja patch for a few days around the same time and at random times like few weeks later. It's really annoying and impossible to deal with especially while tanking. I was in dfhm at the time so I didn't think about a traceroute but if it happens tomorrow, I will do one and see. Also yesterday I noticed the launcher was acting very weird, where it didn't have my username in there; I had to put it in and usually it should be saved. When that happens, then there is something bad going on for sure.
it's been going on for a long time but nothing's been done about it. zayo is largely involved in it from what i understand, and i had an issue with a hop from denver back when i was with that isp (i used to live in california.)