Thank you. Yeah there was a 13 sec difference between the ship kill and the pod kill --- according to ccp i just sat there twiddling my thumbs.

There is a similar thread in the tech section called socket closed errors.
Basically lag has increased for some unknown reason since the last EVE game update.
For some it causes your issue. For others the lag is long enough to get them dissconnected.
I have been in missions over the last few days doing a battle when suddenly I jump 12 km.
I assume this is EVE lag and my client continues for several seconds doing its own thing then suddenly
gets an update after idle for a while and the screen jumps.
This lag seems to happen almost anytime.

But most frequently it happens when doing a session change or loading loot from a wreck/can.
Oddly enough it never seems to happen to me anyway when dropping out of warp.
That must trigger an update that has high priority. It never seems to miss.
But lots of other things do trigger this lag. You guys seem to be lucky enough that your lag does not last long enough to kick you out of the game like the others are getting in the tech help thread.

Lost a noctis to rats recently because of this very issue.

All I could do was sit and watch it die. No matter how many times you slowly and systematically click the location and other buttons to make that thing warp or even move, it ain't going anywhere.

As has been mentioned, submitting a petition only results in them saying no server issue at the time so the petition is declined.

Sounds to me like lag between you and the server.

May have been system related (AV updates can cause lag even with an amazing machine), may have been route related.

I work for my isp in 2nd line network monitoring. No issues there my ping times were 13ms at the time with ccp server also no packet loss. My pc is i7 with nvidia 680 with upto date drivers --- yeah i thought about these things as well but have ruled them out.

Since new inventory implementation there's crap arriving everywhere at everything you might or might not do. keep your cargo opened doesn't help in any way other than increase your lag, game small "crashes" more like if the game stopped completely for a few seconds but only for you, someone else has enough time to target you and kill you.

And there's nothing you can do because they will not come back on this crap, it's a very bad move from their part but they will never ever recognise it and will keep wasting time and people working on it to probably give us back the same thing we had for many years without a problem (except windows not remembering their positions) in about 5 years.

The base idea is good about this inventory, the way it's done is horrible and on top of taking out all the functionality we had just brought us hundreds of old/new bugs.

But you have to learn to deal wiz it. It's the new isk sync

Yeah I feel they know they have a problem, but are not acknowledging it. The ccp seems to internally lagging with so much more requests when ships die eg isk of everything lost --- if you have another ship corp hold open eg orca. It has to retrieve this as well.

I've not had the lag issue while my ship is exploding (and that happens a lot) but i have noticed a lot more socket disconnects than i am used to, but with myself and fellow fleet members.

Something in the patch borked things up, i hope they find it and fix it.

Had this trouble docking, my ship was still in space after Aura said "docking request accepted", than after some 20 seconds i was disconnected, then logged in back and my ship was in station... luckiily.

I also notice lag while undocking, warping, anything I click takes awhile before the action seems to be processed. It seems much slower then I remember before.

I also notice lag while undocking, warping, anything I click takes awhile before the action seems to be processed. It seems much slower then I remember before.

CCP Sputnik wrote:
Sione Tolutau wrote:
Hi guys sorry I've posted this in another thread but I am having the exact same issue
Location: New Zealand
ISP: slingshot

I don't have any packet loss when it happens for me. ping -t was this at all times from log in to "Socket was closed":
Reply from 87.237.38.200: bytes=32 time=301ms TTL=108

and tracert was this:

2 11 ms 11 ms 11 ms cpiak1-l9-G-internet.tranzpeer.net [202.180.81.32]
3 12 ms 10 ms 11 ms vlan93-cpcak3-e1.tranzpeer.net [202.180.76.68]
4 11 ms 11 ms 10 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 44 ms 11 ms 12 ms x7-1-0-101.akbr5.global-gateway.net.nz [202.50.234.61]
6 12 ms 11 ms 12 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
7 12 ms 12 ms 11 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
8 135 ms 142 ms 136 ms xe7-0-0.labr5.global-gateway.net.nz [202.50.232.18]
9 168 ms 167 ms 173 ms ae1-3.sjbr2.global-gateway.net.nz [203.96.120.94]
10 167 ms 169 ms 149 ms ae0.pabr4.global-gateway.net.nz [203.96.120.74]
11 169 ms 168 ms 138 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
12 146 ms 147 ms 149 ms vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
13 141 ms 141 ms 211 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
14 208 ms 211 ms 205 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
15 220 ms 209 ms 212 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.148.46]
16 274 ms 208 ms 208 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]
17 285 ms 278 ms 284 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
18 274 ms 273 ms 278 ms ae-56-221.csw2.London1.Level3.net [4.69.153.130]
19 * 273 ms 277 ms ae-2-52.edge4.London1.Level3.net [4.69.139.106]
20 278 ms 283 ms 302 ms srv248-e.ccp.cc [87.237.36.248]
21 305 ms 311 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
22 307 ms 302 ms 312 ms srv200-g.ccp.cc [87.237.38.200]

hope this helps..


Thank you Sione Tolutau.

I wanted to highlight your post to show people which information they should include in their petitions about the socket closed issue. Having all this information makes it a lot easier for us to figure out who, in this long trace, is responsible for dropping the ball/package.

PS. You might not see the package loss via ping -t if only packages within specific port rages get dropped.



While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement. According to our records, your ------- was killed at 20:30:52 and your pod was lost at 20:30:59. Any discrepancies with your own record of events indicates an issue either with your EVE client, your local computer's hardware or software, your local internet connection or third party hardware or software between the game server and your local client. Unfortunately, such issues are not eligible for reimbursement.

Explain that please dev. you provide evidence they tell you" While your computer generates some records, these records are generated client side and are not considered conclusive regarding reimbursement." Petition denied.