Ive notice a problem with my hitting a damaging targets over the last couple of weeks. I know the game froze up last night, but this has been more of an ongoing problem. I think it may be a lag problem...but heck, I have no idea how this voodoo computer stuff works...
HT< Can you look at this ping plot and tell me if it looks alright? I have comcast and they are the only provider in town. If there is a problem with them... will they be able to fix it, and whats the best way to go about it.... climbing a bell tower has not been ruled out as a possiblity.
Is Hop 10 an issue... ???
Target Name: 206.16.60.38.
IP: 206.16.60.38
Date/Time: 2/2/2009 11:10:28 AM to 2/2/2009 11:11:58 AM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [10.0.1.1]
2 7 ms 7 ms 9 ms 5 ms 5 ms 16 ms 7 ms 8 ms 7 ms 8 ms [73.204.161.1]
3 7 ms 9 ms 7 ms 9 ms 17 ms 7 ms 7 ms 7 ms 7 ms 8 ms ge-2-3-ur01.mayslanding.nj.panjde.comcast.net [68.85.195.33]
4 8 ms 5 ms 5 ms 7 ms 17 ms 5 ms 9 ms 8 ms 7 ms 14 ms te-2-2-ar01.absecon.nj.panjde.comcast.net [68.86.210.46]
5 10 ms 11 ms 10 ms 10 ms 14 ms 19 ms 10 ms 11 ms 9 ms 13 ms be-30-crs01.audubon.nj.panjde.comcast.net [68.86.208.22]
6 12 ms 17 ms 12 ms 12 ms 20 ms 17 ms 16 ms 12 ms 19 ms 12 ms [68.85.192.86]
7 11 ms 26 ms 12 ms 14 ms 18 ms 19 ms 15 ms 15 ms 12 ms 11 ms pos-0-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.29]
8 13 ms 15 ms 15 ms 14 ms 28 ms 20 ms 16 ms 13 ms 13 ms 13 ms pos-1-8-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.86.42]
9 13 ms 18 ms 14 ms 28 ms 32 ms 16 ms 14 ms 16 ms 13 ms 12 ms [208.173.138.17]
10 12 ms 12 ms * * * 14 ms 17 ms 13 ms 12 ms * cr1-tengig-0-8-3-0.NewYork.savvis.net [204.70.198.13]
11 15 ms 14 ms 14 ms 15 ms 31 ms 14 ms 13 ms 13 ms 13 ms 12 ms [204.70.197.5]
12 12 ms 13 ms 12 ms 39 ms 26 ms 15 ms 18 ms 13 ms 13 ms 18 ms [192.205.35.9]
13 88 ms 90 ms 88 ms 88 ms 96 ms 90 ms 89 ms 89 ms 95 ms 88 ms tbr1.n54ny.ip.att.net [12.122.88.30]
14 89 ms 90 ms 95 ms 91 ms 90 ms 90 ms 90 ms 88 ms 88 ms 98 ms cr1.n54ny.ip.att.net [12.122.16.201]
15 94 ms 89 ms 94 ms 87 ms 88 ms 89 ms 89 ms 88 ms 91 ms 87 ms cr2.cgcil.ip.att.net [12.122.1.2]
16 90 ms 89 ms 95 ms 90 ms 89 ms 88 ms 90 ms 88 ms 88 ms 88 ms cr2.sl9mo.ip.att.net [12.122.2.22]
17 90 ms 90 ms 95 ms 91 ms 105 ms 95 ms 91 ms 93 ms 92 ms 98 ms cr1.sl9mo.ip.att.net [12.122.2.217]
18 91 ms 87 ms 92 ms 91 ms 88 ms 89 ms 94 ms 88 ms 88 ms 91 ms cr2.dlstx.ip.att.net [12.122.3.221]
19 90 ms 88 ms 95 ms 91 ms 116 ms 89 ms 88 ms 89 ms 88 ms 88 ms gar5.dlstx.ip.att.net [12.122.138.5]
20 91 ms 89 ms 89 ms 94 ms 91 ms 89 ms 90 ms 89 ms 90 ms 90 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
21 89 ms 89 ms 120 ms 89 ms 96 ms 90 ms 98 ms 318 ms 89 ms 88 ms mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
22 90 ms 97 ms 110 ms 89 ms 95 ms 91 ms 91 ms 91 ms 90 ms 90 ms [206.16.60.38]
Ping statistics for 206.16.60.38.
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 89ms, Maximum = 110ms, Average = 93ms
