Lag spikes, overall internet, not wow, badly need help.

[Buckeye]

Okay so my problem is random ms spikes that go on 24/7. I called my ISP this week once I got back from college to get a technician out here to solve the problem but they told me that because it's a latency issue they might not have to fix it so I'm trying to get answers from anyone. Here is the issue:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Kyle>ping -t google.com

Pinging google.com [74.125.225.48] with 32 bytes of data:
Reply from 74.125.225.48: bytes=32 time=51ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=49ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=51ms TTL=50
Reply from 74.125.225.48: bytes=32 time=247ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Request timed out.
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=49ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Request timed out.
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=538ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=43ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=440ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1360ms TTL=50
Reply from 74.125.225.48: bytes=32 time=53ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1027ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=52ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=693ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=49ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1722ms TTL=50
Reply from 74.125.225.48: bytes=32 time=77ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=63ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=57ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=55ms TTL=50
Reply from 74.125.225.48: bytes=32 time=50ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=44ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=53ms TTL=50
Reply from 74.125.225.48: bytes=32 time=61ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=750ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=735ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=49ms TTL=50
Reply from 74.125.225.48: bytes=32 time=703ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1522ms TTL=50
Reply from 74.125.225.48: bytes=32 time=54ms TTL=50
Reply from 74.125.225.48: bytes=32 time=43ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=50ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=50ms TTL=50
Reply from 74.125.225.48: bytes=32 time=46ms TTL=50
Reply from 74.125.225.48: bytes=32 time=47ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Reply from 74.125.225.48: bytes=32 time=48ms TTL=50
Reply from 74.125.225.48: bytes=32 time=45ms TTL=50
Request timed out.

Ping statistics for 74.125.225.48:
Packets: Sent = 167, Received = 164, Lost = 3 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 1722ms, Average = 103ms
Control-C
^C
C:\Users\Kyle>
C:\Users\Kyle>

I've had this problem for a very long time and have had it while we were with Time Warner and now with WOW. These spikes happen at the same time on all computers on our network. IT IS NOT A COMPUTER ISSUE, it is the network. I'm computer savy enough to identify most problems but I have no networking experience and don't know a lot about the specifics of internet connections so that is why I'm seeking help. If anyone knows what my issue is please help!

[Fuzzykins]

Have you consistently had the same router since the issues have started and now?
Also, putting this here for my own reference. Ignore it. >.>

Reply from 74.125.225.48: bytes=32 time=247ms TTL=50
Reply from 74.125.225.48: bytes=32 time=538ms TTL=50
Reply from 74.125.225.48: bytes=32 time=440ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1360ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1027ms TTL=50
Reply from 74.125.225.48: bytes=32 time=693ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1722ms TTL=50
Reply from 74.125.225.48: bytes=32 time=750ms TTL=50
Reply from 74.125.225.48: bytes=32 time=735ms TTL=50
Reply from 74.125.225.48: bytes=32 time=1522ms TTL=50

[blazzin]

i have seen this problem many times
most of the time its a issue with routing block that you and all your neighbors are connected to
getting your isp to fix it will be a huge issue
ask to put up to a higher tech and request a trace recording on your line
normally takes about 3-4 days of readings to pin down the issue
its pricey hardware for your isp to replace or fix
remember your paying for a service, if they try to give you a runaround like mine did
tell them your going to get a outsource service to fix it if they don't resolve it in a timely manner
that will be billed to them
this will get them hopping to fix it fast
i only found this out after 9 mo's of runaround and the person that suggested it to me was one of there own tech's
next thing i know i got there top trouble shooter at me door and it was fixed within 48 hrs

and update your OS to WINDOWS7 looks to me like your sill using XP,unless your hardware doesn't support it

[Buckeye]

Have you consistently had the same router since the issues have started and now?
Also, putting this here for my own reference. Ignore it. >.>

No we swapped routers and the issue still persists.

Also thanks Blazzin I figured it was a problem with a piece of tech outside the house but had no clue what specifically.

---------- Post added 2011-06-08 at 03:22 PM ----------

Bump for anymore information.