[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

pls fix issues with "Certain internet provider" issues connection to server from australia

13»

Comments

  • SkiffzSkiffz ✭
    edited December 2016
    counterpoint wrote: »
    Skiffz wrote: »
    Tracert below; doesn't look particularly untoward, but something must have changed in the last few days?

    It's better to tracert to diag.enmasse.com because the patch server uses a CDN that has nodes all over the world, and so isn't representative of the in-game connection. Most likely you're being routed through Japan now, as the people above, and this is adding to your ping time.

    Well spotted; cheers for that. Was unaware of the diag.enmasse.com as the connection troubleshooting page provided by EME suggests doing the tracert to the location I originally tested to. GG.

    Tracing route to diag.enmasse.com [208.67.49.180]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
    2 3 ms 3 ms 3 ms 114.23.3.254
    3 5 ms 1 ms 3 ms ae-0-942.cr1.mdr.vygr.net [114.23.3.248]
    4 4 ms 3 ms 3 ms 203.97.9.97
    5 2 ms 3 ms 3 ms be10-2.bgnzftc02.akl.vf.net.nz [203.109.130.41]
    6 4 ms 6 ms 3 ms unknown.telstraglobal.net [134.159.174.41]
    7 5 ms 3 ms 3 ms i-0-2-0-5.sydo-core02.bi.telstraglobal.net [202.84.223.42]
    8 140 ms 139 ms 138 ms i-0-0-4-0.1wlt-core01.bx.telstraglobal.net [202.84.142.106]
    9 131 ms 131 ms 131 ms i-0-7-0-0.1wlt-core01.bi.telstraglobal.net [202.40.149.213]
    10 188 ms 191 ms 191 ms unknown.telstraglobal.net [202.84.137.73]
    11 213 ms 215 ms 216 ms i-0-1-1-0-peer.siko02.pr.telstraglobal.net [134.159.160.177]
    12 212 ms 211 ms 237 ms kddi-peer.siko02.pr.telstraglobal.net [134.159.160.178]
    13 214 ms 220 ms 213 ms otejbb205.int-gw.kddi.ne.jp [106.187.6.73]
    14 225 ms 227 ms 227 ms pajbb001.int-gw.kddi.ne.jp [203.181.100.66]
    15 224 ms 227 ms 227 ms ix-pa10.int-gw.kddi.ne.jp [111.87.3.122]
    16 227 ms 227 ms 227 ms 124.215.192.78
    17 224 ms 227 ms 227 ms sjp-brdr-05.inet.qwest.net [67.14.34.98]
    18 226 ms 227 ms 227 ms 63-235-40-18.dia.static.qwest.net [63.235.40.18]
    19 226 ms 227 ms 227 ms 206.28.98.70
    20 230 ms 229 ms 230 ms cr2-tengig0-7-3-0.sanfrancisco.savvis.net [204.70.206.57]
    21 277 ms 275 ms 275 ms 204.70.192.134
    22 276 ms 275 ms 275 ms hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
    23 275 ms 276 ms 274 ms 64.37.205.6
    24 276 ms 275 ms 275 ms 208.67.49.180

    Trace complete.

    So far only comment from EME is the above by spacecats confirming this is a different issue? After a few days?

    1434214418945.jpg

    The fact remains that the only changes made were on EME's end, and what they've done is make endgame content unplayable for myself and several others.

    But you're right, clearly the issue lies on our end, and all players experiencing a dramatic ping increase overnight that has remained stably high ever since have to contact their support providers and request they resolve the issue that was never present prior. That makes total sense, and I have no idea how I failed to come to that conclusion myself as an infrastructure and user support engineer with 8 years experience working for the largest service provider in my country. >.>

    All I know is when we make a change that causes a large number of our customers - yeah, that's right, I have been purchasing elite status consistently, and also buy the odd cash shop item for my characters, thus making me a paying customer - we get an uncomfortable conversation with management and pressure to fix those services by either reversing the change if they've caused more harm than good or work on the outstanding issues as a priority.

    At the very least we issue an impact statement with expected timelines and regular updates. Because that's the professional thing to do.
  • AnnastashiaAnnastashia ✭✭
    Skiffz wrote: »
    counterpoint wrote: »
    Skiffz wrote: »
    Tracert below; doesn't look particularly untoward, but something must have changed in the last few days?

    It's better to tracert to diag.enmasse.com because the patch server uses a CDN that has nodes all over the world, and so isn't representative of the in-game connection. Most likely you're being routed through Japan now, as the people above, and this is adding to your ping time.

    Well spotted; cheers for that. Was unaware of the diag.enmasse.com as the connection troubleshooting page provided by EME suggests doing the tracert to the location I originally tested to. GG.

    Tracing route to diag.enmasse.com [208.67.49.180]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
    2 3 ms 3 ms 3 ms 114.23.3.254
    3 5 ms 1 ms 3 ms ae-0-942.cr1.mdr.vygr.net [114.23.3.248]
    4 4 ms 3 ms 3 ms 203.97.9.97
    5 2 ms 3 ms 3 ms be10-2.bgnzftc02.akl.vf.net.nz [203.109.130.41]
    6 4 ms 6 ms 3 ms unknown.telstraglobal.net [134.159.174.41]
    7 5 ms 3 ms 3 ms i-0-2-0-5.sydo-core02.bi.telstraglobal.net [202.84.223.42]
    8 140 ms 139 ms 138 ms i-0-0-4-0.1wlt-core01.bx.telstraglobal.net [202.84.142.106]
    9 131 ms 131 ms 131 ms i-0-7-0-0.1wlt-core01.bi.telstraglobal.net [202.40.149.213]
    10 188 ms 191 ms 191 ms unknown.telstraglobal.net [202.84.137.73]
    11 213 ms 215 ms 216 ms i-0-1-1-0-peer.siko02.pr.telstraglobal.net [134.159.160.177]
    12 212 ms 211 ms 237 ms kddi-peer.siko02.pr.telstraglobal.net [134.159.160.178]
    13 214 ms 220 ms 213 ms otejbb205.int-gw.kddi.ne.jp [106.187.6.73]
    14 225 ms 227 ms 227 ms pajbb001.int-gw.kddi.ne.jp [203.181.100.66]
    15 224 ms 227 ms 227 ms ix-pa10.int-gw.kddi.ne.jp [111.87.3.122]
    16 227 ms 227 ms 227 ms 124.215.192.78
    17 224 ms 227 ms 227 ms sjp-brdr-05.inet.qwest.net [67.14.34.98]
    18 226 ms 227 ms 227 ms 63-235-40-18.dia.static.qwest.net [63.235.40.18]
    19 226 ms 227 ms 227 ms 206.28.98.70
    20 230 ms 229 ms 230 ms cr2-tengig0-7-3-0.sanfrancisco.savvis.net [204.70.206.57]
    21 277 ms 275 ms 275 ms 204.70.192.134
    22 276 ms 275 ms 275 ms hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
    23 275 ms 276 ms 274 ms 64.37.205.6
    24 276 ms 275 ms 275 ms 208.67.49.180

    Trace complete.

    So far only comment from EME is the above by spacecats confirming this is a different issue? After a few days?

    1434214418945.jpg

    The fact remains that the only changes made were on EME's end, and what they've done is make endgame content unplayable for myself and several others.

    But you're right, clearly the issue lies on our end, and all players experiencing a dramatic ping increase overnight that has remained stably high ever since have to contact their support providers and request they resolve the issue that was never present prior. That makes total sense, and I have no idea how I failed to come to that conclusion myself as an infrastructure and user support engineer with 8 years experience working for the largest service provider in my country. >.>

    All I know is when we make a change that causes a large number of our customers - yeah, that's right, I have been purchasing elite status consistently, and also buy the odd cash shop item for my characters, thus making me a paying customer - we get an uncomfortable conversation with management and pressure to fix those services by either reversing the change if they've caused more harm than good or work on the outstanding issues as a priority.

    At the very least we issue an impact statement with expected timelines and regular updates. Because that's the professional thing to do.

    hey bud it's all our fault you're not allowed to complain
  • AnnastashiaAnnastashia ✭✭
    Spacecats wrote: »
    Annastashia wrote: »
    EME said themselves that it was to do with the DDOS attacks on the 20th of Nov that is causing these issues.

    There are huge outages during November as detailed in this post about player compensation. While these issues were significant and lasted hours (sometimes), they're unrelated to the issue you're describing.

    How is this unrelated, you literally talk about the network provider in Australia? jesus christ
  • GekaiGekai ✭
    Merry Christmas Sea players no playable ping sorry guys.
Sign In or Register to comment.