High Packet Loss to MA Servers

Mirandax said:

I just pinged a server that is 18 hops away. 0 packet loss.

Click to expand...

Well, regardless of where the problem is, I would suggest sending a support ticket to both your ISP and Mindark. They are the ones that need to figure it out....make sure you give them the copies of the traces and pings...

My guess is it goes down something like this;

Mindark: Not our fault, talk to your ISP
ISP: Not our fault, the place your going to has a faulty ISP
Mindark: We have spoken with out ISP and can confirm it's not us
ISP: We are the ISP and can confirm it's not us
You: F--- this sh-t, I'm going to play *** until it gets fixed
Mindark: Yes, we've called your ISP and have found an issue between us and them. It is/was neither our fault, nor theirs. All is good in the hood.....

Running pingplotter shows severe link dropouts - starting @ above.net. Im connecting from Norway via bluecom/Catch (Telenor infrastructure).

100% packet loss for up to 20 secs, then down to 35% lasting a few secs - and back to 100% loss again. Going in circles...

Theres a problem somewhere, yeah lol

No need for me to log ingame until this gets fixed...

TELIA

From computer
Ping-statistik för 64.125.26.77:
Paket: Skickade = 50, mottagna = 26, Förlorade = 24 (48 %),
Ungefärligt överföringstid i millisekunder:
Lägsta = 116 ms, Högsta = 1972 ms, Medel = 202 ms

from Router
Pings sent: 34
Pings received: 22
Pings lost: 12 (35% loss)
Shortest ping time (in milliseconds): 111
Longest ping time (in milliseconds): 282
Average ping time (in milliseconds): 135

I had a LOT of issues, ran both ping and tracert, against gameserver
and also their website, and all issues are at above.net for me.
MAs website is loading sloooow for me atm...

Yupp this is stupid. I too have this issue a good portion of the time, 50% shots missed and the fap you can just forget about. What i dont get is the missed shots tho, since this is no game of moving targets and a complex hitbox system... its 99% of the time completly static standing still bang bang. If the server accepts the ammo use, it needs to accept them being fired and not out into open air.

Im not the worst but heres mine:

Ping statistics for 64.125.26.77:
Packets: Sent = 50, Received = 39, Lost = 11 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 318ms, Average = 155ms

The latency is unacceptable really, being in 2008 with a pretty advanced infrastructure.

Vinni said:

Running pingplotter shows severe link dropouts - starting @ above.net. Im connecting from Norway via bluecom/Catch (Telenor infrastructure).

100% packet loss for up to 20 secs, then down to 35% lasting a few secs - and back to 100% loss again. Going in circles...

Theres a problem somewhere, yeah lol

No need for me to log ingame until this gets fixed...

Click to expand...

I see the same thing.
I´m located in Finland, connected trough Sonera.
Sweating here I come.
Was mining on TI in Bear+5B and almost got killed by tiny fouls cus I couldnt get out fap or gun.


Ping statistics for 64.125.26.77:
Packets: Sent = 100, Received = 55, Lost = 45 (45% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 270ms, Average = 140ms

Ok, this is getting really annoying now.

I'm no tech guy, so I don't really understand what you are all talking about, but I just want to hunt! Someone, fix this!

A-Bomb said:

Yupp this is stupid. I too have this issue a good portion of the time, 50% shots missed and the fap you can just forget about. What i dont get is the missed shots tho, since this is no game of moving targets and a complex hitbox system... its 99% of the time completly static standing still bang bang. If the server accepts the ammo use, it needs to accept them being fired and not out into open air.

Click to expand...

Yes, and that's something i've brought up in the past. There's absolutely no excuse for a shot to be missed due to lag or lost packets. It can not fire, and not use ammo (sometimes you'll see this--the ammo count goes up again), but to deduct ammo and not register a hit is just shady, and that happens. That is MA's fault and no one else's. It would almost have to be a deliberate design decision...

Vinni said:

Running pingplotter shows severe link dropouts - starting @ above.net. Im connecting from Norway via bluecom/Catch (Telenor infrastructure).

Click to expand...

Yup, the first hop to above.net's routers is where most of my packets get lost.

i Cant even connect to Entropia website to send an support case :/

e-lite said:

In cmd prompt type: ping -n 50 64.125.26.77

50 pings should be enough to get a fair statistics.

Click to expand...

I'm trying this but the DOS window shuts as soon as it's finished pinging so I dont get a chance to see the last few lines.

I'm getting mostly 23-28 ms, with ~5% of 160-230 ms.

Redfrog said:

I'm trying this but the DOS window shuts as soon as it's finished pinging so I dont get a chance to see the last few lines.

