Code: Select all
« SpeedGuide.net TCP Analyzer Results »
Tested on: 02.18.2011 02:38
IP address: 24.251.xxx.xxx
Client OS: Windows 7
TCP options string: 020405b40103030801010402
MSS: 1460
MTU: 1500
TCP Window: 65536 (NOT multiple of MSS)
RWIN Scaling: 8 bits (2^8=256)
Unscaled RWIN : 256
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2621kbps (328KBytes/s)
BDP limit (500ms): 1049kbps (131KBytes/s)
MTU Discovery: ON
TTL: 122
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
Server #1
Code: Select all
C:\Windows\system32>tracert 199.107.6.200
Tracing route to 199.107.6.200 over a maximum of 30 hops
1 8 ms 8 ms 8 ms 10.81.128.1
2 19 ms 30 ms 18 ms ip68-2-4-5.ph.ph.cox.net [68.2.4.5]
3 10 ms 11 ms 7 ms 70.169.75.118
4 8 ms 8 ms 11 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
5 23 ms 27 ms 29 ms langbprj01-ae0.0.rd.la.cox.net [68.1.0.232]
6 22 ms 21 ms 21 ms 192.205.37.145
7 84 ms 89 ms 103 ms cr2.la2ca.ip.att.net [12.122.84.218]
8 90 ms 83 ms 82 ms cr1.slkut.ip.att.net [12.122.30.29]
9 83 ms 85 ms 84 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 84 ms 86 ms 85 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 87 ms 87 ms 90 ms cr2.cgcil.ip.att.net [12.122.2.54]
12 87 ms 94 ms 92 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 86 ms 83 ms 93 ms cr83.n54ny.ip.att.net [12.122.105.50]
14 84 ms 83 ms 91 ms gar20.n54ny.ip.att.net [12.123.2.13]
15 86 ms 83 ms 83 ms 12-122-254-114.attens.net [12.122.254.114]
16 85 ms 83 ms 86 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
Trace complete.
Code: Select all
C:\Windows\system32>tracert 199.107.6.192
Tracing route to 199.107.6.192 over a maximum of 30 hops
1 8 ms 6 ms 7 ms 10.81.128.1
2 9 ms 13 ms 6 ms ip68-2-4-5.ph.ph.cox.net [68.2.4.5]
3 8 ms 10 ms 8 ms 70.169.75.118
4 7 ms 17 ms 11 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
5 45 ms 77 ms 22 ms langbprj01-ae0.0.rd.la.cox.net [68.1.0.232]
6 30 ms 20 ms 25 ms 192.205.37.145
7 85 ms 87 ms 84 ms cr2.la2ca.ip.att.net [12.122.84.218]
8 82 ms 82 ms 84 ms cr1.slkut.ip.att.net [12.122.30.29]
9 83 ms 83 ms 83 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 86 ms 82 ms 140 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 83 ms 86 ms 83 ms cr2.cgcil.ip.att.net [12.122.2.54]
12 124 ms 93 ms 85 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 82 ms 84 ms 93 ms cr83.n54ny.ip.att.net [12.122.105.50]
14 82 ms 81 ms 83 ms gar20.n54ny.ip.att.net [12.123.2.13]
15 82 ms 89 ms 83 ms 12-122-254-114.attens.net [12.122.254.114]
16 86 ms 85 ms 82 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
Trace complete.
Code: Select all
Tracing route to 199.107.6.180 over a maximum of 30 hops
1 9 ms 10 ms 7 ms 10.81.128.1
2 10 ms 8 ms 7 ms ip68-2-4-5.ph.ph.cox.net [68.2.4.5]
3 37 ms 19 ms 9 ms 70.169.75.118
4 10 ms 9 ms 12 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
5 38 ms 21 ms 23 ms langbprj01-ae0.0.rd.la.cox.net [68.1.0.232]
6 21 ms 22 ms 20 ms 192.205.37.145
7 85 ms 93 ms 91 ms cr2.la2ca.ip.att.net [12.122.84.218]
8 84 ms 91 ms 83 ms cr1.slkut.ip.att.net [12.122.30.29]
9 83 ms 83 ms 86 ms cr2.dvmco.ip.att.net [12.122.30.26]
10 83 ms 82 ms 84 ms cr1.cgcil.ip.att.net [12.122.31.86]
11 86 ms 83 ms 85 ms cr2.cgcil.ip.att.net [12.122.2.54]
12 85 ms 86 ms 84 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 85 ms 87 ms 86 ms cr83.n54ny.ip.att.net [12.122.105.50]
14 84 ms 91 ms 83 ms gar20.n54ny.ip.att.net [12.122.131.249]
15 84 ms 83 ms 89 ms 12-122-254-114.attens.net [12.122.254.114]
16 86 ms 87 ms 112 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.24
0.65.14]
Trace Complete.
Now I know all 3 of these weren't needed as you can see they are all in the same location different ports is probably the only real difference. Clean traces I can't see any type of packet loss on the line.
In game latency is 300, Now I've reset my my network basically back to Windows 7 default. I'll throw a few ping tests up here but obviously the speed of a ping test server on a different network isn't going to tell much.




