[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

another whiny lag post!

KillerPenguinsKillerPenguins
in TERA PC - General Discussion
Hi i've made about 10 posts that sound basically identical to this since october of last year or so. I'm making another one because i can't play tera at the moment for reasons beyond my control. Can someone please explain why savvis is so garbage that they think the fastest way to get from illinois to illinois involves going through georgia and texas? i live 250 miles from the tera server and the route my connection takes to get there is between 1700 and 3200 miles, depending on I HAVE NO IDEA WHAT! IT JUST CHANGES RANDOMLY DURING RUNS! I main lancer and have been enjoying my reaper and warrior, which should basically explain to anyone why having incredibly high and unstable ping is not a great thing! other chicago based games and services give me a stable 15-25 ping, which is dead on for what i had while tera was using zayo. this post won't accomplish anything because the people running tera's data center are either not competent or not willing to fix this garbage (it's been going on for so long that it doesn't really matter which one it is) but i just felt like ranting because i can't play tera and don't really have anything better to do! have a nice day.

Comments

  • LesbianViLesbianVi ✭✭✭✭✭
    Yeah, I felt lots of lags since yesterday.
  • KillerPenguinsKillerPenguins ✭✭✭✭
    This has been on and off since october. any time i'm forced to use savvis, my connection quality plummets. the last week or two has been particularly bad though, the route swapping and latency is just horrific.
  • LesbianViLesbianVi ✭✭✭✭✭
    KillerPenguins wrote: »
    This has been on and off since october. any time i'm forced to use savvis, my connection quality plummets. the last week or two has been particularly bad though, the route swapping and latency is just horrific.

    I think it is time for EME, change server location.
  • KillerPenguinsKillerPenguins ✭✭✭✭
    It's not the location of the server - chicago is a great choice for an NA-based game. Their networking team is just not providing adequate routing options. It forces everyone to route through savvis, which is always going to cause problems - it's (almost) impossible to ensure that every ISP on the planet (or even in north america) has quality routes to their servers with only one option, as it relies on every single isp being able to peer with centurylink (who owns savvis) in a manner that doesn't increase latency. In my case, it forces my connection to route through dallas, atlanta, denver, or two of the three depending on network load which means my route on savvis is between five and ten times longer than my route on zayo was. That's reflected in my ping which is between five and ten times higher than it was on zayo.
  • voidyvoidy ✭✭✭✭✭
    I remember when they released that test server in Washington or whatever and it was so stable and smooth.
    Server instability and node issues have been a problem in this game for about a year now, yeah. Sucks.
  • LesbianViLesbianVi ✭✭✭✭✭
    KillerPenguins wrote: »
    It's not the location of the server - chicago is a great choice for an NA-based game. Their networking team is just not providing adequate routing options. It forces everyone to route through savvis, which is always going to cause problems - it's (almost) impossible to ensure that every ISP on the planet (or even in north america) has quality routes to their servers with only one option, as it relies on every single isp being able to peer with centurylink (who owns savvis) in a manner that doesn't increase latency. In my case, it forces my connection to route through dallas, atlanta, denver, or two of the three depending on network load which means my route on savvis is between five and ten times longer than my route on zayo was. That's reflected in my ping which is between five and ten times higher than it was on zayo.

    Zayo is bad too, you might not have lags, but many more get lags. The thing is, there was no lag a year ago, when game was more crowded. So, Zyo, Saavis both got problems.
  • KillerPenguinsKillerPenguins ✭✭✭✭
    Yes, as I said forcing everyone to route through one provider is always going to cause problems. There was a brief period earlier this year where zayo and savvis were both possible routes, you may remember it as "that time people weren't lagging so much" but zayo was removed as an option when the login server crashed. We don't really get much explanation of this stuff as players, which would be fine if the problems were actually adequately addressed at any point but when it just gets worse and worse for months on end with no acknowledgement, it feels like en masse just does not know what they're doing. (Sorry.)
  • counterpointcounterpoint mod
    edited September 2017
    KillerPenguins wrote: »
    Yes, as I said forcing everyone to route through one provider is always going to cause problems. There was a brief period earlier this year where zayo and savvis were both possible routes, you may remember it as "that time people weren't lagging so much" but zayo was removed as an option when the login server crashed.

    I've been monitoring this issue closely all this time, and I'm pretty sure there was not a time when both routes were active at the same time. For a while they swapped between them fairly often, but it appears to have always been one or the other. Of course, the way your ISP and the backbone providers choose to get you into the EME's chosen backbone can vary (you could very well still hit Zayo on the way in before swapping to Savvis, or vice-versa when it was the other way around), and this might explain the change you experienced. But it's not like they just have to check some box to add more possible routing options, and then automagically your ISP will choose the lowest-latency route. If only that were the case...
  • KillerPenguinsKillerPenguins ✭✭✭✭
    edited September 2017
    counterpoint wrote: »
    KillerPenguins wrote: »
    Yes, as I said forcing everyone to route through one provider is always going to cause problems. There was a brief period earlier this year where zayo and savvis were both possible routes, you may remember it as "that time people weren't lagging so much" but zayo was removed as an option when the login server crashed.

    I've been monitoring this issue closely all this time, and I'm pretty sure there was not a time when both routes were active at the same time. For a while they swapped between them fairly often, but it appears to have always been one or the other. Of course, the way your ISP and the backbone providers choose to get you into the EME's chosen backbone can vary (you could very well still hit Zayo on the way in before swapping to Savvis, or vice-versa when it was the other way around), and this might explains the change you experienced. But it's not like they just have to check some box to add more possible routing options, and then automagically your ISP will choose the lowest-latency route. If only that were the case...

    I tried to find a part of your statement which was accurate and failed. You don't understand this issue well enough to comment.

    Edit: Sorry, this was unnecessarily rude. You're trying your best, but it's not helpful to give incorrect information. I'll try to explain it relatively simply. Your first misunderstanding seems to be that I'm expecting zayo and savvis to show up on the same traceroute, but that isn't what it means. Multiple routing options does not mean Me->Zayo->savvis->tera, it means Me->zayo->tera, Other people->savvis->tera, based on which route is best for each person. It's incredibly unlikely you'll route through both zayo and savvis unless you're forced to route through zayo (this happened during part of last year/early this year) and you're on a centurylink isp, or if your isp is carried on zayo's network and you're forced to route through savvis. It's likely you saw your own connection changing between zayo and savvis while they were both active depending on network conditions between you and chicago. As far as adding more possible routing options goes, it's actually fairly straightforward but adds some complications from a networking standpoint. However it's something a decent datacenter/network ops team should not struggle with for this long, and indeed worked well for tera until their login server crashed and zayo was removed from the routing.
  • StitchedSoulStitchedSoul ✭✭✭✭
    I don't know about routing but with any provider I have 250-550 last 2 days. My normal 170-205.
  • counterpointcounterpoint mod
    edited September 2017
    KillerPenguins wrote: »
    counterpoint wrote: »
    KillerPenguins wrote: »
    Yes, as I said forcing everyone to route through one provider is always going to cause problems. There was a brief period earlier this year where zayo and savvis were both possible routes, you may remember it as "that time people weren't lagging so much" but zayo was removed as an option when the login server crashed.

    I've been monitoring this issue closely all this time, and I'm pretty sure there was not a time when both routes were active at the same time. For a while they swapped between them fairly often, but it appears to have always been one or the other. Of course, the way your ISP and the backbone providers choose to get you into the EME's chosen backbone can vary (you could very well still hit Zayo on the way in before swapping to Savvis, or vice-versa when it was the other way around), and this might explains the change you experienced. But it's not like they just have to check some box to add more possible routing options, and then automagically your ISP will choose the lowest-latency route. If only that were the case...

    I tried to find a part of your statement which was accurate and failed. You don't understand this issue well enough to comment.

    Edit: Sorry, this was unnecessarily rude. You're trying your best, but it's not helpful to give incorrect information. I'll try to explain it relatively simply.
    Respectfully, I did actually figure that was what you were saying, but I just don't think what you're describing seems accurate from the data I've reviewed on this issue.

    KillerPenguins wrote: »
    Your first misunderstanding seems to be that I'm expecting zayo and savvis to show up on the same traceroute, but that isn't what it means. Multiple routing options does not mean Me->Zayo->savvis->tera, it means Me->zayo->tera, Other people->savvis->tera, based on which route is best for each person. It's incredibly unlikely you'll route through both zayo and savvis unless you're forced to route through zayo (this happened during part of last year/early this year) and you're on a centurylink isp, or if your isp is carried on zayo's network and you're forced to route through savvis. It's likely you saw your own connection changing between zayo and savvis while they were both active depending on network conditions between you and chicago.

    This was not a misunderstanding. I have actually seen the scenario I described in TERA traceroutes I've reviewed. But I have never seen the situation you've described in all the data I've reviewed over the years. It has always been completely consistent: one provider at a time. As far as I am aware, there has never been a time when they had both active at once -- there's a primary and a failover. I won't go as far as to claim it's impossible, but I've looked at a lot of data (and tracked a lot of forum feedback), and I've never seen it yet. Maybe it should be fairly straightforward, but if so (and if it produced the results you claimed) there's no reason they would not still have that arrangement.

    I'm open to being proven wrong, but I have reviewed an awful lot of traceroutes for this game for people over the years, and what you're describing seems highly irregular. Unless the period you're describing was extremely brief? (Some sort of test that went horribly wrong?)
  • AbaddonoffireAbaddonoffire ✭✭✭
    interestingly enough since i took a break a couple months ago my ping went down to below 20.
  • LesbianViLesbianVi ✭✭✭✭✭
    Abaddonoffire wrote: »
    interestingly enough since i took a break a couple months ago my ping went down to below 20.

    Do you have a basement for a Popo to move in? I will be doing the cleaning and stuff like a good Popo slave.
  • SableFelineSableFeline ✭
    I made a cmd script that will monitor trace route ping to diag.enmasse.com every minute. It resolved nodes' url every 5 minute.
    You can see/download the script here: https://pastebin.com/M0z3kYUN
    After downloading, change the file name from TERAtraceroute.cmd.txt to TERAtraceroute.cmd and you should be able to run the script

    I just leave the script running and copy the log when I see persistent high ping and send to [email protected]

    So far, I have gathered 5 logs that indicates persistent (15-60 minutes) high ping jump at cr1-te-0-8-0-0.washington.savvis.net [204.70.207.121] node.
  • IIBADIIIIBADII ✭
    I'm on the southside of Chicago and never have had any issues with ping in this game. What ISP do you have?
Sign In or Register to comment.