Re: Nhl 18 lag and delay

[Removed unkind comment - CM]

Your game is the problem. Good game, when working. Unfortunately, past 3months has been laggy. Everything else is working perfectly...except for NHL18. 

And still, these incompetent mokeymaking companies can be so arrogant to paying customers. 

For me, my Connection works perfectly From Finland all the way to Germany. Guess what? Eashl does not, even though ping is static 29ms. I mean from inside of the game. Otherwise it's ~12ms. No probs ott small probs with versus and hut but they are P2P.

But when you have to use EA's piece of art servers, problems start. 

It's been proven from ISP and myself that inet works perfectly, with PUBLIC IP!! All to way to Frankfurt. 

Be men, take responsobility. 

Way to go EA, nice job.

@Yllsten If you cannot post without insulting others then please refrain from doing so, there is no need to insult or post unkind comments about others. 

 Have you ran a UO trace to check how your data is being sent? 

You're obviously not even serious, Darko.. If I have also been playing with laggy and dealayed connection for over 3 months IT'S JUST NOT PLAYERS FAULT. Do you really understand it or do you just have to try to protect EA? EA's servers spoils nearly every game and here you are just trying to ask about UO trace which has never helped anyone here..

I'm not insulting anyone.

I'm blaming EA for bad work.

Ok, maybe neandertals was out of topic.

The uotrace. What do you think it actually tells you? And what it is telling me other than i allready know with traceroute and ping with 1000bytes packets?

Give me the IP's of your European servers, i put here the results. My connection is stable up to Frankfurt, which is last (7th) node answering to traceroute and i been pingin every step to that point, with steady results, without packet loss. That now tells something, right?

You don't tell the IP, because you don't want to people know that actually, fail is in Your server.

And Darko, 

i understand that you are not able to say it out loud. 

I'm not blaming you, i blame your employer..

And the uotrace. 

Are you saying, that my gaming is really coming from your mainserver? Really? Because the ip is under ANIA's control. Other said, it's based on US Soil. Why would i make the uotrace to US?

What diffence does it make, when i'm playing in northern Europe. And you should have servers in Europe? Well, do ya?

Yes or no? 

I'm doing pathping as we speak. But i can already tell you, it is NOT my ISP who doing something wrong. 

I see 6 first nodes, nothing behind them. Only " stars". And the last one i see, is 

4.69.163.126, which is frankfurt1.level3.net. Registered to US. In every node before that i have ping in order, jitter in order. So it is not the connection by MY ISP. 

I have my ways to see also your five last servers, which of three first Ip starts with 159...

So why i'm taking these measures to test a connection to US? I should not be connected to US. Instead, i should test my connection to European servers, if you really have servers here as EA claims.

2  91-154-14-2.elisa-laajakaista.fi (91.154.14.2)  12.568 ms'  12.574 ms  11.985 ms

3  193.229.29.205 (193.229.29.205)  12.471 ms  12.976 ms  13.641 ms

4  213.192.186.77 (213.192.186.77)  12.265 ms  12.571 ms  12.749 ms

5  213.192.184.74 (213.192.184.74)  17.718 ms  17.919 ms  17.890 ms

6  212.73.250.181 (212.73.250.181)  18.341 ms  18.528 ms  18.138 ms

7  ae-2-3212.msr1.frankfurt1.level3.net (4.69.163.126)  41.623 ms  41.713 ms  41.804 ms

8  * * *

9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  *traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

* *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *

31  * * *

32  * * *

33  * * *

34  * * *

35  * * *

36  * *traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

*

37  * * *

38  * * *

39  * * *

40  * * *

41  * * *

42  * * *

43  * * *

44  * * *

45  * * *

46  * * *

47  * *traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

*

48  * * *

49  * * *

50  * * *

51  * * *

52  * * *

53  * * *

54  * * *

55  * * *

56  * * *

57  * * *

58  * * *

59  * * *

60  * * *

61  * * *

62  * * *

63  * * *

64  * * *

I left first hop out, because it's my own router. Ping 0.326ms

