Report Lag Here

[Jimcav]

Running a tracert is probably a waste of time, the lag is almost never correlated with actual connectivity problems. Whatever is causing the server to be so slow appears to be within the server itself. We can connect TO the server quickly enough, but once there our packets need an excessively long time to trigger a response. Maybe the server farm operator periodically runs some housekeeping apps on S1 that are sapping its cpu cycles and slowing down response time. Whatever its source, the lag problem doesn't seem to be as bad as it was some months ago. The server is now downright fast at times and the lag storms are less common, but the problem still occurs and still seems specific to S1 and not present on S2.

[Shotgun Opera]

I guess people have decided that it is now just a part of the game and have stopped complaining but we are still getting lag... it is by no means as bad as it was but it is still occuring. the problem is not usually present during the daytime hours but seeing as I'm usually at work then I can't just play during the day. Last night the lag was bad enough to cause people to log off right now it isn't as bad but is still there. I have asked a few others in game and they are also experiencing lag at this time. If you could please look into what is causing this problem it would be appreciated. Thank you

I couldn't even log in because there was so much lag. It times out every click, doesn't load at all. No pictures, nothing. It's not just me either, the entire game had the same problem.

Terrible lag on S2 right now, past 40 min or so have been almost impossible to act.

[Northern Silence]

For once out of 3524657246 reports it really is the server/end network lagging. This is how a tracert looks when it is.

D:\Documents and Settings\Administrator>tracert rwk2.racewarkingdoms.com

Tracing route to rwk2.racewarkingdoms.com [64.34.186.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms pfsense.hyperfoto.com [192.168.0.1]
2 7 ms 7 ms 7 ms 73.102.128.1
3 8 ms 7 ms 5 ms 68.87.207.241
4 7 ms 8 ms 7 ms po-10-ur02.tacoma.wa.seattle.comcast.net [68.85.
240.98]
5 10 ms 10 ms 13 ms be-60-ar01.seattle.wa.seattle.comcast.net [68.85
.240.89]
6 11 ms 9 ms 10 ms pos-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [
68.86.90.209]
7 9 ms 13 ms 16 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
8 16 ms 17 ms 18 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]

9 12 ms 17 ms 17 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]

10 38 ms 50 ms 39 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
11 62 ms 62 ms 63 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
12 62 ms 63 ms 61 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

13 90 ms 91 ms 92 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

14 97 ms 92 ms 93 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.1
58]
15 95 ms 91 ms 93 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
16 93 ms 93 ms 93 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
17 * * * Request timed out.
18 * * * Request timed out.
19 292 ms 288 ms 288 ms mail.racewarkingdoms.com [64.34.186.10]

Trace complete.

D:\Documents and Settings\Administrator>

[Shotgun Opera]

so funny NS ... looks just like all the ones I've posted before but yours is the one showing lag.

Anyways on to todays bussiness... server1 is experiencing lag and has several times over the past few days... tracert looks good but there is lag on S1 and not on s2... I am not the only one seeing it it is there ask in shout.

[Northern Silence]