I'm getting mostly 23-28 ms, with ~5% of 160-230 ms.

Click to expand...

In "run" only type "cmd" and youll get the DOS prompt up. In the DOS prompt you type the command. If you type "cmd ping ..." in run it will run the command and then end the DOS prompt. GL nub

* deleted *

A-Bomb said:

In "run" only type "cmd" and youll get the DOS prompt up. In the DOS prompt you type the command. If you type "cmd ping ..." in run it will run the command and then end the DOS prompt.

Click to expand...

Meh, I'm not used to using DOS with these new-fangled WIMP systems.

A-Bomb said:

GL nub

Click to expand...

Shup you!

Dion Red Strike said:

Well, regardless of where the problem is, I would suggest sending a support ticket to both your ISP and Mindark. They are the ones that need to figure it out....make sure you give them the copies of the traces and pings...

My guess is it goes down something like this;

Mindark: Not our fault, talk to your ISP
ISP: Not our fault, the place your going to has a faulty ISP
Mindark: We have spoken with out ISP and can confirm it's not us
ISP: We are the ISP and can confirm it's not us
You: F--- this sh-t, I'm going to play *** until it gets fixed
Mindark: Yes, we've called your ISP and have found an issue between us and them. It is/was neither our fault, nor theirs. All is good in the hood.....

Click to expand...

I did talk to Telia support when I first started having problems in May. Ofc they claimed nothing was wrong from their side. Forgive me but I'm not going to write to MA's support, that is a complete waste of time. The little faith I had in them I totally lost when i really needed their help with something important and they did absolutely nothing. The only thing they will say is that it's not their fault and that they will forward it to that *censor* design team.

That's the reason i posted here; to see how many others had problems and maybe maybe someone could help me out.

now i must admid that i do havehis problem aswell
but then in a really low scale.
imo it's nothing to worry about. but for the real ped spenders,
i can imagine that it sux bigtime.

i'll hope to see it fixed soon or later.

Btw as alot of others posted, i too run into trouble when i reach above.net. Before that its all good and fine.

Darkaner said:

Maybe we can pinpoint the troubled node if we match the loss with your tracert logs and with our own.

Click to expand...

ok, i'll bite.


Traceroute from Comhem-> rp.entropiauniverse.com
2 83.255.248.168 (83.255.248.168) 5.166 ms 6.102 ms 4.946 ms
3 vrr-pr-r-02-to-vrr-bb-r-01.comhem.se (83.255.252.214) 10.674 ms 11.897 ms 10.949 ms
4 64.209.107.209 (64.209.107.209) 8.898 ms 9.364 ms 7.914 ms
5 64.208.110.70 (64.208.110.70) 71.364 ms 72.592 ms 70.641 ms
6 ten-gige-1-1.mpr1.ams2.nl.above.net (64.125.26.73) 71.871 ms 68.617 ms 72.152 ms
7 * * *

Traceroute from mpr1.ams2.nl.above.net -> comhem
1 ge-1-2-0.mpr1.ams1.nl.above.net (64.125.26.74) 0 msec 0 msec 0 msec
2 *
ge6-0-0-104-1000M.ar1.AMS1.gblx.net (64.208.110.69) 52 msec 52 msec
3 64.209.107.210 [AS 3549] 72 msec 76 msec 72 msec
4 vrr-bb-r-02-to-vrr-pr-r-01.comhem.se (83.255.252.215) [AS 39651] 68 msec 68 msec *
5 *
83.255.248.169 [AS 39651] 64 msec *

ping from comhem to 64.209.107.209:
--- 64.209.107.209 ping statistics Tue Sep 2 21:04:02 2008 ---
1000 packets transmitted, 1000 received, 0.00% packet loss, time 9446ms
rtt min/avg/max/mdev = 7.341/9.900/64.297/4.649 ms

ping from comhem to 64.208.110.70:
--- 64.208.110.70 ping statistics Tue Sep 2 21:04:53 2008 ---
1000 packets transmitted, 939 received, 6.10% packet loss, time 12789ms
rtt min/avg/max/mdev = 76.327/83.133/130.499/6.359 ms

ping from comhem to 64.125.26.73:
--- 64.125.26.73 ping statistics Tue Sep 2 21:05:41 2008 ---
1000 packets transmitted, 391 received, 60.90% packet loss, time 12349ms
rtt min/avg/max/mdev = 76.840/105.671/300.997/52.043 ms

ping from mpr1.ams2.nl.above.net -> mpr1.ams1.nl.above.net
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