I did the traceroute behing my router, but i have bridged line to my PS. Does not change anything.

And pathping is calculated from the bridge:

traceroute -S -q 30  easo.ea.com

traceroute to easo.ea.com (159.153.234.54), 64 hops max, 52 byte packets

1  91-154-14-2 (91.154.14.2)  12.682 ms  12.008 ms  11.988 ms  12.273 ms  11.733 ms  11.933 ms  12.010 ms  11.819 ms  12.273 ms  12.204 ms  12.482 ms  12.203 ms  12.147 ms  11.850 ms  12.720 ms  12.657 ms  12.303 ms  11.941 ms  12.935 ms  11.830 ms  12.390 ms  11.943 ms  12.376 ms  11.967 ms  12.257 ms  11.756 ms  11.767 ms  12.159 ms  11.934 ms  12.280 ms (0% loss)

2  193.229.29.205 (193.229.29.205)  13.350 ms  13.189 ms  13.786 ms  12.422 ms  12.802 ms  12.660 ms  13.451 ms  12.516 ms  12.731 ms  12.699 ms  12.966 ms  12.981 ms  12.472 ms  12.880 ms  12.770 ms  12.665 ms  12.457 ms  13.345 ms  12.360 ms  12.757 ms  12.806 ms  13.265 ms  15.561 ms  16.244 ms  13.393 ms  13.092 ms  13.045 ms  13.162 ms  12.769 ms  12.889 ms (0% loss)

3  213.192.186.77 (213.192.186.77)  13.501 ms  12.175 ms  12.414 ms  12.628 ms  12.507 ms  12.149 ms  12.084 ms  12.179 ms  12.457 ms  11.999 ms  12.030 ms  12.327 ms  12.448 ms  21.128 ms  12.690 ms  12.614 ms  12.491 ms  12.443 ms  15.221 ms  12.383 ms  13.071 ms  12.175 ms  12.175 ms  12.822 ms  12.690 ms  12.199 ms  12.251 ms  12.616 ms  12.525 ms  12.199 ms (0% loss)

4  213.192.184.74 (213.192.184.74)  48.067 ms  17.533 ms  17.457 ms  17.724 ms  17.856 ms  17.706 ms  17.681 ms  17.837 ms  17.612 ms  17.860 ms  17.826 ms  17.694 ms  18.966 ms  17.877 ms  18.162 ms  17.674 ms  17.642 ms  17.635 ms  17.649 ms  22.448 ms  17.728 ms  17.630 ms  17.792 ms  17.479 ms  17.694 ms  17.514 ms  17.710 ms  17.471 ms  18.150 ms  18.234 ms (0% loss)

5  212.73.250.181 (212.73.250.181)  17.957 ms  18.778 ms  18.095 ms  18.464 ms  18.539 ms  18.360 ms  18.508 ms  18.220 ms  18.463 ms  18.853 ms  18.026 ms  18.010 ms  18.488 ms  17.940 ms  18.405 ms  18.030 ms  18.471 ms  18.362 ms  18.394 ms  17.915 ms  18.194 ms  18.594 ms  18.023 ms  18.637 ms  18.016 ms  18.454 ms  17.730 ms  17.983 ms  18.131 ms  18.384 ms (0% loss)

6  ae-2-3212.msr1.frankfurt1.level3.net (4.69.163.126)  42.474 ms  41.616 ms  41.939 ms  41.523 ms  41.378 ms  41.438 ms  41.361 ms  41.630 ms  42.783 ms  41.552 ms  41.396 ms  41.494 ms  42.007 ms  41.630 ms  41.560 ms  42.586 ms  41.765 ms  41.686 ms  41.877 ms  42.134 ms  42.902 ms  43.275 ms  41.945 ms  41.421 ms  42.078 ms  42.572 ms  41.499 ms  41.233 ms  42.277 ms  41.925 ms (0% loss)

7  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

8  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

9  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

10  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

11  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

12  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

13  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

14  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

15  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

16  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

17  * * * * * *traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

*traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

