[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
High ping again
Below is my tracert and wtfast whom i rely on during these times of high ping can't even find a nearby server location in US
I'm from australia, melbourne
Tracing route to 208.67.49.28 over a maximum of 30 hops
1 <1 ms 2 ms <1 ms ~~~~~~~~~~
2 * * * Request timed out.
3 11 ms 12 ms 12 ms CPE-58-160-248-129.wa.bigpond.net.au [58.160.248
.129]
4 13 ms 14 ms 19 ms bundle-ether4.lon-edge901.melbourne.telstra.net
[203.50.76.2]
5 16 ms 17 ms 12 ms bundle-ether10.exi-core10.melbourne.telstra.net
[203.50.11.109]
6 36 ms 33 ms 40 ms bundle-ether12.chw-core10.sydney.telstra.net [20
3.50.11.124]
7 29 ms 25 ms 27 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.5
0.6.93]
8 29 ms 25 ms 33 ms bundle-ether1.sydo-core03.sydney.reach.com [203.
50.13.98]
9 27 ms 35 ms 30 ms i-0-5-0-3.sydp-core02.bi.telstraglobal.net [202.
84.223.17]
10 138 ms 139 ms 156 ms i-0-5-0-2.siko-core03.bx.telstraglobal.net [202.
84.141.234]
11 177 ms 173 ms 195 ms i-0-1-1-0-peer.siko02.pr.telstraglobal.net [134.
159.160.177]
12 141 ms 137 ms 146 ms kddi-peer.siko02.pr.telstraglobal.net [134.159.1
60.178]
13 167 ms 179 ms 181 ms otejbb206.int-gw.kddi.ne.jp [106.187.6.93]
14 269 ms 269 ms 265 ms lajbb002.int-gw.kddi.ne.jp [203.181.100.170]
15 268 ms 267 ms 268 ms ix-la4.int-gw.kddi.ne.jp [59.128.2.38]
16 206 ms 206 ms 203 ms los-brdr-01.inet.qwest.net [63.146.26.61]
17 * * * Request timed out.
18 266 ms 340 ms 220 ms 63-235-40-206.dia.static.qwest.net [63.235.40.20
6]
19 242 ms 203 ms 201 ms er2-xe-7-0-0.SanJoseEquinix.savvis.net [204.70.1
98.142]
20 208 ms 203 ms 203 ms cr2-te-0-5-0-1.sfo.savvis.net [206.28.98.117]
21 265 ms 271 ms 256 ms 204.70.192.134
22 257 ms 257 ms 262 ms hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.
73]
23 248 ms 253 ms 251 ms 64.37.205.6
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out
I'm from australia, melbourne
Tracing route to 208.67.49.28 over a maximum of 30 hops
1 <1 ms 2 ms <1 ms ~~~~~~~~~~
2 * * * Request timed out.
3 11 ms 12 ms 12 ms CPE-58-160-248-129.wa.bigpond.net.au [58.160.248
.129]
4 13 ms 14 ms 19 ms bundle-ether4.lon-edge901.melbourne.telstra.net
[203.50.76.2]
5 16 ms 17 ms 12 ms bundle-ether10.exi-core10.melbourne.telstra.net
[203.50.11.109]
6 36 ms 33 ms 40 ms bundle-ether12.chw-core10.sydney.telstra.net [20
3.50.11.124]
7 29 ms 25 ms 27 ms bundle-ether1.oxf-gw11.sydney.telstra.net [203.5
0.6.93]
8 29 ms 25 ms 33 ms bundle-ether1.sydo-core03.sydney.reach.com [203.
50.13.98]
9 27 ms 35 ms 30 ms i-0-5-0-3.sydp-core02.bi.telstraglobal.net [202.
84.223.17]
10 138 ms 139 ms 156 ms i-0-5-0-2.siko-core03.bx.telstraglobal.net [202.
84.141.234]
11 177 ms 173 ms 195 ms i-0-1-1-0-peer.siko02.pr.telstraglobal.net [134.
159.160.177]
12 141 ms 137 ms 146 ms kddi-peer.siko02.pr.telstraglobal.net [134.159.1
60.178]
13 167 ms 179 ms 181 ms otejbb206.int-gw.kddi.ne.jp [106.187.6.93]
14 269 ms 269 ms 265 ms lajbb002.int-gw.kddi.ne.jp [203.181.100.170]
15 268 ms 267 ms 268 ms ix-la4.int-gw.kddi.ne.jp [59.128.2.38]
16 206 ms 206 ms 203 ms los-brdr-01.inet.qwest.net [63.146.26.61]
17 * * * Request timed out.
18 266 ms 340 ms 220 ms 63-235-40-206.dia.static.qwest.net [63.235.40.20
6]
19 242 ms 203 ms 201 ms er2-xe-7-0-0.SanJoseEquinix.savvis.net [204.70.1
98.142]
20 208 ms 203 ms 203 ms cr2-te-0-5-0-1.sfo.savvis.net [206.28.98.117]
21 265 ms 271 ms 256 ms 204.70.192.134
22 257 ms 257 ms 262 ms hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.
73]
23 248 ms 253 ms 251 ms 64.37.205.6
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out
2
Comments
You mean always.
I live in Wisconsin, and from where I live, Chicago is a 3 hour drive away, less than 200 miles.
You're right, I know it doesn't take an intercontinental connection to have ping spikes. I want to make sure people aren't confusing TERA server stability with internet stability. From a player perspective, the two can seem the same a lot of the time. From our perspective as a game company, we can be doing everything 100% right and have perfectly stable servers, but someone connecting from a great distance is much more likely to have ping spikes anyway, especially during peak internet traffic hours (which happen to line up alongside our Power Hour schedule). The source of that spike in traffic could be anywhere between your home and our servers. A player in Australia will typically route through Japan, for instance.
As far as actions we are taking and traffic we're monitoring, some of that was addressed in the network outages and compensation news post. There are a few things we're considering for the new year as far as TERA service goes, and our goal is always to give players the best possible experience when connecting to the game. At the moment there aren't any announcements though.
However, I have seen messages and chat from people from around the US--CA, IL, NY, FL, etc--who are experiencing this problem. And, while for me personally the answer may still be to just move on, it behooves EME as a company to address this problem head on. Don't pretend it is not a serious problem, or one we just have to live with--dig in and do something about it, even if that means rehosting the servers to other locations, contracting with vendors who specialize is optimizing content delivery, or whatever. Or, just pack it in, give up on those of us having problems and hope there are enough players left to keep the NA game afloat.