+- (wL) Forums (https://war-lords.net/forum)
+-- Forum: Community (https://war-lords.net/forum/forum-4.html)
+--- Forum: Suggestions or Issues (https://war-lords.net/forum/forum-16.html)
+--- Thread: Servers are lagging real bad (/thread-9146.html)
RE: Servers are lagging real bad - Matt - Dec 30 2012
An update from our host
Quote:Hello,
We have a ticket in to nlayer to see what can be done about it. that said we will likely shutdown the nlayer peer Monday and remove them from our network.
--
Dan P.
RE: Servers are lagging real bad - i cri everytiem - Jan 02 2013
No changes yet
RE: Servers are lagging real bad - Matt - Jan 03 2013
Can you provide some more tracerts please? nLayer was taken out of the network mix it seems.
RE: Servers are lagging real bad - Sibrox - Jan 03 2013
C:\Users\Jboy>tracert 173.231.20.20
Tracing route to 173.231.20.20 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 10 ms 13 ms 112.204.0.1
3 12 ms 13 ms 13 ms 122.2.135.97
4 12 ms 12 ms 14 ms 210.213.131.50
5 13 ms 12 ms 13 ms 210.213.133.49
6 170 ms 170 ms 171 ms 210.14.2.178
7 166 ms 166 ms 175 ms 206.223.143.122
8 171 ms 170 ms 171 ms 216.218.213.250
9 166 ms 167 ms 165 ms 100.42.223.150
10 172 ms 172 ms 171 ms 100.42.223.194
11 166 ms 165 ms 167 ms 173.231.20.20
Trace complete.
RE: Servers are lagging real bad - i cri everytiem - Jan 13 2013
Servers weren't lag bad for the past week. But today, couldn't join the servers again.
Code:
tracert 173.231.20.20
Tracing route to 173-231-20-20.hosted.static.webnx.com [173.231.20.20]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 83 ms 88 ms 84 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
3 71 ms 68 ms 70 ms xe-2-1-0-32767-sur01.eatontown.nj.panjde.comcast
.net [68.87.214.129]
4 66 ms 64 ms 77 ms xe-1-1-1-0-ar03.eastwindsor.nj.panjde.comcast.ne
t [68.85.62.77]
5 74 ms 72 ms 78 ms 68.86.152.113
6 81 ms 87 ms 76 ms pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.95.157]
7 72 ms 75 ms 79 ms be-10-pe04.ashburn.va.ibone.comcast.net [68.86.8
4.202]
8 237 ms 314 ms 235 ms as3491-pe01.ashburn.va.ibone.comcast.net [75.149
.228.78]
9 150 ms 140 ms 142 ms webnx.ge9-27.br01.lax05.pccwbtn.net [63.218.42.1
94]
10 138 ms 144 ms 142 ms 100-42-223-138.static.webnx.com [100.42.223.138]
11 139 ms 86 ms 85 ms 100-42-223-178.static.webnx.com [100.42.223.178]
12 88 ms 91 ms 93 ms 173-231-20-20.hosted.static.webnx.com [173.231.2
0.20]
Trace complete.RE: Servers are lagging real bad - Matt - Jan 13 2013
Pretty sure this is definitely a Comcast problem now. You have 88ms at your second hop, when the usual should be around 10-30ms.
Here is from a previous tracert of yours:
2 32 ms 29 ms 28 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
and now:
2 83 ms 88 ms 84 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
also:
8 237 ms 314 ms 235 ms as3491-pe01.ashburn.va.ibone.comcast.net [75.149.228.78]
which is before WebNX's network (transit provider pccwbtn.net)
RE: Servers are lagging real bad - Sibrox - Jan 13 2013
The server starts lagging when there are too much people talking on the microphone, or crash when worse.
RE: Servers are lagging real bad - i cri everytiem - Jan 13 2013
Matt, post: 83851, member: 178 Wrote:Pretty sure this is definitely a Comcast problem now. You have 88ms at your second hop, when the usual should be around 10-30ms.After the tracert, I joined ROD scrim server and no lag at all so I would say it's not comcast.
Here is from a previous tracert of yours:
2 32 ms 29 ms 28 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
and now:
2 83 ms 88 ms 84 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
also:
8 237 ms 314 ms 235 ms as3491-pe01.ashburn.va.ibone.comcast.net [75.149.228.78]
which is before WebNX's network (transit provider pccwbtn.net)
RE: Servers are lagging real bad - M. Bison - Jan 13 2013
DK, post: 83864, member: 3039 Wrote:After the tracert, I joined ROD scrim server and no lag at all so I would say it's not comcast.I don't think you understand how the internet works.
The route comcast is using to get to us is congested (not surprising for a cable provider). That doesn't mean all of comcast's routes or internet exchange points are congested. Comcast is using different backbones and/or routes to get to ROD's server, and these routes may not be congested.
RE: Servers are lagging real bad - Matt - Jan 14 2013
DK your tracert is showing higher pings to basically every Comcast hop than it was before.
Old tracert
Quote:1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 29 ms 28 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
3 28 ms 17 ms 16 ms xe-2-1-0-32767-sur01.eatontown.nj.panjde.comcast.net [68.87.214.129]
4 17 ms 10 ms 12 ms xe-1-1-1-0-ar03.eastwindsor.nj.panjde.comcast.net [68.85.62.77]
5 13 ms 12 ms 13 ms 68.86.152.113
6 20 ms 19 ms 35 ms pos-4-0-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.93.233]
7 34 ms 47 ms 34 ms he-4-11-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.186]
8 53 ms 52 ms 50 ms pos-1-3-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.157]
New tracert
Quote:1 1 ms <1 ms <1 ms 192.168.1.1
2 83 ms 88 ms 84 ms c-68-83-22-1.hsd1.nj.comcast.net [68.83.22.1]
3 71 ms 68 ms 70 ms xe-2-1-0-32767-sur01.eatontown.nj.panjde.comcast.net [68.87.214.129]
4 66 ms 64 ms 77 ms xe-1-1-1-0-ar03.eastwindsor.nj.panjde.comcast.net [68.85.62.77]
5 74 ms 72 ms 78 ms 68.86.152.113
6 81 ms 87 ms 76 ms pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.157]
7 72 ms 75 ms 79 ms be-10-pe04.ashburn.va.ibone.comcast.net [68.86.84.202]
8 237 ms 314 ms 235 ms as3491-pe01.ashburn.va.ibone.comcast.net [75.149.228.78]
They're all Comcast hops.