Report Lag Here - Page 4

Shotgun Opera · 08-18-2009, 03:56 PM

game time 3:55 got home from work a little while ago and server 1 is lagging

Shotgun Opera · 08-18-2009, 06:33 PM

well game time 6:32 lag just hit and its not just me I'm just the only one not too lazy to report it.

08-18-2009, 07:05 PM

game time 19:00 and its been laggin badly for about a half hour now :/

Shotgun Opera · 08-18-2009, 08:38 PM

game time 8:38 pm and its lagging on S1 and not on S2....

Shotgun Opera · 08-18-2009, 09:17 PM

Well the lag went away and there was much rejoicing..... Unfortunately it was only gone for 10 minutes.

08-22-2009, 02:29 PM

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

C:\Users\Tyler>ping racewarkingdoms.com

Pinging racewarkingdoms.com [64.34.186.9] with 32 bytes of data:

Reply from 64.34.186.9: bytes=32 time=33ms TTL=114
Reply from 64.34.186.9: bytes=32 time=30ms TTL=114
Reply from 64.34.186.9: bytes=32 time=32ms TTL=114
Reply from 64.34.186.9: bytes=32 time=31ms TTL=114

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

C:\Users\Tyler>tracert racewarkingdoms.com

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

1 * * * Request timed out.
2 9 ms 9 ms 11 ms 68.87.173.193
3 8 ms 9 ms 16 ms te-2-1-ar01.pittsburgh.pa.pitt.comcast.net [68.8
6.100.85]
4 24 ms 22 ms 23 ms te-2-0-0-4-cr01.chicago.il.ibone.comcast.net [68
.86.90.97]
5 22 ms 21 ms 21 ms xe-10-1-0.edge1.Chicago2.Level3.net [4.71.248.17
]
6 20 ms 22 ms 21 ms vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]
7 30 ms 29 ms 29 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

8 31 ms 36 ms 35 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
54]
9 30 ms 27 ms 28 ms ae-3-89.edge2.Washington3.Level3.net [4.68.17.14
0]
10 31 ms 130 ms 32 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
11 31 ms 32 ms 34 ms 216.187.120.253
12 29 ms 40 ms 33 ms 216.187.120.238
13 31 ms 30 ms 34 ms mail.glitchless.com [64.34.186.9]

Trace complete.

C:\Users\Tyler>

It is 3:30 est and the lag is really bad right now on S1.

08-22-2009, 02:38 PM

.

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

1 18 ms 14 ms 7 ms 10.151.0.1
2 6 ms 6 ms 10 ms 172.23.9.109
3 22 ms 19 ms 18 ms 172.23.9.1
4 40 ms 32 ms 37 ms xe-10-1-0.bar1.Cleveland1.Level3.net [4.53.196.1
]
5 37 ms 37 ms 35 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190
]
6 40 ms 33 ms 36 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
7 33 ms 31 ms 31 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
8 34 ms 33 ms 30 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
9 * * * Request timed out.
10 * * * Request timed out.
11 33 ms 42 ms 41 ms mail.glitchless.com [64.34.186.9]

Trace complete.

Heres is a damn tracer and I'm sure you going to tell me its not RWK laggin well funny how everyone is laggin and not just me.

08-22-2009, 02:44 PM

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

C:\Users\Tyler>ping racewarkingdoms.com

Pinging racewarkingdoms.com [64.34.186.9] with 32 bytes of data:

Reply from 64.34.186.9: bytes=32 time=33ms TTL=114
Reply from 64.34.186.9: bytes=32 time=30ms TTL=114
Reply from 64.34.186.9: bytes=32 time=32ms TTL=114
Reply from 64.34.186.9: bytes=32 time=31ms TTL=114

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

C:\Users\Tyler>tracert racewarkingdoms.com

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

