Here's a quick way to find out where the problem (or should I say BLAME) may lie....
On a Windows computer:
Click on the "start" icon (bottom left corner) --> go to the search box (the ONLY open empty box you can type in) and type in cmd then press enter
A black box will pop up --> type in ping -t cox.com then press enter....
You should see something like this:
C:\Users\Mimi>ping -t cox.com
Pinging cox.com [45.60.49.167] with 32 bytes of data:
Reply from 45.60.49.167: bytes=32 time=121ms TTL=253
Reply from 45.60.49.167: bytes=32 time=122ms TTL=253
Reply from 45.60.49.167: bytes=32 time=122ms TTL=253
Reply from 45.60.49.167: bytes=32 time=123ms TTL=253
Reply from 45.60.49.167: bytes=32 time=121ms TTL=253
Reply from 45.60.49.167: bytes=32 time=123ms TTL=253
Reply from 45.60.49.167: bytes=32 time=121ms TTL=253
Reply from 45.60.49.167: bytes=32 time=120ms TTL=253
Let that run for about 10 minutes or so then press the Ctrl button and, at the same time, press the "C" key on your keyboard --> the following will pop up next....
Ping statistics for 45.60.49.167:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 123ms, Average = 121ms
You want to be looking at that MAXIMUM..... If that's high then there are definitely issues.... If there are issues then run the next test.....
In the same black box type in tracert cox.com and press enter. You should see something similar to the following:
C:\Users\Mimi>tracert cox.com
Tracing route to cox.com [45.60.45.167]
over a maximum of 30 hops:
1 11 ms 17 ms 13 ms 10.5********** (blanked out for my protection)
2 15 ms 13 ms 14 ms 100.127.74.24
3 22 ms 19 ms 17 ms 100.120.100.12
4 372 ms 29 ms 15 ms lag-194.bear1.Phoenix1.Level3.net [4.31.188.61]
5 * * * Request timed out. <----BAD!!!!!
6 177 ms 31 ms 32 ms 4.7.26.34
7 31 ms 179 ms 36 ms 45.60.45.167
Trace complete.
See that section marked BAD??? Yeah, that means something's BROKEN..... If you see high connection time (the section that's in "ms" = milliseconds) or if you see what's in mine (timeout) then you have something to work with. Let's say I'm having slow speeds, I'll run another test to a site that's NOT owned by Cocks......
C:\Users\Mimi>tracert yahoo.com
Tracing route to yahoo.com [206.190.39.42]
over a maximum of 30 hops:
1 9 ms 15 ms 22 ms 10.5********** (blanked out for my protection)
2 16 ms 25 ms 15 ms 100.127.74.26
3 22 ms 16 ms 19 ms 100.120.100.16
4 28 ms 28 ms 27 ms 68.1.4.252 <---- LAST COX CONNETION
5 33 ms 28 ms 29 ms UNKNOWN-216-115-101-X.yahoo.com [216.115.101.244
]
6 29 ms 36 ms 27 ms UNKNOWN-216-115-102-X.yahoo.com [216.115.102.186
]
7 48 ms 41 ms 43 ms UNKNOWN-216-115-104-X.yahoo.com [216.115.104.79]
8 90 ms 59 ms 61 ms ae-6.pat2.swp.yahoo.com [216.115.100.91]
9 94 ms 64 ms 62 ms ae-7.pat1.gqb.yahoo.com [216.115.96.45]
10 121 ms 62 ms 64 ms et-1-0-0.msr1.gq1.yahoo.com [66.196.67.101]
11 63 ms 63 ms 63 ms et-0-0-0.clr2-a-gdc.gq1.yahoo.com [67.195.37.73]
12 63 ms 71 ms 63 ms et-17-25.fab4-1-gdc.gq1.yahoo.com [67.195.1.87]
13 240 ms 63 ms 64 ms po-12.bas2-7-prd.gq1.yahoo.com [206.190.32.35]
14 60 ms 57 ms 55 ms media-router-fp1.prod.media.vip.gq1.yahoo.com [2
06.190.39.42]
Trace complete.
That section that I marked is the last place that Cox physically has any control over your connection to the outside world basically. If you're seeing high connection times or timeout's before that last Cox connection then the issue is COCKS!!!
Don't let their so called tech support beat you up; use tools available to you to challenge them and PROVE they are the one's with issues.....