ping from mpr1.ams2.nl.above.net -> 64.208.110.69 (ar1.AMS1.gblx.net)
Success rate is 40 percent (2/5), round-trip min/avg/max = 60/60/60 ms

--------

traceroute from bbb to rp.entropiauniverse.com
2 ti3031a211-pc5.ti.telenor.net (146.172.72.125) 3.103 ms 5.106 ms 3.978 ms
3 ti3005d320-ge3-0-0.ti.telenor.net (146.172.109.17) 4.188 ms 5.396 ms 4.219 ms
4 * * *
5 ti3003c310-ae5-0.ti.telenor.net (146.172.100.33) 8.952 ms 8.651 ms 8.471 ms
6 ti6000b300-ae1-0.ti.telenor.net (146.172.105.22) 11.244 ms 9.872 ms 10.920 ms
7 212.162.17.133 (212.162.17.133) 28.248 ms 28.157 ms 28.017 ms
8 ae-31-55.ebr1.Dusseldorf1.Level3.net (4.68.119.158) 32.429 ms 29.501 ms 32.580 ms
9 ae-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 40.589 ms 42.387 ms 35.609 ms
10 ae-1-100.ebr1.Dusseldorf1.Level3.net (4.69.132.129) 32.179 ms 38.026 ms 36.178 ms
11 ae-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 43.246 ms 41.155 ms 37.147 ms
12 ae-22-54.car2.Frankfurt1.Level3.net (4.68.118.112) 38.078 ms ae-22-56.car2.Frankfurt1.Level3.net (4.68.118.176) 36.838 ms ae-22-52.car2.Frankfurt1.Level3.net (4.68.118.48) 36.013 ms
13 ge-1-8.mpr1.fra1.de.above.net (62.4.64.61) 38.210 ms 36.694 ms 38.080 ms
14 ten-gige-1-1.mpr1.ams2.nl.above.net (64.125.26.73) 86.358 ms 79.728 ms 81.707 ms
15 * * *
16 ten-gige-1-1.mpr1.ams2.nl.above.net (64.125.26.73) 86.314 ms 90.604 ms 88.477 ms

ping from bbb to 4.68.118.112
--- 4.68.118.112 ping statistics Tue Sep 2 21:48:58 2008 ---
1000 packets transmitted, 1000 received, 0.00% packet loss, time 11984ms
rtt min/avg/max/mdev = 35.092/37.321/78.036/2.313 ms

ping from bbb to 62.4.64.61:
--- 62.4.64.61 ping statistics Tue Sep 2 21:50:12 2008 ---
1000 packets transmitted, 1000 received, 0.00% packet loss, time 12060ms
rtt min/avg/max/mdev = 36.184/38.120/45.612/0.885 m

ping from bbb to mpr1.ams2.nl.above.net
--- 64.125.26.73 ping statistics Tue Sep 2 21:51:14 2008 ---
1000 packets transmitted, 989 received, 1.10% packet loss, time 12529ms
rtt min/avg/max/mdev = 73.976/97.031/280.563/40.135 ms

I'll log on to chat only
No decay from me until the issue is resolved

It will be more useful if everyone could use the pathping command instead of ping/tracert.

And, please pathping to 64.125.26.73, the ip specified in the support ticket from MA listed in this thread.

And when you list your results, I would definitely delete at least your own ip address, if not the first few hops.

This morning the lag is gone for me. It'll be interesting to see if it has returned when I get back home tonight.

K, someone please explain...

MA gives us the ability to select our connection speeds in options. Isn't that 'supposed' to be taking care of packet losses etc??? Why isn't it working???? Isn't it at least in part on MA's side if it isn't working???????

Packet loss can't be the end all / only explanation to the ammo loss and missing if ppl can 'shuffle' for example to stop the problem. All of us changing ISP's can't be a 'solution' to this problem.

Yes, MA should have communicated openly that they were having problems with a node or whatever. These kind of problems should be in the client loader. We shouldn't have to lose any ammo etc without warning from them that there is a problem. Sigh... ...

Casay said:

Packet loss can't be the end all / only explanation to the ammo loss and missing if ppl can 'shuffle' for example to stop the problem. All of us changing ISP's can't be a 'solution' to this problem.

Click to expand...

the "suffle" thing is an old/ongoing thing thats different. it doesnt help with missed faps/cant equip/item locked messages. i brought it up at a point where it seemed there might be a random problems and i was insinuating that MA was doing something deliberat to invoke a human responce to prove bots werent in use. far fetched maybe, but its somthing that comes and goes.

