Sudden Boot

[fbWldcat]

AH has been VERY warpy, and it is starting to show up in regular internet use, too.
This was taken right after a sudden boot, no "Lost UDP switch to TCP" or anything.
I know the target isn't the server, I just wanted to send packets to a site. Hitechcreations was the first one to come to mind.
Where is it going wrong? It looked like the 17th and 15th hops were the most troublesome.

Target Name: www.hitechcreations.com
         IP: 70.85.193.18
  Date/Time: 6/26/2011 9:21:31 PM to 6/26/2011 9:22:56 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    18   3  16.7   0  12   3  [192.168.0.1]
 2    18   3  16.7   8  50  15  CPE-76-177-124-1.natcky.res.rr.com [76.177.124.1]
 3    18   3  16.7   8  80  14  gig0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
 4    18   3  16.7   7  67  13  ae11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
 5    18   3  16.7  28  78  33  ae8.chcgill3-rtr1.kc.rr.com [65.28.199.197]
 6    18   3  16.7  27 108  39  ae-5-1.cr0.chi30.tbone.rr.com [66.109.6.112]
 7    18   3  16.7  27  34  30  ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
 8    18   3  16.7  35 109  47  xe-10-3-0.edge2.Chicago2.Level3.net [4.59.28.113]
 9    18   3  16.7  29  41  35  vlan52.ebr2.Chicago2.Level3.n et [4.69.138.190]
10    18   4  22.2  48  58  53  ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]
11    18   3  16.7  49 105  56  ae-91-91.csw4.Dallas1.Level3.net [4.69.151.161]
12    18   3  16.7  49  93  59  ae-4-90.edge4.Dallas3.Level3.net [4.69.145.205]
13    18   3  16.7  49  63  55  THE-PLANET.edge4.Dallas3.Level3.net [4.59.32.30]
14    18   3  16.7  47 213  62  te2-3.dsr01.dllstx3.networklayer.com [70.87.255.34]
15    18  18 100.0   0   0   0   [-]
16    18   3  16.7  48  79  52  po1.car03.dllstx5.networklaye r.com [70.87.254.18]
17    18   2  11.1  48 207  59  12.c1.5546.static.theplanet.c om [70.85.193.18]

[willy928]

I will tell you that 14, 16, and 17 are known troublesome IP's and hacking IP"s and on a permanent ban from a number of server farms and racks including mine.

[Skuzzy]

That is the WEB server location.  Try 206.16.60.38 for a game server to ping to.

[fbWldcat]

That is the WEB server location.  Try 206.16.60.38 for a game server to ping to.

I was just shooting to get a plot before the signal went back to normal. I'll get one for the game server as soon as I can. (On my phone atm).

[fbWldcat]

Alrighty, I just took this. 200 traces at one trace per second.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 6/28/2011 8:40:35 PM to 6/28/2011 8:43:57 PM

Hop Sent Err PL% Min Max Avg  Host Name / [IP]
 1   200   0 0.0   0 171  27  [192.168.0.1]
 2   200   0 0.0   8 149  29  CPE-76-177-124-1.natcky.res.rr.com [76.177.124.1]
 3   200   0 0.0   8 157  26  gig0-0-0.vrslky-mx41.natcky.rr.com [65.28.198.217]
 4   200   0 0.0   9 103  20  ae11.hdbgky-mx41.natcky.rr.com [65.28.199.109]
 5   200   0 0.0  29  95  36  ae8.chcgill3-rtr1.kc.rr.com [65.28.199.197]
 6   200   0 0.0  27  76  34  ae-5-1.cr0.chi30.tbone.rr.com [66.109.6.112]
 7   200   0 0.0  28  67  34  ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
 8   200   0 0.0  27  81  35  216.156.72.157.ptr.us.xo.net [216.156.72.157]
 9   200   0 0.0  28 114  36  206.111.2.90.ptr.us.xo.net [206.111.2.90]
10   200   0 0.0  55  91  58  cr2.cgcil.ip.att.net [12.122.81.98]
11   200   0 0.0  55  91  59  cr2.sl9mo.ip.att.net [12.122.2.22]
12   200   0 0.0  55 111  60  cr2.kc9mo.ip.att.net [12.122.28.89]
13   200   0 0.0  54  89  58  cr1.dlstx.ip.att.net [12.122.28.85]
14   200   0 0.0  53 191  60  gar23.dlstx.ip.att.net [12.122.139.153]
15   200   0 0.0  54 319  61  12-122-254-190.attens.net [12.122.254.190]
16   200   0 0.0  55 265  61  mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]
17   200   0 0.0  53  65  57  [206.16.60.38]

[1701E]

Um, maybe I'm reading it wrong, but an average of 27ms on the Router with spikes up to 171?  That seems like an issue in itself.  Never had good times if it went over 1ms (spikes of 2 on a busy day).

[fbWldcat]

Um, maybe I'm reading it wrong, but an average of 27ms on the Router with spikes up to 171?  That seems like an issue in itself.  Never had good times if it went over 1ms (spikes of 2 on a busy day).

Well, we took out our wireless and had put the connection straight into our comp. Well, that was great, until one day I woke up and the internet WOULD NOT WORK AT ALL. They had a tech come out (Very good tech, very thorough, very smart, good family friend). He finds some possible problems. WELL, he plugs in a device and sees no packet loss, nothing wrong at all. CLEAN AS A WHISTLE. But the Internet still wouldn't work on the comp. He changed out routers and rebooted the comp, nothing worked. He left, told us it was a coding problem that THEY had to fix on their server, he told the HQ and they were going to have a guy recode some stuff. A week later, we called Time Warner and they told us they had no record of ANY of this happening. They told us they were going to send out another tech. We said no thanks, and went back to wireless. We entered the password and now the comp works well and so does the internet. The internet does seem laggy at times (ESPECIALLY when playing Black Ops [I will notice it while playing AH, also]). It spikes really bad, sometimes bad enough to boot me from PSonline and AH. It just doesn't seem normal anymore to have internet that doesn't work like crap sometimes. I've grown used to it. But yeah, the original problem had the best tech in our area stumped.

[fbWldcat]

And yes, I know that wireless is a gambling system to work with, that's why we tried direct wiring and it failed.