1 * * * Request timed out.
2 9 ms 9 ms 11 ms 68.87.173.193
3 8 ms 9 ms 16 ms te-2-1-ar01.pittsburgh.pa.pitt.comcast.net [68.8
6.100.85]
4 24 ms 22 ms 23 ms te-2-0-0-4-cr01.chicago.il.ibone.comcast.net [68
.86.90.97]
5 22 ms 21 ms 21 ms xe-10-1-0.edge1.Chicago2.Level3.net [4.71.248.17
]
6 20 ms 22 ms 21 ms vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]
7 30 ms 29 ms 29 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]

8 31 ms 36 ms 35 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.1
54]
9 30 ms 27 ms 28 ms ae-3-89.edge2.Washington3.Level3.net [4.68.17.14
0]
10 31 ms 130 ms 32 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
11 31 ms 32 ms 34 ms 216.187.120.253
12 29 ms 40 ms 33 ms 216.187.120.238
13 31 ms 30 ms 34 ms mail.glitchless.com [64.34.186.9]

Trace complete.

C:\Users\Tyler>

Lag is gone right now and here is another tracert

08-23-2009, 06:23 PM

so what is the sense in posting tracer's when nothing happens LAG IS BACK and i'm not posting a tracer just letting you know if you give a crap that the lag is back.

Jimcav · 08-23-2009, 09:14 PM

It might be best to just post when you happen to notice a change in any direction, things get significantly better or worse, along with the date and exact time it happens. If anyone at the server farm gets those data it may be instructive to try correlating them with events on or with the server for some insight into when performance changes. Or, if seeing nothing obvious being done makes you get even more frustrated than the lag itself, it's probably best to just avoid this forum altogether. Getting more aggravated just detracts from your remaining enjoyment of the game without any compensating benefits.

Northern Silence · 08-23-2009, 09:48 PM

1. quit bitching and being an *******, you expect bitching to get anything fixed?

2. Post when lag began
3. Check if s2 is lagging too.
4. See if anyone else on the server is lagging.
5. post a tracert if not EVERYBODY says it is lagging, and 1-2 people does not = everybody.

Khyron · 08-25-2009, 12:27 PM

here mine i also checked S2 as you stated and S2 is fine while S1 lag heh

