Okay, since the latest disconnect cost me an Artemis mk2, it's time to write down here.

I'm getting 100% immediate disconnect when I log in at first attempt. After this usually (most times) I log in normally.
During the time that I play, I have 50-ish ms ping, but, I still got some inadequate random disconnects without losing an internet connection at all, neither loosing a quality/speed of connection. Sometime, most of the cases, immediate relogin works, sometimes not, while still other sites are availible, even that one.
I tried shutting down all applications that could use the channel, such as skype, etc, and it does not help. I launched pingplotter during the play - it does not have even spikes when I got discoed, however, a very seldom packet loss appear, but without any visible effect on the game.
And the problem appeared only 4-5 days ago, previously I played without disconnections for a few days after I renewed subscription.

C Spawn
77.73.88.18
ISP UG-Telecom, Russia
8Mbit down/1Mbit up
Cable
http://www.speedtest.net/result/1579121561.png

Aaaargh, and now it even fatal crashed when I tried to record pingplotter tests. Next time, Mr. Fox.

Hello,
No idea if anyone from the Dev team is reading this. But the majority of our Corp is having issues with N/A Lag spikes when we go into battle be it with NPCs or other players. We can easily recreate just by targeting one another and we get N/A lag. It seems to affect people with higher latency than those with under 200ms. We have traced and many of the members have completely different routes to the server. It has been extremely bad the last 2-3 weeks since the last patch. We are even seeing lag up to 30 seconds when we are grinding NPCs and in battles, some of the guys haven't even seen their deaths due to the Lag being so bad.

Its important to understand that during mining, in station, running around seems to be ok ( not always but 99% of the time its stable and happy ), but as soon as we lock and start shooting many of the corp guys get N/A and we often just sit there not knowing what happens. Its near to unplayable.

Tracing route to 195.228.152.156 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    18 ms    18 ms    18 ms  nexthop.vic.iinet.net.au [203.215.7.251]
  3    17 ms    18 ms    18 ms  te7-2.mel-pipe-bdr2.iinet.net.au [203.215.6.12]
  4    31 ms    31 ms    32 ms  xe-0-1-0-0.syd-mas-core1.iinet.net.au [203.215.20.106]
  5   223 ms   223 ms   223 ms  34023.sydp06.cu.reach.com [134.159.160.57]
  6   179 ms   179 ms   179 ms  i-0-0-2-0.paix-core01.bx.reach.com [202.84.140.106]
  7   177 ms   177 ms   177 ms  i-1-2.paix01.bi.reach.com [202.84.251.74]
  8   226 ms   226 ms   226 ms  62.156.138.145
  9   396 ms   395 ms   413 ms  vie-sa3-i.VIE.AT.NET.DTAG.DE [62.154.14.93]
10   373 ms   373 ms   372 ms  194.25.210.178
11   373 ms   375 ms   373 ms  81.183.0.110
12   374 ms   375 ms   411 ms  81.183.0.201
13   376 ms   377 ms   376 ms  81.183.2.197
14   376 ms   375 ms   375 ms  195.228.152.156

BTW, if I do a ping -10000 to 195.228.152.156 and do a quick test.. My client will show N/A yet the ping is constantly around 377ms, here is a time where we tested, so its not dropping as far as we can see ( though we use showprofiler and at times we do have packet loss but its complete loss for a period of time and then all is good and only if we start to shoot someone/something ).

Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=378ms TTL=112
Reply from 195.228.152.156: bytes=32 time=383ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=380ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=378ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=380ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=379ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=379ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=378ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=379ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=406ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=377ms TTL=112
Reply from 195.228.152.156: bytes=32 time=376ms TTL=112

Through this ping my client experienced a number of N/A lag situations.. we were shooting each other in tests.

We have disable shadows, restarted clients etc etc.. and this is now getting beyond a joke. We had a battle this morning with RG, it was extremely frustrating to spend a majority of the battle with N/A and we are getting quite annoyed at it. Prior to the last patch we did not appear to have any of these issues.

We need this looked at ( and saying we have no issues with 80ms ping is not helping many ), but we are starting to get to the point of just saying game is unplayable and go and do something else.

Thanks

Duma

Edit: also when opening NPC containers we get N/A lag. For example, we have 2-3 NPC boxes. We try and access one and N/A lag.. then it comes good and we are able to loot all the containers fine.

The lag is horrible recently.
Instead of the usual stable 100 I more often get this (Ingame lag 300-1000 with N/A every 10 seconds).

The Alsbale triangle ...

The guys are working on the gridline lag issue for the new patch, we'll see how it will turn out.

Excellent news.

Perhaps I should have stuck it out and continued to "care bear" my rear off, but after almost losing a scarab to trash on the Shinjalar Hwy and the only official response at the time IIRC was something along the lines of
"we think its just an internet network issue but we'll look into it, no promises though"
I just couldn't muster the enthusiasm.

I'm looking foward to coming back as soon as it becomes playable again.
Thanks for the prompt and encouraging reply.

Ok this is probably related to the Grid Problem.
I was recently investigating on the lags i have in certain areas in the map while i stumbled upon the traffic graph function of my Net Limiter 2 and made some interesting observations.
Whenever i got past a certain coordinate there was a peak in traffic coming from the client passing that line. This peak is reproduceable at least for that spot. The following Screenshots show the spot and the correlating netgraph.

this one shows the spot

and this shows the netgraph when i pass this line back and forth in quick succession.
The Peak in Network Activity is very high and prolonged in comparison with just driving from point A to B.
I also made a screenshot of the netgraph while driving from Brightstone (Alsbale) over Naynitch teleport to Shinjalar Main Terminal using the Highway.

1) On this spot i entered Shinjalar
2) On this point i used the teleport from Ordurai I to Koija II
between 2 and 3 i passed a NPC group wich is marked with the little arrow
3) I entered the Main Terminal

You will also see Peaks on this Netgraph they are also very high but not as prolonged as in the first netgraph the reason for this is could be that i didnt start driving back and forth on the point i encountered a Traffic Peak or something entirely unrelated.
Whenever a player with a bad internet connection passes such a point he can experience a rapid increase in latency wich will quickly fall again in some cases that can be enugh to crash the conenction though....

Not sure if it's system lag or network lag, but when I first log on if my toon is deployed on island it  can take up to ten minutes for the client to load the island. I have three active accounts, but this is regardless of whether I have one, two or three clients running. If my toon is in station it can take between 5-10 minutes, on average, for my character to undock. After I click the undock button I have a black screen which, if I click on it, goes to a white screen which displays NOT RESPONDING in the title bar. The worst I have experienced was an approximately 15 minute lag between hitting undock and the client updating. Note, when the client updates with my character outside terminal, the undock and molecular instability timers are still running, so it's not as if they've undocked and I've just had a black screen.

I'm running Vista 32bit on an Intel dual core E4600 2.4G system with 3g RAM and a Radeon HD 5570 with all settings on all three clients as low as they go. I have two monitors and play with two clients in full screen windows and one floating window.  The problems occur when I have one client open and logged in, as well as when I have all three client windows open.

I agree with tux. I have killed alot of plants do to this issue. I have also noticed near stucrtures it gets worse MUCH worse alot of corp members along with myself have seen 12k plus since patch

I don't think test1 and test2.perpetuum-online.com are relevant anymore, or work for that matter.