[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

Routing change (with server migration?)

KillerPenguinsKillerPenguins
in TERA PC - General Discussion
Dunno if this affects anyone else, but since last tuesday or so, my connection to tera (or at least diag.enmasse.com) has been routing through dallas instead of straight to chicago. I'm mostly fine with it because it eliminates the packet loss I was experiencing with the other savvis route (making tera playable..), but it does mean my ping which was 15 with zayo is now stable at around 60-70. Did anyone else's route change or Is this limited to my isp?

Tracing route to diag.enmasse.com [208.67.49.180] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 20 ms 8 ms 7 ms dtr02nstlmo-tge-0-2-0-2.nstl.mo.charter.com [96.34.56.125]
4 10 ms 10 ms 20 ms crr02blvlil-bue-30.blvl.il.charter.com [96.34.76.221]
5 15 ms 15 ms 15 ms bbr01blvlil-bue-110.blvl.il.charter.com [96.34.2.170]
6 10 ms 10 ms 10 ms 38.140.99.113
7 16 ms 15 ms 16 ms be2316.ccr21.mci01.atlas.cogentco.com [154.54.80.121]
8 26 ms 25 ms 25 ms be2432.ccr31.dfw01.atlas.cogentco.com [154.54.3.133]
9 26 ms 26 ms 26 ms be2763.ccr41.dfw03.atlas.cogentco.com [154.54.28.74]
10 91 ms 64 ms 37 ms qwest.dfw03.atlas.cogentco.com [154.54.11.166]
11 25 ms 25 ms 25 ms 63-235-40-202.dia.static.qwest.net [63.235.40.202]
12 33 ms 33 ms 32 ms 206.28.101.229
13 59 ms 55 ms 55 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]
14 56 ms 55 ms 55 ms cr1-te-0-2-0-0.chd.savvis.net [204.70.194.73]
15 54 ms 54 ms 54 ms 206.28.101.165
16 53 ms 54 ms 54 ms 64.37.205.6
17 56 ms 53 ms 54 ms 208.67.49.180

Trace complete.

Comments

  • counterpointcounterpoint mod
    edited November 2017
    I don't notice any major changes here, so it may be that something changed to finally workaround the bad nodes from before (though indeed, that's a crazily roundabout way to do it).

    Of interest, yesterday CenturyLink (who owns Savvis) got approval to buy Level 3, another major U.S. backbone. As part of that process, they are also required to perform some divestitures. So, expect some more possible changes in the months ahead...
Sign In or Register to comment.