[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

Unstable Servers

2»

Comments

  • DelusoDeluso ✭✭✭✭
    It's not like I don't want to help but here is the tracert result:
    Vvc3zrB.jpg

    Yes I know, it's basically shows nothing at all but here I tried with 2 other tools.

    Traceroute 1 -
    traceroute to diag.enmasse.com (208.67.49.180), 30 hops max, 60 byte packets
    1 static.33.75.46.78.clients.your-server.de (78.46.75.33) 0.318 ms 0.311 ms 0.303 ms
    2 core21.fsn1.hetzner.com (213.239.229.249) 0.273 ms core22.fsn1.hetzner.com (213.239.229.253) 0.277 ms 0.279 ms
    3 core4.fra.hetzner.com (213.239.245.18) 4.959 ms core4.fra.hetzner.com (213.239.245.14) 4.955 ms 4.950 ms
    4 ix-et-3-1-0-0.tcore1.FR0-Frankfurt.as6453.net (195.219.219.9) 4.943 ms 5.143 ms 5.138 ms
    5 if-ae-2-2.tcore1.FNM-Frankfurt.as6453.net (195.219.156.1) 90.727 ms 93.174 ms if-ae-7-2.tcore1.FNM-Frankfurt.as6453.net (195.219.156.5) 90.996 ms
    6 if-ae-6-2.tcore1.AV2-Amsterdam.as6453.net (195.219.156.62) 90.906 ms if-ae-6-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.237) 90.139 ms if-ae-6-2.tcore1.AV2-Amsterdam.as6453.net (195.219.194.77) 90.538 ms
    7 if-ae-2-2.tcore2.AV2-Amsterdam.as6453.net (195.219.194.6) 89.587 ms 89.869 ms 89.571 ms
    8 if-ae-14-2.tcore2.L78-London.as6453.net (80.231.131.160) 87.019 ms 87.149 ms 86.524 ms
    9 if-ae-4-2.tcore2.N0V-New-York.as6453.net (80.231.131.158) 90.734 ms 89.042 ms 90.933 ms
    10 * if-ae-2-2.tcore1.N0V-New-York.as6453.net (216.6.90.21) 87.941 ms 100.566 ms
    11 63-235-41-97.dia.static.qwest.net (63.235.41.97) 93.873 ms 91.768 ms 92.329 ms
    12 nyc2-brdr-01.inet.qwest.net (205.171.134.50) 86.688 ms nyc2-brdr-01.inet.qwest.net (205.171.134.54) 93.812 ms 93.795 ms
    13 63.146.26.102 (63.146.26.102) 87.104 ms 63.146.26.158 (63.146.26.158) 93.288 ms 100.743 ms
    14 cr1-xe-10-0-1.jfk2.savvis.net (206.28.99.157) 87.014 ms cr1-xe-9-2-1.jfk2.savvis.net (206.28.99.165) 94.979 ms cr2-xe-1-1-1.jfk2.savvis.net (206.28.99.197) 87.384 ms
    15 cr1-te-0-1-0-1.chd.savvis.net (206.28.100.233) 106.212 ms cr2-te-0-1-0-1.chd.savvis.net (206.28.100.245) 105.942 ms cr1-te-0-1-0-1.chd.savvis.net (206.28.100.233) 107.384 ms
    16 cr1-tengig-0-0-2-0.chicago.savvis.net (204.70.196.241) 109.014 ms 109.139 ms 108.583 ms
    17 * * hr3-xe-8-0-0.elkgrovech3.savvis.net (204.70.198.73) 105.279 ms
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    Traceroute 2 -
    traceroute to 208.67.49.180 (208.67.49.180), 30 hops max, 60 byte packets
    1 praha-4d-c1-vl55.masterinter.net (77.93.199.253) 0.557 ms 0.641 ms 0.729 ms
    2 vl1387.cr3.r1-8.dc1.4d.prg.masterinter.net (83.167.254.150) 0.204 ms 0.211 ms 0.302 ms
    3 vl1388.cr2.c16.127.cecolo.prg.masterinter.net (83.167.254.148) 0.246 ms 0.240 ms 0.398 ms
    4 prag-b3-link.telia.net (62.115.147.38) 0.329 ms 0.299 ms 0.295 ms
    5 prag-bb1-link.telia.net (62.115.133.92) 0.345 ms win-bb2-link.telia.net (213.155.137.20) 5.837 ms win-bb2-link.telia.net (62.115.117.102) 5.840 ms
    6 ffm-bb3-link.telia.net (80.91.248.142) 18.654 ms ffm-bb3-link.telia.net (213.155.130.202) 18.897 ms ffm-bb3-link.telia.net (62.115.113.134) 18.720 ms
    7 ash-bb3-link.telia.net (213.155.135.57) 117.132 ms ash-bb4-link.telia.net (80.91.246.62) 114.461 ms ash-bb4-link.telia.net (213.155.135.59) 114.380 ms
    8 ffm-bb4-link.telia.net (62.115.116.159) 109.866 ms ffm-bb4-link.telia.net (62.115.137.166) 109.833 ms ash-b1-link.telia.net (62.115.113.217) 116.519 ms
    9 prs-bb3-link.telia.net (62.115.123.15) 117.995 ms qwest-ic-151228-ash-b2.c.telia.net (213.248.96.94) 122.904 ms 115.469 ms
    10 * * *
    11 208.173.158.25 (208.173.158.25) 115.789 ms 115.821 ms ash-b1-link.telia.net (62.115.123.37) 117.161 ms
    12 ash-b1-link.telia.net (62.115.113.209) 122.751 ms cr1-tengig0-7-2-0.washington.savvis.net (204.70.197.242) 134.183 ms ash-b1-link.telia.net (62.115.122.233) 121.958 ms
    13 * 206.28.96.209 (206.28.96.209) 136.063 ms 136.083 ms
    14 hr3-xe-8-0-0.elkgrovech3.savvis.net (204.70.198.73) 138.713 ms 136.845 ms 208.173.158.25 (208.173.158.25) 109.605 ms
    15 208.173.158.25 (208.173.158.25) 121.794 ms bpr1-so-6-0-0.VirginiaEquinix.savvis.net (208.173.52.65) 123.667 ms 63-235-40-90.dia.static.qwest.net (63.235.40.90) 122.840 ms
    16 206.28.96.209 (206.28.96.209) 127.626 ms * cr1-tengig0-7-2-0.washington.savvis.net (204.70.197.242) 143.545 ms
    17 * hr3-xe-8-0-0.elkgrovech3.savvis.net (204.70.198.73) 132.173 ms *
    18 * * hr3-xe-8-0-0.elkgrovech3.savvis.net (204.70.198.73) 144.560 ms
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *

    I also tried to included 3rd one here but it seems failed at savvis route, where it keeps forwarding my "connection" to 32 different router for about 2 minutes and stuck there in loop.

    Other than that I also tried basic ping to both diag.enmasse.com and patch.tera.enmasse-game.com, respectively.
    Ping to diag.enmasse.com -
    NQ6XXw4.jpg
    Ping to patch.tera.enmasse-game.com
    wpbxY5e.jpg

  • counterpointcounterpoint mod
    edited March 2017
    Yeah, unfortunately the two other traceroutes you provided don't help because they are not from your own connection. It looks like your router or something is blocking the traceroute from happening locally, so there's nothing really that can be gleamed from that.

    And yes, the ping to the patch server doesn't really matter because the patch server uses a CDN, so it'll be connecting near you. The game servers are still going to have to travel the globe. Given that you're playing from SEA, the problem could really be anywhere along the route.
  • DelusoDeluso ✭✭✭✭
    This is the 3rd one I mention earlier, which I download a tool to do the trace route from my location. The very 1st local IP is indeed from my modem (I disconnect my router and use direct connection from modem instead).

    Part 1 of 2 - Where it stuck at the red box for about a minute.
    7bo4YaV.jpg

    Part 2 of 2 - Self explained.
    YJpho2m.jpg

    If the problem (failed trace route) is from my modem/router, please advice.
    Current modem firewall setting.
    nXMR1aB.jpg
Sign In or Register to comment.