Lag and High ping after update (Broken Prision)

Deathxx7 · January 2017

counterpoint wrote: »

Deathxx7 wrote: »

Well, then a simple question, because on Tuesday morning doing the rally I was with the ping to 160 - 170 and the afternoon after the update my ping has not dropped so far from 220 - 230? Route? Assurance? Why would the route change in a matter of hours?

Routes can change all the time because they're deterministic (they try to remap themselves around problems), and can be influenced by all sorts of issues along the path. It can easily happen multiple times during a given day. By adding one new dungeon on the server, they didn't fundamentally rewrite the netcode so that it would add +60 to your median ping times. That is not the most likely explanation for the problem.

Sylviette wrote: »

@counterpoint Do you still playing the game, or just log onto the forum to white knight EME all day everyday ?
You think everyone who's complaining on the forum are people who play alone without guild or friends and they only complain because the issue affected them and not everyone they played with ? When a whole guild of roughly 30 ppl online at all time complain about the them problem, at the same time, yes, you can assume it's not because of our individual connection, and no, not every single one of us would bother to get on the forum to report it. Do you need signed document for each and everyone of us to prove that this is a problem to more than 1 person too ?

Traceroute cannot show the issue with ping spikes, unless you constantly spam traceroute to the server and it happens to caught on right when there's a ping spike. It's impossible to miss if you actually play the game and not just log in and afk.

Yes I still play the game. There are different issues going on here, which is the whole point. You are talking about ping spikes. This thread is talking about a global increase in median ping times. They are not the same problem at all, nor do they have the same root cause. The problem is that everyone lumps every single problem they have into this giant bucket of "this game is [filtered]" when there are multiple unrelated issues caused by different things, and this doesn't help at all in terms of actually diagnosing or troubleshooting problems. Of course most people don't want to actually know what the problem is, they just want EME to "stop being [filtered]" and wave some magic wand to fix it all.

SwollenPopo wrote: »

Tempest Reach is suffering badly from lag spikes and freezes right now and traceroute to diag,enmasse.com doesn't show anything.

I am on TR right now and not seeing any spikes. What part of the world are you in, or is this in an instance? Or maybe it's already stopped by now?

Well, I'm a software developer my friend, I know very well what can happen to updates and how they can affect the performance of an application and also that "bugs" created in remote application locations can affect the connection or the response From the server to a particular action. The problem is not in my sending of packages but in the receipt of them, which causes a great delay and increase of ping, Soon more night I will put here the LOG of EMEDiag.exe so that they can see that there my maximum pinga consists As described here 160-170. So, my dear friend, do not come to discuss code and development with anyone who knows what you're talking about, because I would not complain if it was something temporary. Well, answering the other question, if it were the routes, how did you even say they change constantly, I would not stay a week or more with the correct ping? Importantly, my connection is linked directly to a main backbone, making the route the best possible, unchanged, since I do not have to go through numerous access providers.

Sylviette · January 2017

counterpoint wrote: »

Sylviette wrote: »

When there're multiple issue got reported for months and the only reply EME has was "we're still looking into it" or just has no reply at all, noone can criticize people for lumping everything into 1 giant bucket of "this game is [filtered]" because who would bother to list "we have high ping issue, spike issue, bg not popping issue, not enough ppl in this or that server issue, dungeons not rewarding enough issue, CU being exploit issue,...." ?

I can't blame you for your feelings, but bring up unrelated baggage in a thread about a specific issue solves nothing. The only possible hope of solving any of these issues is to stay objective and to treat each issue one by one.

So, for the specific issue of people who have seen their median ping increase by ~60 ms recently, it would be helpful to post the traceroute. This is what I recommend as important needed data for this specific issue, not the other ones.

I can't blame you for your white knight dedication either, but regarding 2 connection issues as unrelated baggage while they're very likely to relate to each other is straight out counter productive. You can't cure a flu by treating its symptoms one by one like using pain killer for headache, cold pad for muscle aches, energy drink for fatigue,... you have to take all the symptoms into consideration to come to the conclusion: it's a flu, go get a shot. Simple enough ?

Deathxx7 · January 2017

