Lag, Rubberband, Lag, Kicked off server

[Norna]

Okay, this is ridiculous. I can't even PvE with this kind of lag/latency: Clicking on an NPC causes a 10 second freeze-lag before either I get error 90K or dialog pops up. Attacking random mob out in the middle of nowhere: lag of 5-10 seconds, rubberband, then some more lag followed by being kicked off the server (or I die from unavoidable AoEs/unseen respawns mobbing me and get kicked off the server while porting home).

Both Balmung (US Legacy) and Moogle (EU) does this. I have even tried ALL (spanning the globe at this point) the servers of three different tunneling services to see if it was a problem on my end, and got the same result. Also, it wasn't prime-time yet on either server.

But to make sure, it isn't just me who is getting this, right?

[ninesunz]

system specs?

while logged into the game:
start > run > cmd
type "netstat"
look for listing that starts with 199.

in the same cmd window type
tracert 199.xxx.xxx.xxx

do this 4 or 5 times
post results

this will show if anywhere in your connection there is a provider having an issue keeping your data alive

[Norna]

Well, here it is:

System Specs:
Windows 7 Ultimate 64 bit
Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (Overclocked to 4.00GHz, underclocking makes no change)
16345.523MB RAM
NVIDIA GeForce GTX 690(VRAM 4038 MB) 9.18.0013.3182
Screen: ASUS VG248QE (144GHz)

Character Benchmark:

Score:11340
Average Framerate:102.061
Performance:Extremely High
-Easily capable of running the game on the highest settings.

Screen Size: 1920x1080
Screen Mode: Full Screen
Graphics Presets: Custom
General
-Enable HDR rendering and improve overall graphic quality. : Enabled
-Disable rendering of objects when not visible. (Occlusion Culling) : Enabled
-Use low-detail models on distant objects. (LOD) : Disabled
-Cache LOD data only when necessary. (LOD Streaming) : Disabled
-Real-time Reflections : High
-Edge Smoothing (Anti-aliasing) : Off
-Transparent Lighting Quality : High
-Grass Quality : High
Shadows
-Self : Display
-Other NPCs : Display
Shadow Quality
-Use low-detail models on shadows. (LOD) : Enabled
-Shadow Resolution : High - 2048p
-Shadow Cascading : Best
-Shadow Softening : Strong
Texture Detail
-Texture Filtering : Anisotropic
-Anisotropic Filtering : x16
Movement Physics
-Self : Full
-Other NPCs : Full
Effects
-Naturally darken the edges of the screen. (Limb Darkening) : Enabled
-Blur the graphics around an object in motion. (Radial Blur) : Enabled
-Screen Space Ambient Occlusion : Strong
-Glare : Normal
Cinematic Cutscenes
-Enable depth of field. : Enabled

-------------------------------------------------------------------

Big huge traceroute:

Spårar route till 199.91.189.27 över ett maximalt antal av 30 hopp

1 2 ms 1 ms 2 ms 192.xxx.xxx.xxx
2 24 ms 23 ms 24 ms gw1-no116.tbcn.telia.com [90.224.86.1]
3 40 ms 39 ms 39 ms s-b2-link.telia.net [80.91.248.69]
4 38 ms 39 ms 38 ms level3-ic-155475-s-b2.c.telia.net [213.248.99.13
4]
5 147 ms 147 ms 148 ms ae-214-3604.ebr1.Berlin1.Level3.net [4.69.159.14
]
6 148 ms 146 ms 157 ms ae-1-100.ebr2.Berlin1.Level3.net [4.69.148.206]

7 149 ms 149 ms 148 ms ae-28-28.ebr2.Dusseldorf1.Level3.net [4.69.200.1
73]
8 152 ms 151 ms 150 ms ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.19
7]
9 156 ms 154 ms 154 ms ae-24-24.ebr2.Amsterdam1.Level3.net [4.69.143.66
]
10 149 ms 147 ms 148 ms ae-46-46.ebr2.London1.Level3.net [4.69.143.74]
11 147 ms 149 ms 146 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

12 148 ms 149 ms 148 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

13 149 ms 149 ms 151 ms ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41]

14 153 ms 152 ms 267 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
15 203 ms 268 ms 229 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

16 149 ms 148 ms 151 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
17 * * * Begäran gjorde timeout.
18 159 ms 159 ms 159 ms 192.34.76.2
19 151 ms 151 ms 152 ms 199.91.189.234
20 153 ms 155 ms 153 ms 199.91.189.27

-----------

Spårar route till 199.91.189.27 över ett maximalt antal av 30 hopp

1 1 ms 1 ms 1 ms 192.xxx.xxx.xxx
2 25 ms 23 ms 27 ms gw1-no116.tbcn.telia.com [90.224.86.1]
3 41 ms 39 ms 39 ms s-b2-link.telia.net [80.91.248.69]
4 39 ms 39 ms 38 ms level3-ic-155475-s-b2.c.telia.net [213.248.99.13
4]
5 149 ms 148 ms 148 ms ae-214-3604.ebr1.Berlin1.Level3.net [4.69.159.14
]
6 148 ms 146 ms 148 ms ae-1-100.ebr2.Berlin1.Level3.net [4.69.148.206]

7 149 ms 147 ms 148 ms ae-28-28.ebr2.Dusseldorf1.Level3.net [4.69.200.1
73]
8 152 ms 151 ms 151 ms ae-45-45.ebr1.Amsterdam1.Level3.net [4.69.143.19
7]
9 153 ms 155 ms 154 ms ae-24-24.ebr2.Amsterdam1.Level3.net [4.69.143.66
]
10 148 ms 148 ms 147 ms ae-46-46.ebr2.London1.Level3.net [4.69.143.74]
11 148 ms 150 ms 147 ms ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

