unreasonable lag since last maintenance

[Tiggy]

I was lagging like this before the maintenance, I've had no problems since then. Dunno what's happening to you guys.

[Noahlimits]

I'm still lagging a tiny bit, but way less since the last maintenance.

[_XIII]

It seems that every maintenance they resolve some of the peoples lagging problems but at the same time manages to cause a completely entire group to have the lag.

[Seaside8]

Still having the issue :/

[Jockiechon]

I've been skipping frames like I am some sort of bad stop-motion animation.
This never happened until recently...

[RuneBlade]

I've always had some lag, but never this bad!

Tracing route to 199.91.189.18 over a maximum of 30 hops

1 629 ms 141 ms 27 ms cpe-108-184-240-1.socal.res.rr.com [108.184.240.1]
2 12 ms 14 ms 36 ms tge0-7-0-5.vnnzca2401h.socal.rr.com [76.166.5.133]
3 22 ms 13 ms 30 ms agg11.vnnycajz01r.socal.rr.com [72.129.14.96]
4 34 ms 52 ms 14 ms agg29.lsancarc01r.socal.rr.com [72.129.13.0]
5 27 ms 17 ms 13 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.212]
6 13 ms 17 ms 32 ms 107.14.19.138
7 28 ms 32 ms 104 ms 66.109.9.122
8 95 ms 88 ms 99 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
9 89 ms 89 ms 109 ms ae-72-72.ebr2.LosAngeles1.Level3.net [4.69.137.21]
10 88 ms 94 ms 90 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
11 87 ms 86 ms 85 ms ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169]
12 99 ms 90 ms 87 ms ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162]
13 115 ms 89 ms 89 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
14 95 ms 96 ms 96 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
15 99 ms 89 ms 111 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
16 * * * Request timed out.
17 91 ms 87 ms 92 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
18 107 ms 118 ms 113 ms 10.2.2.1
19 135 ms 122 ms 120 ms 192.34.76.2
20 125 ms 150 ms 136 ms 199.91.189.234
21 * 105 ms 141 ms 199.91.189.18

Trace complete.

[Seaside8]

Can I get a post from a moderator addressing the issue? Why is it that it takes them less than 15 minutes to shutdown posts that have "already been solved," but they just leave us to complain among ourselves when there's an issue that has not been addressed?

Can we at least get an acknowledgement of the problem?

[Royel]

My tracert always shows problems at Montreal1.Level3.net and Montreal2.Level3.net during peak times.
I'm in upstate NY and have TWC.

I finally decided to capture it on video because it happens every night and seemingly is getting worse...
http://www.youtube.com/watch?v=HvkL3M9zsCU

[Sushi]

find the ip of your servers on this website http://www.arrstatus.com/ and ping it , open the command window by type in the search box cmd, and then type: ping xxx.xx.xxx.xx -t (note this is an infinity loop,so stop it manually with ctrl-c)
I think most of you who live in the US don't have latency problem but the package lost problem. check the result of the percentage of the packet lost.

[Royel]

the command "tracert xxx.xx.xxx.xx" will show you the route that the signal takes to get from your computer to the server and the ping of each individual router along the way. If you run that a few times during prime time in your area, one or more of the addresses will have lost packets and/or unusually high latency likely from data loss. I pasted my results below for the diabolos server.


Tracing route to 199.91.189.38 over a maximum of 30 hops

1 39 ms 17 ms 32 ms
2 18 ms 11 ms 11 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
3 12 ms 11 ms 13 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
4 15 ms 13 ms 12 ms rdc-74-76-243-78.alb.east.twcable.com [74.76.243.78]
5 25 ms 23 ms 22 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 20 ms 23 ms 23 ms 107.14.19.26
7 21 ms 22 ms 22 ms 66.109.1.36
8 21 ms * 20 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 35 ms 36 ms 37 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
10 51 ms 34 ms 34 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11 155 ms 214 ms 236 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 29 ms * 30 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 37 ms 31 ms 31 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 42 ms 44 ms 79 ms 10.2.2.1
15 * 45 ms 43 ms 192.34.76.2
16 43 ms 44 ms 44 ms 199.91.189.234
17 44 ms 43 ms 41 ms 199.91.189.38

Trace complete.

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 41 ms 27 ms 16 ms
2 12 ms 31 ms 12 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
3 27 ms 11 ms 13 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
4 13 ms 44 ms 11 ms rdc-74-76-243-78.alb.east.twcable.com [74.76.243.78]
5 27 ms 22 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 25 ms 23 ms 23 ms 107.14.19.26
7 60 ms 37 ms 22 ms 66.109.1.36
8 22 ms 21 ms 22 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 32 ms 52 ms 33 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
10 33 ms 35 ms 34 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11 29 ms 28 ms 30 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 * * 93 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 30 ms 32 ms 33 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 45 ms 44 ms 48 ms 10.2.2.1
15 56 ms 42 ms 44 ms 192.34.76.2
16 43 ms 44 ms 44 ms 199.91.189.234
17 42 ms 43 ms 44 ms 199.91.189.38

Trace complete.