As promised, here are the latency tests with the TERA and ZMR games, with the two games being located on different servers. As I had said since the beginning of the topic, my ping was 160 - 170, what happens in the ZMR that is of ENMASSE also, but in TERA it jumped to 210 - 220 in the last update, thanks to the server savvis that for what I was analyzing and searching Not as good as they say on the site. Well, how can you compare Savvis is rubbish and AshBurn (ZMR servers) are absurdly better. Perhaps it is a new analysis to see how much this Saviis server has declined and is damaging the TERA players. Who knows also the ENMASSE of some glance in this publication, because until now and it is not serving at all this forum.

Detail that for the server of the TERA we have 14 jumps and for the server of the ZMR we have 23 jumps, 9 jumps more and even so the ping is 40 lower.

=================================
=== PATHPING TERA
=================================

Rastreando a rota para diag.enmasse.com [208.67.49.180]
com no m ximo 30 saltos:
0 DESKTOP-S32MLLC [192.168.1.107]
1 192.168.1.1
2 190-15-43-1.net11.com.br [190.15.43.1]
3 177.137.12.30.net11.com.br [177.137.12.30]
4 100.64.5.1
5 81.33.186.200.sta.impsat.net.br [200.186.33.81]
6 ae7-40G.ar5.JFK1.gblx.net.ae7-40G.ar5.JFK1.gblx.net [67.17.67.46]
7 jfk-brdr-04.inet.qwest.net [63.235.40.57]
8 nyc2-brdr-01.inet.qwest.net [205.171.134.54]
9 63.146.26.158
10 cr1-xe-1-0-0.jfk2.savvis.net [206.28.99.145]
11 cr1-te-0-1-0-1.chd.savvis.net [206.28.100.233]
12 hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
13 64.37.205.6
14 208.67.49.180

Calculando estat¡sticas para 21 segundos...
Origem aqui Este n¢/V¡nculo
Perdido/Enviado Perdido/Enviado
Salto RTT = Pct = Pct Endere‡o
0 DESKTOP-S32MLLC [192.168.1.107]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 190-15-43-1.net11.com.br [190.15.43.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 177.137.12.30.net11.com.br [177.137.12.30]
0/ 100 = 0% |
4 12ms 0/ 100 = 0% 0/ 100 = 0% 100.64.5.1
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% 81.33.186.200.sta.impsat.net.br [200.186.33.81]
0/ 100 = 0% |
6 189ms 0/ 100 = 0% 0/ 100 = 0% ae7-40G.ar5.JFK1.gblx.net.ae7-40G.ar5.JFK1.gblx.net [67.17.67.46]
0/ 100 = 0% |
7 199ms 0/ 100 = 0% 0/ 100 = 0% jfk-brdr-04.inet.qwest.net [63.235.40.57]
0/ 100 = 0% |
8 191ms 0/ 100 = 0% 0/ 100 = 0% nyc2-brdr-01.inet.qwest.net [205.171.134.54]
0/ 100 = 0% |
9 191ms 0/ 100 = 0% 0/ 100 = 0% 63.146.26.158
0/ 100 = 0% |
10 195ms 0/ 100 = 0% 0/ 100 = 0% cr1-xe-1-0-0.jfk2.savvis.net [206.28.99.145]
0/ 100 = 0% |
11 217ms 0/ 100 = 0% 0/ 100 = 0% cr1-te-0-1-0-1.chd.savvis.net [206.28.100.233]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% hr3-xe-8-0-0.elkgrovech3.savvis.net [204.70.198.73]
0/ 100 = 0% |
13 212ms 0/ 100 = 0% 0/ 100 = 0% 64.37.205.6
1/ 100 = 1% |
14 211ms 1/ 100 = 1% 0/ 100 = 0% 208.67.49.180

Rastreamento conclu¡do.

=================================
=== PATHPING ZMR
=================================

Rastreando a rota para diag1.wdc1.enmasse.com [207.244.81.152]
com no m ximo 30 saltos:
0 DESKTOP-S32MLLC [192.168.1.107]
1 192.168.1.1
2 190-15-43-1.net11.com.br [190.15.43.1]
3 177.137.12.30.net11.com.br [177.137.12.30]
4 100.64.5.1
5 189-10-194-17.paebv300.ipd.brasiltelecom.net.br [189.10.194.17]
6 201.10.246.94
7 201.10.227.135
8 100.120.18.67
9 177.2.219.18
10 * 100.120.16.83
11 100.122.18.56
12 100.122.17.167
13 ix-xe-3-3-3-0.tcore1.NTO-New-York.as6453.net [63.243.128.81]
14 if-ae-7-2.tcore1.N0V-New-York.as6453.net [63.243.128.26]
15 if-ae-5-2.thar1.NJY-Newark.as6453.net [66.198.70.81]
16 if-ae-1-3.thar2.NJY-Newark.as6453.net [216.6.57.2]
17 if-ae-11-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.137]
18 if-ae-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
19 if-ae-32-2.tcore1.VN5-Manassas.as6453.net [66.198.155.22]
20 66.198.154.230
21 po-10.ce02.wdc-01.us.leaseweb.net [108.59.15.147]
22 er1.wdc1.enmasse.com [108.59.1.170]
23 diag1.wdc1.enmasse.com [207.244.81.152]

