Menu
What's New
By:
Filters

High Packet Loss to MA Servers

i had similar problems several weeks ago with equip-lag and items locking out. except straight ping tests showed nothing wrong. sent a support case and got a responce similar to the above, use pingplotter and send a log. they claimed they didnt get it but thats by the bye, suddenly everything seem to clear up. no idea why. the ping plot was usless anyway, showed up spikes but brief and from inconsistant routers. one of the notable features was the equip-lag kicked in after 15-20 minutes activity, oddly even shifting if i spent 10 min in auction before hunting. im still half-convinced there was a bug somewhere.

now... conspiracy time... wasnt there an odd bug a while back that require one to make small shuffle move to regain ability to hit, which some believe was related to seeking out botter... i cant help but wonder if this is a simlar thing.
 
* deleted *
 
Last edited:
Everything has been working great for me... Until.. this VU :confused:

insane lag, etc.. did a ping and got lowest: 108 highest: 204

packet loss 39% (im on Telia) never had this problem before :(


[edit]not blaming this VU, but it started first time i logged in on new VU[/edit]


/Faith
 
Last edited:
aridash said:
i had similar problems several weeks ago with equip-lag and items locking out. except straight ping tests showed nothing wrong. sent a support case and got a responce similar to the above, use pingplotter and send a log. they claimed they didnt get it but thats by the bye, suddenly everything seem to clear up. no idea why. the ping plot was usless anyway, showed up spikes but brief and from inconsistant routers. one of the notable features was the equip-lag kicked in after 15-20 minutes activity, oddly even shifting if i spent 10 min in auction before hunting. im still half-convinced there was a bug somewhere.

now... conspiracy time... wasnt there an odd bug a while back that require one to make small shuffle move to regain ability to hit, which some believe was related to seeking out botter... i cant help but wonder if this is a simlar thing.
Click to expand...

Yes, I still rely on this. My hunting goes:
shoot shoot shoot shoot shuffle
shoot shoot shoot shoot shuffle
shoot shoot shoot shoot shuffle
shoot shoot shoot shoot shuffle
etc

If I don't it goes
hit hit miss miss miss miss hit hit hit hit hit hit miss miss miss miss hit hit hit hit hit hit miss miss miss miss.

I can only hope the cry2 update will fix this because it makes me sick to think about the cash I've wasted on their network incompetence.
 
e-lite said:
Well, doesnt look good. I am on labs2/bredband2 and I got this result:


Ping statistics for 64.125.26.77:
Packets: Sent = 97, Received = 22, Lost = 75 (77% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 86ms, Average = 84ms
Click to expand...

On a AT&T 3 Mb DSL line.

Ping statistics for 64.125.26.77:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 712ms, Average = 131ms
 
Last edited:
LLS said:
I have same ISP and have experienced the same things if not worse all summer. When it was really bad I was missing up to 50% very often, if not more(!) and ofc unable to switch fap/weapon in almost evry kill etc... At first I suspected MA servers, but soon noticed only I (most of the times at least) had these issues. I have tried evrything (with MA's great help) but nothing has helped the situation. This problem eventually went away by itself...

...only to be replaced since last 4 weeks with huge issues even staying connected. I get dc 2-20 times per hour (total loss of internet for around 30-60 sec) during the dark hours of the day, often a lot less during daylight hours. My ISP have admitted that they have a "cable-error" on their side, not that they are doing anything about it!!

Since last 2-3 days EU is very laggy again however (due to the recent VU I guess?)

Havent been able to hunt much for months now bec of all this, and it really SUCKS BIG TIME!!! :(
Click to expand...


I was away a few weeks this summer, maybe that was good, for several reasons, reading your post. I do get more connection lost nowaday but its not that often that it bothers me. Really sorry to hear about your situation =( It is interesting tho that this problem seems to be far more common among Telia users.

What makes it suck even more is that I bought a new kickass computer a month ago, I don't get to enjoy it this way..
 
After the last patch I started to have problems too. I also got Telia.
 
46% loss on 64.125.26.77

46% loss on 64.125.26.73 (the one support mentioned).

:rolleyes:
 
smoothee said:
Yes, I still rely on this. My hunting goes:
shoot shoot shoot shoot shuffle
shoot shoot shoot shoot shuffle
shoot shoot shoot shoot shuffle
shoot shoot shoot shoot shuffle
etc

If I don't it goes
hit hit miss miss miss miss hit hit hit hit hit hit miss miss miss miss hit hit hit hit hit hit miss miss miss miss.
Click to expand...

what does exactly "shuffle" mean, in terms of avatar actions???

because, the second paragraph in your post describes 100% what i've been getting during the last 1-2 years...:mad:
 
jdegre said:
what does exactly "shuffle" mean, in terms of avatar actions???

because, the second paragraph in your post describes 100% what i've been getting during the last 1-2 years...:mad:
Click to expand...

Just tap a movement key so you move slightly. Then, amazingly :rolleyes:, you will start to hit again.
 
jdegre said:
what does exactly "shuffle" mean, in terms of avatar actions???

because, the second paragraph in your post describes 100% what i've been getting during the last 1-2 years...:mad:
Click to expand...

To me it means press the move left or right key once which is what I've always had to do since I started playing or I just get miss after miss after miss once I've had one, so, as soon as I get a miss I 'shuffle' and then I can hit again. It's habit to me now and I don't even think about it.
 
From NE USA I'm getting 0% packet loss and just over 100ms latency.

Actually seems pretty good today.. I usually get 130ms or more.
 
Long ago many player did report a lag problem and ping problem with many paquet loss...
After many test , there was always a problem with telia node...
After that , MA did change host , and most player notice an improvement in the connection quality...
Maybe those that use telia should change isp...

But just a ping does not help , we need to trace , spot the bad node and report it to MA ...
 
Ping statistics for 64.125.26.73:
Packets: Sent = 1000, Received = 473, Lost = 527 (52% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 433ms, Average = 237ms

From SW USA, ISP Comcast

:rolleyes:
 
Ping statistics for 64.125.26.77:
Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 217ms, Average = 35ms

i took a look and it seemed bad but compared to you guys its not as bad.

but i am changing ISP's in the next 3 weeks so ill see if it makes a HUGE difference.

btw. im on a UK ISP
 
France:

Ping statistics for 64.125.26.77:
Packets: Sent = 50, Received =50, Lost = 0 (0%)
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 258ms, Average = 70ms
 
Have the same problem, but in waves - A ping and tracert went through cleanly.. Odd
 
Some statistics from the 3rd world (Brazil - ISP: Telefonica):

Estatísticas do Ping para 64.125.26.77:
Pacotes: Enviados = 100, Recebidos = 100, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 278ms, Máximo = 436ms, Média = 298ms
 
So it's either change ISPs, which will take 3 months, or do that "shuffle" thing? I don't really like any of the options
 
Mirandax said:
So it's either change ISPs, which will take 3 months, or do that "shuffle" thing? I don't really like any of the options
Click to expand...

Changing ISP's may not help.
 
0% loss here, 50 ping test

min 31ms, max 219ms
 
Mirandax said:
So it's either change ISPs, which will take 3 months, or do that "shuffle" thing? I don't really like any of the options
Click to expand...

or route your traffic through another isp that currently doesn't have issues.
 
Etopia said:
But just a ping does not help , we need to trace , spot the bad node and report it to MA ...
Click to expand...


the servers that I'm having issues with are the above.net ones
 
Ping-statistik för 64.125.26.77:
Paket: Skickade = 50, mottagna = 49, Förlorade = 1 (2 %),
Ungefärligt överföringstid i millisekunder:
Lägsta = 24 ms, Högsta = 224 ms, Medel = 36 ms


I had one loss out of 50 and havent had the problems u described, i am in sweden aswell but not using telia. maybe Telia is the root of EVUL :cdevil:

Pe@ce Gunz
 
50 pings said:
ping statistics for 64.125.26.77:
Packets: Sent = 50, received = 45, lost = 5 (10% loss),
approximate round trip times in milli-seconds:
Minimum = 53ms, maximum = 252ms, average = 76ms
Click to expand...

Again with 100 pings said:
Ping statistics for 64.125.26.77:
Packets: Sent = 100, Received = 95, Lost = 5 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 215ms, Average = 60ms
Click to expand...

and 100 pings for supports IP said:
Ping statistics for 64.125.26.73:
Packets: Sent = 100, Received = 96, Lost = 4 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 259ms, Average = 62ms
Click to expand...
Rarely have problems in game, but this doesn't look too good.

I'm in Denmark. ISP is TDC. :(
 
Last edited:
Code: 
C:\[I]deleted[/I]>[B]pathping 64.125.26.73[/B]

Tracing route to ten-gige-1-1.mpr1.ams2.nl.above.net [64.125.26.73]
over a maximum of 30 hops:
  0  [I]deleted[/I]
  1  [I]deleted[/I]
  2  [I]deleted[/I]
  3  [I]deleted[/I]
  4  [I]deleted[/I]
  5  [I]deleted[/I]
  6  xe-10-2-0.edge3.LosAngeles1.Level3.net [4.71.136.5]
  7  vlan99.csw4.LosAngeles1.Level3.net [4.68.20.254]
  8  ae-93-93.ebr3.LosAngeles1.Level3.net [4.69.137.45]
  9  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
 10  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
 11  ae-1-69.edge1.SanJose3.Level3.net [4.68.18.16]
 12  xe-1-3-0.er1.sjc7.us.above.net [64.125.13.241]
 13  ge-4-0-0-0.mpr1.sjc2.us.above.net [64.125.27.90]
 14  so-1-0-0.mpr1.lga5.above.net [64.125.26.230]
 15     *     so-1-0-0.mpr1.ams1.nl.above.net [64.125.27.186]
 16  ten-gige-1-1.mpr1.ams2.nl.above.net [64.125.26.73]

Computing statistics for 400 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0   [I]deleted[/I]
  1   [I]deleted[/I]
  2   [I]deleted[/I]
  3   [I]deleted[/I]
  4   [I]deleted[/I]
  5   [I]deleted[/I]
  6   39ms     0/ 100 =  0%     0/ 100 =  0%  xe-10-2-0.edge3.LosAngeles1.Level3.net [4.71.136.5]
                                0/ 100 =  0%   |
  7   43ms     0/ 100 =  0%     0/ 100 =  0%  vlan99.csw4.LosAngeles1.Level3.net [4.68.20.254]
                                0/ 100 =  0%   |
  8   44ms     0/ 100 =  0%     0/ 100 =  0%  ae-93-93.ebr3.LosAngeles1.Level3.net [4.69.137.45]
                                0/ 100 =  0%   |
  9   52ms     0/ 100 =  0%     0/ 100 =  0%  ae-2.ebr3.SanJose1.Level3.net [4.69.132.9]
                                0/ 100 =  0%   |
 10   52ms     1/ 100 =  1%     1/ 100 =  1%  ae-63-63.csw1.SanJose1.Level3.net [4.69.134.226]
                                0/ 100 =  0%   |
 11   53ms     0/ 100 =  0%     0/ 100 =  0%  ae-1-69.edge1.SanJose3.Level3.net [4.68.18.16]
                                0/ 100 =  0%   |
 12   50ms     0/ 100 =  0%     0/ 100 =  0%  xe-1-3-0.er1.sjc7.us.above.net [64.125.13.241]
                               30/ 100 = 30%   |
 13   47ms    40/ 100 = 40%    10/ 100 = 10%  ge-4-0-0-0.mpr1.sjc2.us.above.net [64.125.27.90]
                                0/ 100 =  0%   |
 14  122ms    30/ 100 = 30%     0/ 100 =  0%  so-1-0-0.mpr1.lga5.above.net [64.125.26.230]
                                0/ 100 =  0%   |
 15  236ms    30/ 100 = 30%     0/ 100 =  0%  so-1-0-0.mpr1.ams1.nl.above.net [64.125.27.186]
                               11/ 100 = 11%   |
 16  239ms    41/ 100 = 41%     0/ 100 =  0%  ten-gige-1-1.mpr1.ams2.nl.above.net [64.125.26.73]

Trace complete.
 
k, I've done a trace too:

pathping to 64.125.26.73 said:
Tracing route to ten-gige-1-1.mpr1.ams2.nl.above.net [64.125.26.73]
over a maximum of 30 hops:
...
6 pos4-0-0-10G.ldn2nxg1.ip.tele.dk [83.88.12.118]
7 ge3-0.pr1.lhr1.uk.above.net [195.66.224.76]
8 so-1-0-0.mpr2.ams5.nl.above.net [64.125.27.178]
9 so-0-0-0.mpr1.ams1.nl.above.net [64.125.26.45]
10 ten-gige-1-1.mpr1.ams2.nl.above.net [64.125.26.73]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
...
6 41ms 0/ 100 = 0% 0/ 100 = 0%
.............................0/ 100 = 0% |
7 55ms 0/ 100 = 0% 0/ 100 = 0%
.............................4/ 100 = 4% |
8 55ms 11/ 100 = 11% 7/ 100 = 7%
.............................0/ 100 = 0% |
9 58ms 4/ 100 = 4% 0/ 100 = 0%
.............................2/ 100 = 2% |
10 60ms 6/ 100 = 6% 0/ 100 = 0%
Click to expand...
Not entirely sure what this means.

I kinda expected only 1 node to lose packages? :scratch2:
 
Last edited:
1st Attemt:
2 time outs WTF??
Sent 4, recieved 1, lost 3 Not Good!
average 151ms

2nd attempt:
All 3 timed out all 4 packets lost, just depressing now you see why I have PK problems lol

3rd attempt:
1st time out next 3 pinged
Sent 4, recieved 3, lost 1 there may be hope...
 
You must log in or register to reply here.
Back
Top