* * * * * * * * * * * * * * * * * * * * * * * (100% loss)

18  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

19  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

20  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

21  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

22  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

23  * * * * * * * * * *traceroute: sendto: Network is down

traceroute: wrote easo.ea.com 52 chars, ret=-1

*traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

* * * * * * * * * * * * * * * * * * * (100% loss)

24  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

25  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

26  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

27  * * * * * * * * * * * * * * * * * * * * * * * * * *traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

* * * * (100% loss)

28  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

29  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

30  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

31  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

32  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

33  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

34  * * * * * * * * * * * * * * * *traceroute: sendto: Network is down

traceroute: wrote easo.ea.com 52 chars, ret=-1

*traceroute: sendto: Can't assign requested address

traceroute: wrote easo.ea.com 52 chars, ret=-1

* * * * * * * * * * * * * (100% loss)

35  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

36  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

37  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

38  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

39  * * * * * * * * * *^C

It's saying "Network is down because i was clicking the mousepad. 

Can you please explain me why I do this to your server in US?

Hi,

I'm writing from Finland, Europe.

For weeks, 6-8weeks, i've been suffering lag in eashl clubgames.

HUT, 1vs1, eashl randoms, no probs, or atleast small one´s. 

But clubgames, *. Ps ping shows 29ms, steady line. But it feels like 1000-1500ms, laggy as h..l. Running in a swamp..

My team mates don't have this problem, regardless are the playing through wifi, 4G, fiber. Only me. I'm not a captain either..


I'm playing with Lan connection (VDSL), NAT1 (public IP, bridge) , dualshock connected with usb cable. And have been rebooting, ping, tracerouting, you name it, i've pretty much done it. And ten's of times...

Google dns europe gives me steady 18ms, my own ISP 12ms, allways. So it's not ISP baised failure.

I got guidance to trace route easo.ea.com, which i did. But been European, i saw Frankfurts jump as last, after that no node jumps visible. My ping from FIN to Frankfurt GER, took steady 41ms. I was measuring with 1000bytes packet for 30min.. no probs.

Have been talking with my operator, that end is check. No probs. Problems start after GER  (frankfurt) somewhere.

What is left to do?

Can you solve this somehow? I'm starting to be innoyed about this *!

My ps4 is about one year old, ASUS DSL ROUTER 4 months old. Tried another router, tried switch with dsl bridge for pros, nothing helps.

@Yllsten Please refrain from using language.

Can I ask why you are testing to the US servers if you live in Europe? 

Because your customer service told me to do so. I got mail for your "Specialist"..

I asked why, i'm living in Europe, they did not answer.

Guess why i'm a bit frustrated??!!

So do You have any better ways to solve this out, because that was their idea, which i was fighting against heavily. 

@Yllsten In the email you were sent a link to the connection troubleshooting steps, if you look under Run a UOTrace you will see that it lists a number of IP addresses for you to use depending on your location. If you read the steps sent you will see where it lists the IP to use if you live in Europe. 

You are right...So i do it again

new ones

traceroute 159.153.72.252

traceroute to 159.153.72.252 (159.153.72.252), 64 hops max, 52 byte packets

1  91-154-***.** (91.154.***.**)  12.718 ms  11.938 ms  12.280 ms

2  193.229.29.205 (193.229.29.205)  13.587 ms  12.477 ms  12.396 ms

3  213.192.186.77 (213.192.186.77)  12.663 ms  12.150 ms  13.131 ms

4  213.192.184.65 (213.192.184.65)  18.470 ms  18.436 ms  18.417 ms

5  212.73.250.181 (212.73.250.181)  18.533 ms  18.680 ms  18.667 ms

6  ae-1-8.bar1.dublin1.level3.net (4.69.153.230)  64.304 ms  64.889 ms  65.215 ms

7  213.242.106.234 (213.242.106.234)  64.635 ms  65.493 ms  65.497 ms

8  * * *

9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *

31  * * *

32  * * *

33  * * *

34  * * *

35  * * *

36  * * *

37  * * *

38  * * *

39  * * *