Calculando estat¡sticas para 34 segundos...
Origem aqui Este n¢/V¡nculo
Perdido/Enviado Perdido/Enviado
Salto RTT = Pct = Pct Endere‡o
0 DESKTOP-S32MLLC [192.168.1.107]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 5ms 0/ 100 = 0% 0/ 100 = 0% 190-15-43-1.net11.com.br [190.15.43.1]
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% 177.137.12.30.net11.com.br [177.137.12.30]
0/ 100 = 0% |
4 7ms 0/ 100 = 0% 0/ 100 = 0% 100.64.5.1
0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% 189-10-194-17.paebv300.ipd.brasiltelecom.net.br [189.10.194.17]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 201.10.246.94
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 201.10.227.135
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 100.120.18.67
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% 177.2.219.18
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% 100.120.16.83
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% 100.122.18.56
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% 100.122.17.167
0/ 100 = 0% |
13 170ms 20/ 100 = 20% 20/ 100 = 20% ix-xe-3-3-3-0.tcore1.NTO-New-York.as6453.net [63.243.128.81]
0/ 100 = 0% |
14 176ms 0/ 100 = 0% 0/ 100 = 0% if-ae-7-2.tcore1.N0V-New-York.as6453.net [63.243.128.26]
0/ 100 = 0% |
15 176ms 0/ 100 = 0% 0/ 100 = 0% if-ae-5-2.thar1.NJY-Newark.as6453.net [66.198.70.81]
0/ 100 = 0% |
16 175ms 6/ 100 = 6% 6/ 100 = 6% if-ae-1-3.thar2.NJY-Newark.as6453.net [216.6.57.2]
0/ 100 = 0% |
17 178ms 26/ 100 = 26% 26/ 100 = 26% if-ae-11-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.137]
0/ 100 = 0% |
18 175ms 0/ 100 = 0% 0/ 100 = 0% if-ae-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2]
0/ 100 = 0% |
19 184ms 0/ 100 = 0% 0/ 100 = 0% if-ae-32-2.tcore1.VN5-Manassas.as6453.net [66.198.155.22]
0/ 100 = 0% |
20 --- 100/ 100 =100% 100/ 100 =100% 66.198.154.230
0/ 100 = 0% |
21 162ms 0/ 100 = 0% 0/ 100 = 0% po-10.ce02.wdc-01.us.leaseweb.net [108.59.15.147]
0/ 100 = 0% |
22 173ms 48/ 100 = 48% 48/ 100 = 48% er1.wdc1.enmasse.com [108.59.1.170]
0/ 100 = 0% |
23 169ms 0/ 100 = 0% 0/ 100 = 0% diag1.wdc1.enmasse.com [207.244.81.152]

Rastreamento conclu¡do.

counterpoint · January 2017

So... it's an issue caused by the Savvis backbone switch... exactly as I said all along.

Sylviette wrote: »

I can't blame you for your white knight dedication either, but regarding 2 connection issues as unrelated baggage while they're very likely to relate to each other is straight out counter productive.

They are not related at all.

Deathxx7 · January 2017

Ok, problem identified, because ENMASSE can not analyze this simple LOG that they themselves make available? It is ridiculous to have such a support where the guys do not have the least competence to solve the problem or charge the same from their service providers.

counterpoint · January 2017

Deathxx7 wrote: »

Ok, problem identified, because ENMASSE can not analyze this simple LOG that they themselves make available? It is ridiculous to have such a support where the guys do not have the least competence to solve the problem or charge the same from their service providers.