because mine shows connection problems AFTER my ISP, interstate hops, and Peer1(jeff's datacenter pipe)

19 292 ms 288 ms 288 ms mail.racewarkingdoms.com [64.34.186.10]

there is no lag or packet loss untill it reaches jeff's server so that is where the lag was at that time. All your tracerts (except one 09-13-2009, 12:03 AM ) show no increased ping or lag directly on jeff's server.

[Shotgun Opera]

its lagging again at around noon game time

same problem for several days now

ISSUE 1: NOD Issue

1:10 Server Time to about 3:00 Server Time there were issues on mail.nodiatis.com directly, the host was not responding to requests frequently during this time period.

Biggest issue during this time: 1:30 - 2:00.

That being said, it seems that my NOD client was not affected by the problems!


ISSUE 2: Internet Issue

Currently and to this moment, starting from 5:30 server time I am seeing a lot of packet loss on the way to mail.nodiatis.com

The packet loss starts with ae-4-4.ebr4.Washington1.Level3.net (4.69.144.52).

I realize this one is an internet issue, there is nothing you can do about it(am just posting for other's benefit so that they can see the difference).

This issue is directly affecting my NOD client, I am getting the server timeout countdown messages.

FYI

Boom

It's been several weeks now me and my roomate have been having lag, not even just RWK but I don't know if it's a bad modem or what. My ISP, comcast says its not them because when I run speed tests, the download speed is fast but we still constantly lag. Whatever this peer1-gw.ip4.tinet. net thing is, seems to be at least part of the problem. I ran 3 ping tests and 3 tracerts:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.



Pinging rwk [64.34.186.9] with 32 bytes of data:
Reply from 64.34.186.9: bytes=32 time=319ms TTL=113
Reply from 64.34.186.9: bytes=32 time=49ms TTL=113
Reply from 64.34.186.9: bytes=32 time=131ms TTL=113
Reply from 64.34.186.9: bytes=32 time=50ms TTL=113

Ping statistics for 64.34.186.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 319ms, Average = 137ms

C:\Users\Tim>ping rwk

Pinging rwk [64.34.186.9] with 32 bytes of data:
Reply from 64.34.186.9: bytes=32 time=130ms TTL=113
Reply from 64.34.186.9: bytes=32 time=105ms TTL=113
Reply from 64.34.186.9: bytes=32 time=107ms TTL=113
Reply from 64.34.186.9: bytes=32 time=175ms TTL=113

Ping statistics for 64.34.186.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 175ms, Average = 129ms

C:\Users\Tim>ping rwk

Pinging rwk [64.34.186.9] with 32 bytes of data:
Reply from 64.34.186.9: bytes=32 time=56ms TTL=113
Reply from 64.34.186.9: bytes=32 time=177ms TTL=113
Reply from 64.34.186.9: bytes=32 time=178ms TTL=113
Reply from 64.34.186.9: bytes=32 time=672ms TTL=113

Ping statistics for 64.34.186.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 672ms, Average = 270ms

C:\Users\Tim>tracert rwk

Tracing route to rwk[64.34.186.9]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 23 ms 76 ms 42 ms 98.206.16.1
3 163 ms 13 ms 12 ms te-7-1-sr01.dekalb.il.chicago.comcast. net [68.86
.115.141]
4 110 ms 18 ms 63 ms te-6-3-ur04.wchicago.il.chicago.comcast.n et [68.
87.210.154]
5 35 ms 59 ms 42 ms te-1-1-0-2-ar01.area4.il.chicago.comcast. net [68
.87.210.137]
6 26 ms 17 ms 20 ms pos-3-9-0-0-cr01.350ecermak.il.ibone.comcast. net
[68.86.90.45]
7 24 ms 20 ms 22 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast. net
[68.86.86.158]
8 53 ms 64 ms 18 ms xe-9-0-0.chi10.ip4.tinet. net [77.67.71.145]
9 55 ms 91 ms 56 ms xe-7-1-0.was14.ip4.tinet. net [89.149.184.42]
10 407 ms 118 ms 78 ms peer1-gw.ip4.tinet. net [173.241.128.102]
11 * * * Request timed out.
12 * * * Request timed out.
13 227 ms 56 ms 75 ms mail.glitchless. com [64.34.186.9]

Trace complete.

C:\Users\Tim>tracert rwk

Tracing route to racewarkingdoms. com [64.34.186.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 29 ms 48 ms 29 ms 98.206.16.1
3 27 ms 14 ms 68 ms te-7-1-sr01.dekalb.il.chicago.comcast. net [68.86
.115.141]
4 74 ms 236 ms 15 ms te-6-3-ur04.wchicago.il.chicago.comcast. net [68.
87.210.154]
5 253 ms 150 ms 132 ms te-1-1-0-2-ar01.area4.il.chicago.comcast. net [68
.87.210.137]
6 21 ms 65 ms 101 ms pos-3-9-0-0-cr01.350ecermak.il.ibone.comcast. net
[68.86.90.45]
7 66 ms 128 ms 21 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast. net
[68.86.86.158]
8 18 ms 40 ms 36 ms xe-9-0-0.chi10.ip4.tinet. net [77.67.71.145]
9 272 ms 120 ms 77 ms xe-7-1-0.was14.ip4.tinet. net [89.149.184.42]
10 93 ms 154 ms 180 ms peer1-gw.ip4.tinet. net [173.241.128.102]
11 * * * Request timed out.
12 * * * Request timed out.
13 312 ms 55 ms 69 ms mail.glitchless. com [64.34.186.9]

Trace complete.

C:\Users\Tim>tracert rwk

Tracing route to rwk[64.34.186.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 46 ms 49 ms 49 ms 98.206.16.1
3 98 ms 30 ms 16 ms te-7-1-sr01.dekalb.il.chicago.comcast. net [68.86
.115.141]
4 25 ms 67 ms 17 ms te-6-3-ur04.wchicago.il.chicago.comcast. net [68.
87.210.154]
5 713 ms 20 ms 17 ms te-1-1-0-2-ar01.area4.il.chicago.comcast. net [68
.87.210.137]
6 30 ms 17 ms 76 ms pos-3-9-0-0-cr01.350ecermak.il.ibone.comcast. net
[68.86.90.45]
7 86 ms 18 ms 18 ms pos-1-3-0-0-pe01.350ecermak.il.ibone.comcast. net
[68.86.86.158]
8 47 ms 32 ms 73 ms xe-9-0-0.chi10.ip4.tinet. net [77.67.71.145]
9 118 ms 118 ms 86 ms xe-7-1-0.was14.ip4.tinet. net [89.149.184.42]
10 87 ms 791 ms 64 ms peer1-gw.ip4.tinet. net [173.241.128.102]
11 * * * Request timed out.
12 * * * Request timed out.
13 326 ms 56 ms 81 ms mail.glitchless. com [64.34.186.9]

Trace complete.

Any ideas? Thanks

[Northern Silence]

You have 700+ms pings onr andom hops all over the place. Check your network for torrent clients.

[Midtun]

Hello,

Just want to report that the game has been lagging non stop all day for several players from Europe.
There is something wrong with the new server.

[Glitchless]

RWK announcements have been updated with a temporary work around for people having issues.

[xaivia]

The lag is really bad again today.

[Per]

I'm having crazy lag spikes on S2 right now. Several minutes at a time of requests timing out.

[Soxson]

Need more than that. Operating system, RAM, browser (and if up to date), the tracert (do different tracerts for each server, or post both). Post all that and glitch is more likely to look into it.

Go to windows start and type CMD and hit enter. The black box will appear. Type "Tracert nd1.nodiatis.com" (for server 1) and hit enter. And then copy and paste the results. (you may need to right click to copy) Don't ask me how to do this on apple products.

*just an example, nod is running fine for me*

2012 pavillion g6 series laptop running windows 7, 6 GB of RAM, up to date mozilla firefox browser

Tracing route to nd1.nodiatis.com [208.100.40.128]
over a maximum of 30 hops:

1 7 ms 1 ms 2 ms router.asus.com [192.168.1.1]
2 10 ms 10 ms 10 ms d192-24-1-230.col.wideopenwest.com [24.192.230.1
]
3 13 ms 9 ms 9 ms dynamic-76-73-171-69.knology.net [76.73.171.69]

4 12 ms 11 ms 12 ms 76-73-164-125.knology.net [76.73.164.125]
5 11 ms 18 ms 11 ms 76-73-164-121.knology.net [76.73.164.121]
6 11 ms 10 ms 11 ms 76-73-164-109.knology.net [76.73.164.109]
7 15 ms 12 ms 13 ms 76-73-164-105.knology.net [76.73.164.105]
8 11 ms 19 ms 13 ms 76-73-164-65.knology.net [76.73.164.65]
9 18 ms 12 ms 13 ms static-76-73-191-224.knology.net [76.73.191.224]

10 14 ms 13 ms 16 ms dynamic-75-76-35-10.knology.net [75.76.35.10]
11 13 ms 15 ms 12 ms dynamic-75-76-35-6.knology.net [75.76.35.6]
12 13 ms 13 ms 13 ms eqix1.chi01.steadfast.NET [206.223.119.34]
13 14 ms 20 ms 13 ms te3-3.dist01.chi01.steadfast.net [208.100.32.55]

14 12 ms 13 ms 15 ms nd1.nodiatis.com [208.100.40.128]

[xaivia]

Nod is on different servers to RWK. It was down for everyone for over an hour. Unless you are a server admin for Glitchless (hint: you aren't) your contributions to this thread are less than helpful.

[Soxson]

Originally Posted by xaivia

Nod is on different servers to RWK. It was down for everyone for over an hour. Unless you are a server admin for Glitchless (hint: you aren't) your contributions to this thread are less than helpful.

Then CMD > Tracert http://www.racewarkingdoms.com/ instead of nd1.nodiatis.com >_>

Doesn't take a computer scientist to figure it out <_<

[xaivia]

Originally Posted by Soxson

Then CMD > Tracert http://www.racewarkingdoms.com/ instead of nd1.nodiatis.com >_>

Doesn't take a computer scientist to figure it out <_<

True. The other thing that doesn't take a computer scientist to figure out is that condescending investigation recommendations on behalf of Glitchless make you look like a gargling moron.

There is no need to perform a tracert when the servers are down for everyone. It wasn't a network issue, you are not being helpful. You do not work for them, you do not have the first clue what Jeff needs to know from the players to investigate the issue this morning.

[Niizandar]

here is my report from today at 11:10 am Est.

PS. I am sorry if your eyes are bleeding because it's in french my tech don't know much about english.


Microsoft Windows [version 10.0.10586]
(c) Microsoft Corporation, 2015. Tous droits r?serv?s.

C:\Users\Insis Client.DESKTOP-OHVMJU8>tracert www.racewarkingdoms.com

D?termination de l’itin?raire vers www.racewarkingdoms.com [208.100.40.136]
avec un maximum de 30 sauts*:

1 8 ms 9 ms 8 ms 10.11.0.1
2 336 ms 309 ms 307 ms 207-164-139-121.telebecinternet.net [207.164.139.121]
3 335 ms * 137 ms admin.telebecinternet.com [207.164.139.13]
4 175 ms 179 ms 200 ms ae7.bx01.mtrl.pq.aliant.net [207.231.227.129]
5 239 ms 240 ms 261 ms ae8.bx01.toro.on.aliant.net [207.231.227.121]
6 297 ms 350 ms 324 ms bx2-torontoxn_ae3 [184.150.187.56]
7 343 ms 356 ms * xe-8-2-1.bar1.Toronto1.Level3.net [4.59.183.185]
8 * * * D?lai d’attente de la demande d?pass?.
9 308 ms 295 ms 298 ms NOZONE-INC.ear2.Chicago2.Level3.net [4.71.248.202]
10 356 ms 375 ms 403 ms te9-1.dist02.chi01.steadfast.net [208.100.32.35]
11 470 ms 431 ms * rwk1.racewarkingdoms.com [208.100.40.136]
12 196 ms 211 ms 217 ms rwk1.racewarkingdoms.com [208.100.40.136]

Itin?raire d?termin?.

C:\Users\Insis Client.DESKTOP-OHVMJU8>ping www.racewarkingdoms.com

Envoi d’une requ?te 'ping' sur www.racewarkingdoms.com [208.100.40.136] avec 32 octets de donn?es*:
R?ponse de 208.100.40.136*: octets=32 temps=197 ms TTL=119
R?ponse de 208.100.40.136*: octets=32 temps=258 ms TTL=119
R?ponse de 208.100.40.136*: octets=32 temps=299 ms TTL=119
R?ponse de 208.100.40.136*: octets=32 temps=351 ms TTL=119

Statistiques Ping pour 208.100.40.136:
Paquets*: envoy?s = 4, re?us = 4, perdus = 0 (perte 0%),
Dur?e approximative des boucles en millisecondes :
Minimum = 197ms, Maximum = 351ms, Moyenne = 276ms

C:\Users\Insis Client.DESKTOP-OHVMJU8>