40  * * *

41  * * *

42  * * *

43  * * *

44  * * *

45  * * *

46  * * *

47  * * *

48  * * *

49  * * *

50  * * *

51  * * *

52  * * *

53  * * *

54  * * *

55  * * *

56  * * *

57  * * *

58  * * *

59  * * *

60  * * *

61  * * *

62  * * *

63  * * *

64  * * *

pathping

traceroute -S -q 30  159.153.72.252

traceroute to 159.153.72.252 (159.153.72.252), 64 hops max, 52 byte packets

1  91-154-***.** (91.154.***.**)  13.466 ms  12.478 ms  12.060 ms  12.416 ms  11.939 ms  12.151 ms  12.328 ms  12.172 ms  12.131 ms  12.670 ms  12.882 ms  13.167 ms  12.478 ms  12.715 ms  12.390 ms  12.750 ms  12.197 ms  12.090 ms  11.937 ms  13.002 ms  12.065 ms  12.129 ms  12.663 ms  12.459 ms  12.032 ms  12.479 ms  12.400 ms  12.489 ms  12.395 ms  12.254 ms (0% loss)

2  193.229.29.205 (193.229.29.205)  12.733 ms  12.632 ms  12.495 ms  14.632 ms  12.889 ms  12.836 ms  12.586 ms  12.990 ms  12.751 ms  12.769 ms  12.515 ms  12.853 ms  14.127 ms  12.545 ms  12.967 ms  14.332 ms  13.164 ms  12.696 ms  12.755 ms  12.167 ms  12.290 ms  12.779 ms  12.368 ms  12.583 ms  12.356 ms  12.212 ms  12.588 ms  12.673 ms  12.268 ms  12.666 ms (0% loss)

3  213.192.186.77 (213.192.186.77)  12.444 ms  12.559 ms  21.506 ms  12.232 ms  12.277 ms  12.317 ms  12.081 ms  12.162 ms  12.349 ms  12.127 ms  12.118 ms  12.285 ms  12.223 ms  12.297 ms  12.233 ms  12.396 ms  12.428 ms  12.430 ms  12.010 ms  12.159 ms  12.493 ms  12.222 ms  12.451 ms  12.364 ms  12.553 ms  12.598 ms  12.117 ms  11.983 ms  12.143 ms  12.529 ms (0% loss)

4  213.192.184.65 (213.192.184.65)  18.620 ms  18.274 ms  18.445 ms  18.968 ms  18.197 ms  18.235 ms  19.425 ms  18.276 ms  18.548 ms  21.513 ms  18.179 ms  18.856 ms  18.831 ms  18.183 ms  18.548 ms  18.102 ms  18.583 ms  18.607 ms  18.437 ms  21.204 ms  18.513 ms  18.190 ms  18.219 ms  22.413 ms  18.421 ms  18.045 ms  19.651 ms  18.321 ms  18.014 ms  18.517 ms (0% loss)

5  212.73.250.181 (212.73.250.181)  18.484 ms  18.810 ms  18.479 ms  18.935 ms  18.818 ms  18.257 ms  18.213 ms  18.298 ms  18.401 ms  18.722 ms  18.437 ms  19.057 ms  18.652 ms  18.436 ms  18.231 ms  18.283 ms  18.444 ms  18.570 ms  19.045 ms  18.734 ms  18.436 ms  18.493 ms  18.531 ms  19.832 ms  19.363 ms  18.668 ms  18.515 ms  18.537 ms  18.897 ms  18.509 ms (0% loss)

6  ae-1-8.bar1.dublin1.level3.net (4.69.153.230)  64.757 ms  64.848 ms  64.819 ms  64.694 ms  65.440 ms  65.069 ms  64.432 ms  64.296 ms  64.485 ms  64.401 ms  64.483 ms  64.170 ms  64.259 ms  64.478 ms  64.567 ms  64.394 ms  64.431 ms  64.298 ms  64.645 ms  64.434 ms  67.205 ms  64.383 ms  64.485 ms  64.274 ms  64.570 ms  64.291 ms  64.799 ms  64.481 ms  64.365 ms  71.244 ms (0% loss)