The reason for switching to Savvis was not because they were trying to increase your ping times in Brazil. A big reason is because Savvis was generally having lower ping times and less lag for U.S. players on Comcast (the biggest American ISP). So even if your ping went up, they would still probably make the choice they did given the circumstances.

You can try complaining to your ISP that your route from Brazil to Savvis in the U.S. is taking too many unnecessary hops, but I'm not sure if they're likely to care. International connections are not optimized for low ping times. And even if EME tries to elevate the issue to their U.S. hosting provider to elevate it to Savvis and then try to push it up the line, it's not much more likely to be successful. Other than switching backbones, EME is not able to do anything about the routing between your ISP and their ISP. Even if they change backbone providers for TERA to use the same one as ZMR, it's not guaranteed to be more reliable on the whole even if you have lower median ping times. (Ping time itself is only part of the story in the first place.)

If you want something you can actually do yourself for now, the best would be to try to find a VPN that gives you a better route into the U.S. I realize this should not be necessary, but routing problems are a constant reality when trying to play online games internationally.

Fleett · January 2017

And high ping strikes back! EME fix your sh**t. During a HH run too...

LancerJiva · January 2017

Fix your potato servers. My ping is normally 12-40 and now its staying at 100+, thats more then 5x my normal ping.

xvct · January 2017

LancerJiva wrote: »

Fix your potato servers. My ping is normally 12-40

jesus.

Imarabbitdawg · January 2017

Seems like servers been going through higher than usual ping around after the elite bar reset and lasts a few hours, pretty much can't play from 10pm-3am~ my time, at least outside of those time frames i've managed to find a solution for the ping and packet loss, sucks this is when friends get online and everybody is lagging and spiking like [filtered]

feazeshero · January 2017

Was on earlier today and things were normal as usual but now around 9 pm eastern time, my ping is around 100 ms higher than what I usually have. Something definitely changed.

Deathxx7 · January 2017

counterpoint wrote: »

Deathxx7 wrote: »

Ok, problem identified, because ENMASSE can not analyze this simple LOG that they themselves make available? It is ridiculous to have such a support where the guys do not have the least competence to solve the problem or charge the same from their service providers.

The reason for switching to Savvis was not because they were trying to increase your ping times in Brazil. A big reason is because Savvis was generally having lower ping times and less lag for U.S. players on Comcast (the biggest American ISP). So even if your ping went up, they would still probably make the choice they did given the circumstances.

You can try complaining to your ISP that your route from Brazil to Savvis in the U.S. is taking too many unnecessary hops, but I'm not sure if they're likely to care. International connections are not optimized for low ping times. And even if EME tries to elevate the issue to their U.S. hosting provider to elevate it to Savvis and then try to push it up the line, it's not much more likely to be successful. Other than switching backbones, EME is not able to do anything about the routing between your ISP and their ISP. Even if they change backbone providers for TERA to use the same one as ZMR, it's not guaranteed to be more reliable on the whole even if you have lower median ping times. (Ping time itself is only part of the story in the first place.)

If you want something you can actually do yourself for now, the best would be to try to find a VPN that gives you a better route into the U.S. I realize this should not be necessary, but routing problems are a constant reality when trying to play online games internationally.

It is, but the problem is not a route, this is already the best possible route, and the ping is this garbage, and for the log that I sent, the problem is not here and mainly is not outside Brazil, if not the servers of ZMR Would they have the same ping do not agree? I say that is the best route, because I tested with 5 pingers and none of them worked, they all kept the ping in the same proportion. The fact is that ENMASSE does not know how to choose a server. If they knew to analyze the minimum and keep all or 99% of the player with ping between 150 ~ 180 all would get to play, but no. It is better to leave an American with ping 10 and a Brazilian with ping 250 and to lose a player, being that a good part of the profits comes from countries that are not the USA. But this is it, a company that has no competence, if you want to look at the forum to find out what your players are putting on the agenda for discussion.

Endeva · January 2017

Deathxx7 wrote: »

counterpoint wrote: »

Deathxx7 wrote: »

Ok, problem identified, because ENMASSE can not analyze this simple LOG that they themselves make available? It is ridiculous to have such a support where the guys do not have the least competence to solve the problem or charge the same from their service providers.

The reason for switching to Savvis was not because they were trying to increase your ping times in Brazil. A big reason is because Savvis was generally having lower ping times and less lag for U.S. players on Comcast (the biggest American ISP). So even if your ping went up, they would still probably make the choice they did given the circumstances.