12 149 ms 149 ms 148 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

13 151 ms 149 ms 148 ms ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41]

14 296 ms 208 ms 204 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
15 153 ms 151 ms 152 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

16 149 ms 149 ms 148 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
17 * * * Begäran gjorde timeout.
18 160 ms 159 ms 161 ms 192.34.76.2
19 152 ms 151 ms 150 ms 199.91.189.234
20 154 ms 154 ms 155 ms 199.91.189.27

Spårning utförd.

-----------

All the rest are the same, so I don't think posting them will change anything.

[ZohnoReecho]

Well, here it is:

Looks like nodes 15/16 in Montreal are your main issue.
SE servers are after 17.

[Norna]

Looks like nodes 15/16 in Montreal are your main issue.
SE servers are after 17.

Isn't it that S-E works with Ormuco (from what I can gather, they do data center/cloud services) in keeping their NA/EU data center running? Why would there be such huge packet loss between Ormuco and S-E's server architecture? Also, I looked around at others having similar problems, and saw that a few with posted trace routes have perfect connections until they hit Ormuco, then they either get losses where I do, or between the S-E IP addresses.

[ZohnoReecho]

Isn't it that S-E works with Ormuco (from what I can gather, they do data center/cloud services) in keeping their NA/EU data center running? Why would there be such huge packet loss between Ormuco and S-E's server architecture? Also, I looked around at others having similar problems, and saw that a few with posted trace routes have perfect connections until they hit Ormuco, then they either get losses where I do, or between the S-E IP addresses.

If Ormuco is bad it doesn't mean it's SE fault xD
I did a tracert too and the last 3 nodes are the only thing in common.

1 <1 ms 1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms OPENRG [192.168.1.254]
3 10 ms 11 ms 11 ms 10.134.248.1
4 10 ms 10 ms 10 ms 10.3.233.162
5 11 ms 10 ms 10 ms 10.251.149.209
6 10 ms 10 ms 10 ms 10.251.144.37
7 11 ms 9 ms 10 ms 10.251.145.1
8 11 ms 10 ms 9 ms 10.251.149.194
9 10 ms 10 ms 9 ms 10.3.136.205
10 11 ms 11 ms 10 ms 10.3.128.62
11 11 ms 10 ms 10 ms 10.254.11.73
12 28 ms 14 ms 14 ms 10.254.1.81
13 15 ms 15 ms 15 ms 89.97.200.170
14 25 ms 24 ms 24 ms 89.96.200.1
15 24 ms 24 ms 24 ms 89.96.200.114
16 59 ms 206 ms 99 ms te2-3.ccr01.mil01.atlas.cogentco.com [149.6.152.69]
17 29 ms 28 ms 29 ms te0-0-0-3.ccr21.zrh01.atlas.cogentco.com [154.54.62.6]
18 34 ms 37 ms 34 ms be2023.ccr21.muc01.atlas.cogentco.com [130.117.0.249]
19 38 ms 38 ms 38 ms te0-2-0-2.mpd21.fra03.atlas.cogentco.com [130.117.48.69]
20 47 ms 45 ms 45 ms te0-5-0-3.mpd21.ams03.atlas.cogentco.com [154.54.78.169]
21 57 ms 55 ms 55 ms be2184.ccr21.lpl01.atlas.cogentco.com [154.54.37.70]
22 126 ms 126 ms 126 ms te0-2-0-1.ccr21.ymq02.atlas.cogentco.com [154.54.87.62]
23 127 ms 127 ms 126 ms 38.122.42.34
24 * * * Richiesta scaduta.
25 125 ms 123 ms 124 ms 192.34.76.2
26 124 ms 123 ms 123 ms 199.91.189.234
27 123 ms 124 ms 124 ms 199.91.189.27

[Norna]

So Ormuco is just an internet route owner like Cogent? *sighs* Would have been easier to fix if they worked directly with S-E.

Though it is interesting that your packet loss happens just before S-E's servers like mine, considering that we have totally different routes. Either they are stuck at Ormuco/Cogent's place, or S-E's servers refuses to receive them.

[ZohnoReecho]

So Ormuco is just an internet route owner like Cogent? *sighs* Would have been easier to fix if they worked directly with S-E.

Though it is interesting that your packet loss happens just before S-E's servers like mine, considering that we have totally different routes. Either they are stuck at Ormuco/Cogent's place, or S-E's servers refuses to receive them.

I think that's just a node that doesn't respond to pings. Might be SE's entry point.

[ninesunz]

Your system specs are good, so that shouldn't be an issue.

The node that doesn't report anything just before SE's servers, like Zohno said, is a node that doesn't respond to pings. These are fairly common.

What you want to do is keep running the tracert until you see one of the nodes that are currently giving data stop giving you responses. Or keep your command prompt open and when you get a bout of lag run the trace right away. Also pull up task manager when you start lagging (or keep it up full time) to see if you're having any run away processes. Task manager > peformance tab > resource monitor button. See if you're having high CPU, disk or memory usage during the latency.


My route path is surprisingly similar to yours Norna, in fact it's exactly the same after the 10th hop, but I do not have any latency issues.

[Marishi-Ten]

Level3 is currently having issues with routing traffic on SBC nodes:

http://www.internetpulse.net/