7  213.242.106.234 (213.242.106.234)  65.478 ms  65.121 ms  65.191 ms  64.915 ms  65.284 ms  65.158 ms  65.013 ms  65.611 ms  65.046 ms  65.716 ms  64.737 ms  66.388 ms  65.212 ms  65.660 ms  65.146 ms  65.762 ms  65.077 ms  65.155 ms  65.430 ms  65.436 ms  65.174 ms  65.179 ms  64.786 ms  64.975 ms  65.698 ms  69.883 ms  65.271 ms  66.837 ms  65.145 ms  65.200 ms (0% loss)

8  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

9  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

10  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

11  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

12  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

13  * * * * * * * * * * * * * * * *traceroute: sendto: Can't assign requested address

traceroute: wrote 159.153.72.252 52 chars, ret=-1

* * * * * * * * * * * * * * (100% loss)

14  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

15  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * (100% loss)

16  * * *^C

I vanishded the two last octets of my ip..

Any thoughts?

Anything else i can do?

The hop between nodes 5 and 6 seems to be too big...

@Yllsten That is something you would need to speak with your ISP in relation to as we have no control over how they route your data to the game servers.

Yeah,

i see that now, when i got the right server IP. Thanks for help and sorry for my language and bad attitude. 

Thing is, it worked just fine, and then it stopped working. I think now they propably made some changes for routing table which is now causing this, my server ping most likely increased at the same.

Can you answer what the ping stands for in EASHL game when it shows 29ms. Is it between the players

within the team? Because it is not the connection to server. 

How is it build? 

That has been the big question mark to me

Because would i knew that, i could have asked the right questions from my ISP. 

If ping shows green and under 30 steady line and it's NOT the server ping,  i've been blaiming the wrong instance. But then again, i don't know what my teammates are using as a data line. So what i'm thinking is:

If my teammate is using mobiledata, which sends data to server and server gathers and sends that so called teamdata to both teams...and if my team mates data has much of jitter, so could it be, that my normal 65ms ping to gameserver cannot even up he's jittered data to me. 

 Because if i'm having 65ms ping, and he has much of jitter, i'm going close to magical 100ms border line. And then it's just not working? 

Am i even close?

Can you explain how these connections work? Like in a nut shell?

No answer. 

Surprise.

@YllstenIf you do not tag me in the reply then it is very easy to overlook. 

Have you spoken with your ISP in regards to the issues you have been having?

@EA_Darko

Yes, 

they said they cannot take steps to node's which are not owned by them, (IP 4.69....), registered US. 

It seems to be like problems starts, if someone in our teem has poor contact via mobiledata...

So that is the reason i would like to understand why it happens when it happens. And it would be helpfull, if you just would tell me, how it is build, who is sending data to who, is someone host etc..when the server is doing something? 

For me it looks like your server does not handle lag in a good way, if people are playing with un-stabile connection. But why they are not suffering, I am, even though i have stabile landline?

only in club mode

@EA_Darko

So i don't think anymore this problem would be something which would be my ISP's fault. 

The only mode what is doing this is eashl club mode. Sometimes on HUT and versus too, but they are p2p, so opponents connection plays big role.

And not in any other game than EA😕. 

So, your company should do it better. Simple as that. I hope, i don't suffer this in nhl19, otherwise i just move to other games..

It's your ISP job to get your data from your router to the game servers, they control how it is routed and sent and if it hits a troubled hop before it reaches the game servers then is something your ISP will need to fix. 

@EA_Darko

Yes, 

but is lag because of my sending or receiving? 

and most games, ping 65ms is good result, why it is not in EA's game? 

And by 65ms i mean connection From Finland to Ireland to your server.

And why 65ms feels like 1000ms?

like running in the swamp...

And during the game, my ping shows 29ms...what that stands for?

So third time,

can you walk me through how this teamplay is build? Is someone hosting,  or are we all separately sending/receiving data to your server...? Or mixed both? 

in a nut shell..