You can try complaining to your ISP that your route from Brazil to Savvis in the U.S. is taking too many unnecessary hops, but I'm not sure if they're likely to care. International connections are not optimized for low ping times. And even if EME tries to elevate the issue to their U.S. hosting provider to elevate it to Savvis and then try to push it up the line, it's not much more likely to be successful. Other than switching backbones, EME is not able to do anything about the routing between your ISP and their ISP. Even if they change backbone providers for TERA to use the same one as ZMR, it's not guaranteed to be more reliable on the whole even if you have lower median ping times. (Ping time itself is only part of the story in the first place.)

If you want something you can actually do yourself for now, the best would be to try to find a VPN that gives you a better route into the U.S. I realize this should not be necessary, but routing problems are a constant reality when trying to play online games internationally.

It is, but the problem is not a route, this is already the best possible route, and the ping is this garbage, and for the log that I sent, the problem is not here and mainly is not outside Brazil, if not the servers of ZMR Would they have the same ping do not agree? I say that is the best route, because I tested with 5 pingers and none of them worked, they all kept the ping in the same proportion. The fact is that ENMASSE does not know how to choose a server. If they knew to analyze the minimum and keep all or 99% of the player with ping between 150 ~ 180 all would get to play, but no. It is better to leave an American with ping 10 and a Brazilian with ping 250 and to lose a player, being that a good part of the profits comes from countries that are not the USA. But this is it, a company that has no competence, if you want to look at the forum to find out what your players are putting on the agenda for discussion.

If you want better ping, may be try moving into North America... You know... the place where En Masse has a license to publish Tera.

ElinUsagi · January 2017

Ginjitsu wrote: »

If you want better ping, may be try moving into North America... You know... the place where En Masse has a license to publish Tera.

Not only that but that maybe more than 90% of their income are from people living on North America.

So EME makes the right desicion trying to give better service for that +90% of wallets.

Deathxx7 · January 2017

Ginjitsu wrote: »

Deathxx7 wrote: »

counterpoint wrote: »

Deathxx7 wrote: »

Ok, problem identified, because ENMASSE can not analyze this simple LOG that they themselves make available? It is ridiculous to have such a support where the guys do not have the least competence to solve the problem or charge the same from their service providers.

The reason for switching to Savvis was not because they were trying to increase your ping times in Brazil. A big reason is because Savvis was generally having lower ping times and less lag for U.S. players on Comcast (the biggest American ISP). So even if your ping went up, they would still probably make the choice they did given the circumstances.

You can try complaining to your ISP that your route from Brazil to Savvis in the U.S. is taking too many unnecessary hops, but I'm not sure if they're likely to care. International connections are not optimized for low ping times. And even if EME tries to elevate the issue to their U.S. hosting provider to elevate it to Savvis and then try to push it up the line, it's not much more likely to be successful. Other than switching backbones, EME is not able to do anything about the routing between your ISP and their ISP. Even if they change backbone providers for TERA to use the same one as ZMR, it's not guaranteed to be more reliable on the whole even if you have lower median ping times. (Ping time itself is only part of the story in the first place.)

If you want something you can actually do yourself for now, the best would be to try to find a VPN that gives you a better route into the U.S. I realize this should not be necessary, but routing problems are a constant reality when trying to play online games internationally.

It is, but the problem is not a route, this is already the best possible route, and the ping is this garbage, and for the log that I sent, the problem is not here and mainly is not outside Brazil, if not the servers of ZMR Would they have the same ping do not agree? I say that is the best route, because I tested with 5 pingers and none of them worked, they all kept the ping in the same proportion. The fact is that ENMASSE does not know how to choose a server. If they knew to analyze the minimum and keep all or 99% of the player with ping between 150 ~ 180 all would get to play, but no. It is better to leave an American with ping 10 and a Brazilian with ping 250 and to lose a player, being that a good part of the profits comes from countries that are not the USA. But this is it, a company that has no competence, if you want to look at the forum to find out what your players are putting on the agenda for discussion.

If you want better ping, may be try moving into North America... You know... the place where En Masse has a license to publish Tera.

WTF? Face you should not have much notion of life itself, I will not even comment....

Lag and High ping after update (Broken Prision)

Comments