Now as you can see I have a pretty strong line, I don't have packet loss issues and overall it seems to be fine but over the last month or so something happened and now gaming is barely playable at times. Constant disconnects in game but no where else for instance I can be on skype/Vent/Mumble and in game and the game will look as it's experiencing extreme packet loss. Sometimes it will catch up 30-60 seconds later and there is no DC other times it's just a DC.
It feels like there is some type of throttle or something on sending and receiving only effecting the game. I really don't know if this will be any help or what I can even do about it but it's definitely killing my enjoyment atm.
Here is a quick ping test in case it's something else you would like to see. This has me pretty puzzled and while I'm not really interested in reinstalling my OS I will if I can't determine the issue. I've done everything I can think of to resolve this issue it is possible there isn't one but I figure it can't hurt to let someone else take a stab at it.
Code: Select all
C:\Windows\system32>ping us.login.worldofwarcraft.com -n 25
Pinging us.login.worldofwarcraft.com [208.67.216.145] with 32 bytes of data:
Reply from 208.67.216.145: bytes=32 time=51ms TTL=55
Reply from 208.67.216.145: bytes=32 time=52ms TTL=55
Reply from 208.67.216.145: bytes=32 time=62ms TTL=55
Reply from 208.67.216.145: bytes=32 time=56ms TTL=55
Reply from 208.67.216.145: bytes=32 time=51ms TTL=55
Reply from 208.67.216.145: bytes=32 time=90ms TTL=55
Reply from 208.67.216.145: bytes=32 time=51ms TTL=55
Reply from 208.67.216.145: bytes=32 time=52ms TTL=55
Reply from 208.67.216.145: bytes=32 time=50ms TTL=55
Reply from 208.67.216.145: bytes=32 time=56ms TTL=55
Reply from 208.67.216.145: bytes=32 time=50ms TTL=55
Reply from 208.67.216.145: bytes=32 time=56ms TTL=55
Reply from 208.67.216.145: bytes=32 time=60ms TTL=55
Reply from 208.67.216.145: bytes=32 time=57ms TTL=55
Reply from 208.67.216.145: bytes=32 time=57ms TTL=55
Reply from 208.67.216.145: bytes=32 time=51ms TTL=55
Reply from 208.67.216.145: bytes=32 time=75ms TTL=55
Reply from 208.67.216.145: bytes=32 time=50ms TTL=55
Reply from 208.67.216.145: bytes=32 time=51ms TTL=55
Reply from 208.67.216.145: bytes=32 time=57ms TTL=55
Reply from 208.67.216.145: bytes=32 time=49ms TTL=55
Reply from 208.67.216.145: bytes=32 time=50ms TTL=55
Reply from 208.67.216.145: bytes=32 time=51ms TTL=55
Reply from 208.67.216.145: bytes=32 time=52ms TTL=55
Reply from 208.67.216.145: bytes=32 time=52ms TTL=55
Ping statistics for 208.67.216.145:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 90ms, Average = 55ms