[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

Tera fix your servers.....

124

Comments

  • counterpointcounterpoint mod
    edited September 2016
    Concepcion30 wrote: »
    But this is more or less a recent issue. What changed to cause the routing issue?

    It seems to be a few hops before it gets to the TERA servers, so maybe... a) the equipment is over-capacity, b) the equipment is malfunctioning, c) something is misconfigured so traffic isn't being distributed properly, or d) somebody screwed up. Either way, the colo provider needs to start making some phone calls, it looks like. (I know people think it seems to be timed with the server merger, but problems at this level are above what EME can affect on their end.)
  • AranathAranath ✭
    It would assure a lot of people if EME would comment on this at least. So we'd know they're at the very least collaborating with whoever it is they need to be talking to in order to resolve this problem. It's affecting quite a large number of players.
  • DraqskoDraqsko ✭✭
    Aranath wrote: »
    It would assure a lot of people if EME would comment on this at least. So we'd know they're at the very least collaborating with whoever it is they need to be talking to in order to resolve this problem. It's affecting quite a large number of players.

    What would you like them to say, "Sorry folks, it's the internet and there's nothing we can do about it?"

    Because that's really the fact of the matter in this situation. It's not even EME's ISP, it's Zayo so the only thing they can do is call their ISP, issue a complaint and hope that their ISP elevates their complaint AND Zayo decides to get off their [filtered] and do something about it. Usually Tier 1 providers will fix their equipment on their time and terms, not yours.

    The best thing a player can do with this type of problem is:

    Run a tracert to determine where the problem is.
    Report the problem, along with the tracert.
    Have some understanding that EME is just as helpless as you are once the problem goes beyond their own server or ISP, and blaming them is not going to lead to a solution.
  • AranathAranath ✭
    Draqsko wrote: »
    Aranath wrote: »
    It would assure a lot of people if EME would comment on this at least. So we'd know they're at the very least collaborating with whoever it is they need to be talking to in order to resolve this problem. It's affecting quite a large number of players.

    What would you like them to say, "Sorry folks, it's the internet and there's nothing we can do about it?"

    Because that's really the fact of the matter in this situation. It's not even EME's ISP, it's Zayo so the only thing they can do is call their ISP, issue a complaint and hope that their ISP elevates their complaint AND Zayo decides to get off their [filtered] and do something about it. Usually Tier 1 providers will fix their equipment on their time and terms, not yours.

    The best thing a player can do with this type of problem is:

    Run a tracert to determine where the problem is.
    Report the problem, along with the tracert.
    Have some understanding that EME is just as helpless as you are once the problem goes beyond their own server or ISP, and blaming them is not going to lead to a solution.

    Yes, we'd like to know that they're aware of the problem and have spoken with Zayo. Because random players calling Zayo complaining about game lag isn't going to generate as much positive action as a legal entity like EME. That's not unreasonable is it?

    "Sorry folks, it's the internet and there's nothing we can do about it?" nobody's expecting as idiotic a response as this and only your addled brain could have conceived this is what anyone on this thread had in mind.
  • DraqskoDraqsko ✭✭
    Aranath wrote: »
    Draqsko wrote: »
    Aranath wrote: »
    It would assure a lot of people if EME would comment on this at least. So we'd know they're at the very least collaborating with whoever it is they need to be talking to in order to resolve this problem. It's affecting quite a large number of players.

    What would you like them to say, "Sorry folks, it's the internet and there's nothing we can do about it?"

    Because that's really the fact of the matter in this situation. It's not even EME's ISP, it's Zayo so the only thing they can do is call their ISP, issue a complaint and hope that their ISP elevates their complaint AND Zayo decides to get off their [filtered] and do something about it. Usually Tier 1 providers will fix their equipment on their time and terms, not yours.

    The best thing a player can do with this type of problem is:

    Run a tracert to determine where the problem is.
    Report the problem, along with the tracert.
    Have some understanding that EME is just as helpless as you are once the problem goes beyond their own server or ISP, and blaming them is not going to lead to a solution.

    Yes, we'd like to know that they're aware of the problem and have spoken with Zayo. Because random players calling Zayo complaining about game lag isn't going to generate as much positive action as a legal entity like EME. That's not unreasonable is it?

    "Sorry folks, it's the internet and there's nothing we can do about it?" nobody's expecting as idiotic a response as this and only your addled brain could have conceived this is what anyone on this thread had in mind.

    You realize you can call your ISP just as well as EME can call theirs to complain about this issue.
  • DeathologistDeathologist ✭✭✭
    Not a single problem for me, My net has been always [filtered], my ping is what it was, 230 to 280, my country is [filtered] and my net is [filtered], there is nothing wrong with servers. b/c I will be one of the 1st ppl to feel it.
  • AranathAranath ✭

    I have called my ISP. Multiple times. As the first thing I suspected was my ISP might have been having problems. But it works fine with anything else and as far as they can figure there's absolutely nothing wrong on their end. I even tried connecting to the server from two other ISPs. Which again work absolutely fine, except when connecting to TERA. And as:
    counterpoint wrote: »
    Amphiptere wrote: »
    Like wtf is wrong with the servers.
    It's not the servers themselves, but the routing. If you are taking certain paths into Chicago through Zayo, you will have this problem. If you are taking a different path, no problem. This is why it isn't something EME either caused or can fix directly; they have to elevate it to their service provider who have to elevate it to their backbone provider. There's really nothing EME can do on the server or in the client.

    someone has already illustrated, if it is indeed a problem with Zayo affecting a service from EME it would appear it's in their vested interest to look into it at the very least. Since as far as i can figure the only thing this affects is connecting to TERA. I've even tried using a VPN to no avail. It still spikes to barely playable amounts.

    So before you say something like this "Sorry folks, it's the internet and there's nothing we can do about it?" for shock value at least actually read the thread so you have some context. Since I believe we're all talking about this to come up with a viable solution to this problem.
  • DraqskoDraqsko ✭✭
    edited September 2016
    Aranath wrote: »
    I have called my ISP. Multiple times. As the first thing I suspected was my ISP might have been having problems. But it works fine with anything else and as far as they can figure there's absolutely nothing wrong on their end. I even tried connecting to the server from two other ISPs. Which again work absolutely fine, except when connecting to TERA. And as:
    counterpoint wrote: »
    Amphiptere wrote: »
    Like wtf is wrong with the servers.
    It's not the servers themselves, but the routing. If you are taking certain paths into Chicago through Zayo, you will have this problem. If you are taking a different path, no problem. This is why it isn't something EME either caused or can fix directly; they have to elevate it to their service provider who have to elevate it to their backbone provider. There's really nothing EME can do on the server or in the client.

    someone has already illustrated, if it is indeed a problem with Zayo affecting a service from EME it would appear it's in their vested interest to look into it at the very least. Since as far as i can figure the only thing this affects is connecting to TERA. I've even tried using a VPN to no avail. It still spikes to barely playable amounts.

    So before you say something like this "Sorry folks, it's the internet and there's nothing we can do about it?" for shock value at least actually read the thread so you have some context. Since I believe we're all talking about this to come up with a viable solution to this problem.

    Actually, that is exactly what Treeshark did say in that post. counterpoint is Tree's alt account. Did you read the rest of my post? Where it said to DO A TRACERT AND REPORT THE RESULTS? You want them to help, well help them by providing the test results they ask for so they CAN help you.
  • AranathAranath ✭
    It was already sent. And it's gotten worse. From the previous tracert only spiking up to 500 ms it's turned into this.

    http://imgur.com/a/nw767

    It's just timing out completely now.
  • DraqskoDraqsko ✭✭
    Aranath wrote: »
    It was already sent. And it's gotten worse. From the previous tracert only spiking up to 500 ms it's turned into this.

    http://imgur.com/a/nw767

    It's just timing out completely now.

    Try pinging diag.enmasse.com (IP address: 208.67.49.180), it'll respond to ping requests. Not sure what address you were trying to reach, but if it was the server itself, that is why you got those results. The game servers don't respond to ping requests.

    For example:

    Pinging CH:
    Target Name: 208.67.49.68
    IP: 208.67.49.68
    Date/Time: 9/20/2016 8:35:28 AM - 9/20/2016 8:45:28 AM

    Hop Sent PL% Min Max Avg Host Name / [IP]
    1 *
    2 *
    3 *
    4 *
    5 5 0 16.51 18.83 17.20 nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
    6 5 0 16.10 18.76 16.97 68.105.31.102 [68.105.31.102]
    7 5 0 15.74 27.26 20.84 ae2.cr1.lga5.us.zip.zayo.com [64.125.31.213]
    8 5 0 33.36 64.04 42.93 ae27.cs1.lga5.us.eth.zayo.com [64.125.30.250]
    9 5 0 33.74 58.58 39.31 ae3.cs1.ord2.us.eth.zayo.com [64.125.29.209]
    10 5 0 32.70 35.50 34.19 ae27.cr1.ord2.us.zip.zayo.com [64.125.30.243]
    11 5 0 33.08 44.59 37.07 ae9.mpr1.ord11.us.zip.zayo.com [64.125.24.106]
    12 5 0 33.80 47.58 38.41 ae4.mpr1.ord5.us.zip.zayo.com [64.125.24.94]
    13 5 0 39.25 56.69 43.02 64.125.186.90.t00764-02.above.net [64.125.186.90]
    14 5 100 0 0 0 208.67.49.68 [208.67.49.68]

    As you can see, 100% loss on CH (and I ran that test WHILE I was in the game chatting with my guild so obviously the server is up).

    Pinging diag.enmasse.com:
    Target Name: diag.enmasse.com
    IP: 208.67.49.180
    Date/Time: 9/20/2016 8:40:52 AM - 9/20/2016 8:50:52 AM

    Hop Sent PL% Min Max Avg Host Name / [IP]
    1 *
    2 *
    3 *
    4 *
    5 5 0 15.93 16.52 16.25 nyrkbprj01-ae3.0.rd.ny.cox.net [68.1.5.157]
    6 5 0 15.67 16.81 16.09 68.105.31.102 [68.105.31.102]
    7 5 0 15.58 18.17 16.20 ae2.cr1.lga5.us.zip.zayo.com [64.125.31.213]
    8 5 0 33.66 41.05 38.14 ae27.cs1.lga5.us.eth.zayo.com [64.125.30.250]
    9 5 0 32.62 35.31 34.13 ae3.cs1.ord2.us.eth.zayo.com [64.125.29.209]
    10 5 0 33.66 48.75 37.77 ae27.cr1.ord2.us.zip.zayo.com [64.125.30.243]
    11 5 0 33.30 42.32 38.03 ae9.mpr1.ord11.us.zip.zayo.com [64.125.24.106]
    12 5 0 33.56 34.21 33.84 ae4.mpr1.ord5.us.zip.zayo.com [64.125.24.94]
    13 5 0 40.27 40.92 40.43 64.125.186.90.t00764-02.above.net [64.125.186.90]
    14 5 0 38.22 53.01 46.28 diag.enmasse.com [208.67.49.180]

    Since it is exactly the same routing as the game server up until the last hop, it'll work for actually determining the conditions between you and the game server, and respond to your requests.

    PS. and bonus points for seeing that it's IP: 64.125.30.250 that is the bane of my connection to the game. These results don't show the 150 ms ping on that router I got at 7 am Sunday morning and it is still jumping wildly.
  • AmphiptereAmphiptere ✭✭
    Why does this zayo adds 90-100 to my ping?
  • DraqskoDraqsko ✭✭
    edited September 2016
    Amphiptere wrote: »
    Why does this zayo adds 90-100 to my ping?

    It depends on the cause.

    Could be misconfigured router, could be failing or dead router forcing more traffic through other routers, could just be total traffic volume has increased beyond their projections so they don't have the equipment on hand yet to deal with it.

    Edit: I should add that is one of the drawbacks with how the internet works. Only the top tier provider will really know what is wrong at that level and they are not likely to come out and talk about it, so the internet remains a mystery to many of its users. When things go wrong, people look for someone to blame and the easiest targets are the people you deal with directly, companies like EME and your ISP. However because of the hierarchical structure of the web, generally those people and companies are the ones who are least responsible for your problems.
Sign In or Register to comment.