it since has developed in to a wholesale networking issue. but it could be on a network between MA's ISP and individuals, so its tricky to say how to fix - and MA may not kow there is an issue. ICMP used for ping can also be dropped or low priority, so people testing will get readings that indicate a problem where one doesnt exist. However, there is a strong suggestion theres somthing up with abovenet and that could be due to traffic shaping or them rejigging networks or a dozen other things.

raise support cases and get MA looking at from there end, they will get a better overview of where its coming from and have more clout.

The sad thing is that MA seems to be viewing it as not a problem of them.
It has a big negative impact on how a lot of people experience the game.

I have stopped hunts because of hanging FAP/weapon problems. Mobs that normally can't kill me any more managed to kill me because i could not equip the FAP or even the heal failed while i had to wait to heal a 2nd time.

If this happens more then 3 times in a hunt i disband the hunt. Which actually means MA is loosing money because of this since i stop generating decay.

In my point of view MA should have a mechanism where they can sort of look over the shoulder of a player and see what is happening to them. This way they can experience what we are experiencing. And they should together with their ISP start to look at a packet level why so many packets are dropped.

Symptoms like seeing half of your FL drop offline at the same moment with connections lost are real symptoms. Especially when those people come from all over the world.

Seeing that many people from all over the world are experiencing the same issue's it can only be somewhere in the MA network/servers or with their ISP.
The last is improbable though. ISP's can not afford to have such big problems since customers start running away really fast. My guess is there are some structural problems in MA's network/server park or something is wrong in the client server configuration of the game itself.

Cheers Siam

Daltor said:

This morning the lag is gone for me. It'll be interesting to see if it has returned when I get back home tonight.

Click to expand...

Im almost sure lag will return at peaktime

I still have high ping times and "almost" dropped packets. ~70-100ms ping times and i live only 150km from gothenburg.

rhogenbe said:

Symptoms like seeing half of your FL drop offline at the same moment with connections lost are real symptoms. Especially when those people come from all over the world.

Click to expand...

I think when several people drop off at once it is because of server reboots, not related to the lost packets problem. But I agree with everything else you said.

Xen said:

I think when several people drop off at once it is because of server reboots, not related to the lost packets problem. But I agree with everything else you said.

Click to expand...

Not necesarrely always the case. I had it happen that over half of the people in Camp Echidna suddenly went offline while i and a few other did not experience any problem at all.

The following is some speculation of my part:

I sometimes have the feeling that a session is managed by 2 servers. 1 is a logon/session server of which there are at least 2 mayby even more (one being down does not show on the active server list since i think this are only the area server, i could be wrong though). And the other is the area server where you are on at that time.

If one of those two gets into problems this seems to result in a connection lost.

Cheers
Siam

Seems ok for me 337ms and 0% packet loss.

To OP,

Not sure if this has been suggested yet,

Though you may wish to ring your provider and ask them what the recommended MTU size should be set to on your modem/router when connecting to their service.

I did not see the device & method listed in your post to how your connecting to the internet, though some routers and modems have a funky default setting for the Maximum Transmission Unit Size which is larger than what the service provider handles (has set) often incurring packet loss.

This is a common problem in the cheaper brands of modems/routers.

I have yet to experience any major non-VU inccured lag issues since the start of this year and I am in Australia on a QoS business subscription plan with our national provider Telstra.

Cheers,
Sparkz

Mirandax said:

In May i first started getting the problem. Lots of busy items and swaplag. It got a bit better but now it's horrible. Not only is it very frustrating and annoying but I also die from it waiting for the fappings to come thru. Half the time i emptyfap.

I tried pinging the servers and I got the following result:

Ping-statistic for 64.125.26.77:
Packet: Sent = 104, Received = 85, Lost = 19 (18 %),
Transfertime in milliseconds:
Lowest = 60 ms, Highest = 212 ms, Average = 67 ms

My ISP is Telia, and I have no packet loss to anywhere else it seems.Is anyone else experiencing similar problems? Any ideas what I can do?

Click to expand...

I have a Ping of Lowest = 55 ms, Highest = 412 ms i lost 28 of 100 packets
and im sitting locally @ the ISP Telia so i should have decent times... but when i tell this to the support the fault is at my place or my computer .... so i guess they are as clueless as usual.

predden said:

I have a Ping of Lowest = 55 ms, Highest = 412 ms i lost 28 of 100 packets
and im sitting locally @ the ISP Telia so i should have decent times... but when i tell this to the support the fault is at my place or my computer .... so i guess they are as clueless as usual.

Click to expand...

They COULD be right that the problem is on your computer/LAN or your ISP or whatever... But as this thread suggests, it's most likely not.

So, show support a print of a tracert or pathping to their IPs (See earlier in this thread if you don't know how).

Then they can see, where the problem is.