Microsoft Windows [version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. Tous droits réservés.

C:\Users\Sébastien>tracert racewarkingdoms
Impossible de résoudre le nom du système cible racewarkingdoms.

C:\Users\Sébastien>tracert racewarkingdoms.com

Détermination de l'itinéraire vers racewarkingdoms.com [64.34.186.9]
avec un maximum de 30 sauts*:

1 <1 ms <1 ms <1 ms PC-de-S [192.168.2.1]
2 7 ms 8 ms 6 ms VTC-A-CAT.csc.com [20.1.0.1]
3 8 ms 16 ms 10 ms cnq2-14.cablevision.qc.ca [24.212.2.14]
4 7 ms 7 ms 15 ms cnq3-25.cablevision.qc.ca [24.212.3.25]
5 14 ms 11 ms 12 ms 67.69.244.153
6 13 ms 12 ms 14 ms core2-ottawa23_POS13-1-0.net.bell.ca [64.230.164
.17]
7 15 ms 17 ms 18 ms Ncore3-montreal02_POS0-4-0-0.net.bell.ca [64.230
.147.133]
8 14 ms 15 ms 15 ms core4-montreal02_POS4-0-0_core.net.bell.ca [64.2
30.168.222]
9 30 ms 24 ms 22 ms core1-newyork83_pos_4_0_0.net.bell.ca [64.230.20
7.134]
10 24 ms 24 ms 24 ms bx2-newyork83_POS3-0.net.bell.ca [206.108.103.19
4]
11 24 ms 31 ms 25 ms dcr4-so-3-0-0.newyork.savvis.net [216.89.91.133]

12 30 ms 27 ms 26 ms cr2-tengig-0-7-0-0.Washington.savvis.net [204.70
.196.106]
13 28 ms 28 ms 28 ms 204.70.197.245
14 33 ms 32 ms 28 ms cpr2-ge-5-0.virginiaequinix.savvis.net [204.70.1
93.101]
15 30 ms 29 ms 30 ms 208.173.10.194
16 30 ms 31 ms 28 ms 10ge.ten1-2.wdc-sp2-cor-1.peer1.net [216.187.115
.234]
17 31 ms 31 ms 29 ms 216.187.120.238
18 31 ms 28 ms 29 ms racewarkingdoms.com [64.34.186.9]

Itinéraire déterminé.

C:\Users\Sébastien>

08-25-2009, 12:42 PM

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Mike>tracert racewarkingdoms.com

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

1 34 ms 35 ms 54 ms 10.232.96.1
2 35 ms 34 ms 34 ms 209.115.156.205
3 36 ms 35 ms 34 ms 209.115.197.49
4 56 ms 36 ms 35 ms 154.11.10.205
5 59 ms 47 ms 46 ms 154.11.10.150
6 46 ms 46 ms 45 ms 204.239.129.213
7 48 ms 46 ms 46 ms oc48.so-2-0-0.van-hc21e-cor-1.peer1.net [216.187
.89.97]
8 92 ms 90 ms 91 ms oc48.so-3-0-2.tor-151f-cor-1.peer1.net [216.187.
114.138]
9 99 ms 98 ms 98 ms oc48-po3-0.mtl-bvh-cor-1.peer1.net [216.187.114.
198]
10 99 ms 99 ms 98 ms 10ge.xe-0-0-0.mtl-bvh-cor-1.peer1.net [216.187.1
15.85]
11 107 ms 107 ms 106 ms oc192.xe-4-0-0.nyc-telx-dis-1.peer1.net [216.187
.115.54]
12 112 ms 111 ms 113 ms 10ge.ten1-2.wdc-sp2-cor-2.peer1.net [216.187.115
.222]
13 113 ms 113 ms 112 ms 216.187.120.253
14 111 ms 112 ms 112 ms 216.187.120.234
15 112 ms 113 ms 113 ms mail.glitchless.com [64.34.186.9]

Trace complete.

C:\Documents and Settings\Mike>

08-25-2009, 12:43 PM

it seems my signal no longer goes through the east coast, it bounces from vancouver to toronto. Current game time is 12:45, lag has been happening for at least the last half an hour.

Homer Stokes · 08-26-2009, 11:55 AM

started tracerts at 11:30am EST and finished at about12:15 pm EST, right after lag ended, but it started up again about 20 min all these tracerts
.racewarkingdoms.com

1 Request timed out.
2 13 ms 12 ms 14 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 12 ms 12 ms 20 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 13 ms 14 ms 18 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 14 ms 14 ms 20 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 25 ms 23 ms 38 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 22 ms 21 ms 22 ms ge-0-3-0.albynywav-rtr03.nyroc.rr.com [24.24.7.1
70]
8 28 ms 24 ms 25 ms xe-11-0-0.bar1.Boston1.Level3.net [4.79.0.69]
9 26 ms 26 ms 26 ms ae-0-11.bar2.Boston1.Level3.net [4.69.140.90]
10 34 ms 30 ms 27 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
11 43 ms 39 ms 54 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

12 41 ms 34 ms 37 ms ae-94-94.csw4.Washington1.Level3.net [4.69.134.1
90]
13 40 ms 41 ms 35 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
14 40 ms 34 ms 35 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
15 Request timed out.
16 Request timed out.
17 41 ms 40 ms 36 ms mail.glitchless.com [64.34.186.9]

rwk2.racewarkingdoms.com
rwk2.racewarkingdoms.com [64.34.186.9]

1 Request timed out.
2 12 ms 14 ms 12 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 31 ms 12 ms 17 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 22 ms 12 ms 12 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 13 ms 12 ms 12 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 22 ms 23 ms 21 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 27 ms 18 ms 18 ms ge-0-3-0.albynywav-rtr03.nyroc.rr.com [24.24.7.1
70]
8 36 ms 23 ms 24 ms xe-11-0-0.bar1.Boston1.Level3.net [4.79.0.69]
9 25 ms 24 ms 38 ms ae-0-11.bar2.Boston1.Level3.net [4.69.140.90]
10 41 ms 29 ms 28 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
11 47 ms 36 ms 34 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

12 45 ms 35 ms 40 ms ae-94-94.csw4.Washington1.Level3.net [4.69.134.1
90]
13 34 ms 35 ms 37 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
14 36 ms 33 ms 34 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
15 * * * Request timed out.
16 * * * Request timed out.
17 34 ms 34 ms 34 ms mail.glitchless.com [64.34.186.9]
google.com
.l.google.com [64.233.169.103]

1 Request timed out.
2 10 ms 13 ms 14 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 13 ms 13 ms 11 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 12 ms 12 ms 13 ms gig0-0-0.albynytry-rtr02.nyroc.rr.com [24.29.39.
161]
5 13 ms 15 ms 22 ms gig1-1-0.albynywav-rtr01.nyroc.rr.com [24.29.37.
45]
6 14 ms 16 ms 15 ms ge-1-0-0.albynywav-rtr03.nyroc.rr.com [24.24.7.2
1]
7 25 ms 19 ms 17 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74]
8 26 ms 24 ms 26 ms ae-4-0.cr0.dca20.tbone.rr.com [66.109.6.28]
9 23 ms 25 ms 25 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
10 31 ms 25 ms 29 ms 66.109.9.66
11 25 ms 24 ms 25 ms 216.239.48.108
12 30 ms 25 ms 24 ms 64.233.175.111
13 35 ms 36 ms 35 ms 72.14.232.25
14 26 ms 28 ms 25 ms yo-in-f103.google.com [64.233.169.103

THIS TRACERT WAS STARTED WHEN LAG STARTED TO COME BACK
racewarkingdoms.com [64.34.186.9]

1 Request timed out.
2 14 ms 13 ms 12 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 11 ms 10 ms 12 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 15 ms 11 ms 12 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 13 ms 12 ms 19 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 22 ms 22 ms 21 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 * 23 ms 21 ms ge-7-3-0.albynywav-rtr03.nyroc.rr.com [24.24.7.1
74]
8 24 ms 29 ms 23 ms xe-11-0-0.bar1.Boston1.Level3.net [4.79.0.69]
9 27 ms 24 ms 25 ms ae-0-11.bar2.Boston1.Level3.net [4.69.140.90]
10 29 ms 31 ms 31 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
11 33 ms 35 ms 37 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

12 40 ms 37 ms 35 ms ae-94-94.csw4.Washington1.Level3.net [4.69.134.1
90]
13 36 ms 35 ms 48 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
14 37 ms 35 ms 38 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
15 Request timed out.
16 Request timed out.
17 36 ms 34 ms 34 ms mail.glitchless.com [64.34.186.9]

THIS TRACERT SHOWS, WHEN I WAS CLICKING, A SPOT WHERE "CHAT PUKE" HAPPENED I ENDED UP WITH ALL YELLOW ASH ITEMS DELETED FROM MY SCREEN
racewarkingdoms.com
racewarkingdoms.com [64.34.186.9]
1 * * * Request timed out.
2 14 ms 12 ms 12 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 12 ms 13 ms 11 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 11 ms 12 ms 13 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 12 ms 13 ms 11 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 337 ms 19 ms 33 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 19 ms 18 ms 19 ms ge-0-3-0.albynywav-rtr03.nyroc.rr.com [24.24.7.1
70]
8 24 ms 24 ms 25 ms xe-10-3-0.bar1.Boston1.Level3.net [4.79.0.73]
9 25 ms 25 ms 35 ms ae-0-11.bar2.Boston1.Level3.net [4.69.140.90]
10 33 ms 30 ms 27 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
11 48 ms 35 ms 35 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

12 46 ms 35 ms 35 ms ae-94-94.csw4.Washington1.Level3.net [4.69.134.1
90]
13 34 ms 35 ms 36 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
14 34 ms 35 ms 34 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
15 Request timed out.
16 Request timed out.
17 37 ms 33 ms 35 ms mail.glitchless.com [64.34.186.9]
tracert .google.com
.l.google.com [64.233.169.99]
1 * * * Request timed out.
2 13 ms 11 ms 17 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 12 ms 13 ms 12 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 13 ms 13 ms 15 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 14 ms 15 ms 16 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 20 ms 18 ms 19 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 42 ms 41 ms 38 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
8 41 ms 40 ms 78 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
9 46 ms 36 ms 39 ms 74.125.48.109
10 38 ms 36 ms 38 ms 209.85.251.38
11 41 ms 101 ms 87 ms 209.85.248.222
12 48 ms 40 ms 40 ms 64.233.175.111
13 40 ms 50 ms 50 ms 72.14.232.25
14 50 ms 43 ms 42 ms yo-in-f99.google.com [64.233.169.99]
>tracert .google.com
Tracing route to .l.google.com [64.233.169.99]
1 Request timed out.
2 13 ms 12 ms 12 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 12 ms 9 ms 9 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 10 ms 12 ms 12 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 25 ms 17 ms 12 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 21 ms 26 ms 21 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 38 ms 38 ms 39 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
8 38 ms 44 ms 38 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
9 44 ms 40 ms 37 ms 74.125.48.109
10 38 ms 42 ms 76 ms 209.85.251.38
11 44 ms 38 ms 41 ms 209.85.242.209
12 56 ms 39 ms 41 ms 64.233.175.109
13 40 ms 52 ms 50 ms 216.239.49.145
14 41 ms 41 ms 41 ms yo-in-f99.google.com [64.233.169.99]
tracert .racewarkingdoms.com
.racewarkingdoms.com [64.34.186.9]

1 Request timed out.
2 11 ms 13 ms 15 ms cable1-0.albynyqby-ar402.nyroc.rr.com [67.240.32
.1]
3 10 ms 14 ms 16 ms gig2-6.albynyqby-swt01.nyroc.rr.com [24.29.39.20
1]
4 13 ms 14 ms 15 ms gig4-0-0.albynysat-rtr02.nyroc.rr.com [24.29.39.
165]
5 16 ms 13 ms 12 ms gig6-0-0.albynywav-rtr02.nyroc.rr.com [24.29.37.
33]
6 21 ms 24 ms 22 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.
25]
7 19 ms 19 ms 23 ms ge-7-3-0.albynywav-rtr03.nyroc.rr.com [24.24.7.1
74]
8 26 ms 25 ms 25 ms xe-11-0-0.bar1.Boston1.Level3.net [4.79.0.69]
9 25 ms 25 ms 25 ms ae-0-11.bar2.Boston1.Level3.net [4.69.140.90]
10 29 ms 31 ms 28 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98]
11 44 ms 46 ms 52 ms ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]

12 37 ms 37 ms 35 ms ae-94-94.csw4.Washington1.Level3.net [4.69.134.1
90]
13 41 ms 34 ms 36 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.20
4]
14 35 ms 36 ms 35 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
15 Request timed out.
16 Request timed out.
17 44 ms 34 ms 35 ms mail.glitchless.com [64.34.186.9]

Jimcav · 08-26-2009, 05:07 PM

The traces don't show any difference with or without lag in the game, which is consistent with what players have seen before. I think running them is pointless, it's probably better to just report the date and time you notice lagging begin or end.

08-28-2009, 07:52 PM

It is 8:51 EST and S1 is down, I cannot even log back in. Minor lag started around 8:35 and around 8:40 the game would do nothing but say Request Timed Out.

08-28-2009, 08:20 PM

Does anyone online know what is going on? There are a lot of people confused about what happened. It's now 9:20 EST and still noone can log.

08-28-2009, 10:31 PM

It's 11:30 EST and S1 is down again. I, along with many others are not even able to log on

Shotgun Opera · 08-28-2009, 10:38 PM

well now the server is going down completely at times I have stopped bothering to post when it lags because nothing changes and no one cares.