Slow Cable Connection

[Tokenekie]

--This is not an ordinary complaint.


The problem here is simple. My internet is slow. Browsing can take anywhere from 1 minute to 3 minute per page and often does not receive a response from sites browsed.

The problem is complex in that these issues generally tend to escalate in magnitude from noon till anytime in the morning then improves over the course of the day where the cycle repeats again.

I have made multiple attempts to correct this issue. Below is a time line of events and actions regarding this problem (All actions listed did nothing to alter the aforementioned problem cycle):
---------------------------------------------------------------------------
6-1-07:

1) Power restarted Cable Mode, Router, Computer 1, Computer 2, Laptop
2) Cleaned each computer and laptop of viruses and spyware using McAfee Antivirus, and AdAware SE
3) Disconnected Router and directly fed connection to Computer 1, then computer 2, then the Laptop
4) Cleared browser caches and temporary internet files from each computing system.
5) E-Mailed ISP about issue.




6-2-07:

1) Received an E-Mail from ISP instructing to redo steps (1-4) on 6-1-07
2) Further instructions were to run a speed test, Traceroute, Ping, Ipconfig all, and Netstat tests.
3) Results Below. Test one conducted at Noon, Test two conducted at 1:00 AM
4) E-mailed results to ISP

Time Warner Cable Internet Bandwidth Results Your throughput is 1253 kilobits per second. Tracing route to www.yahoo-ht3.akadns.net [209.191.93.52] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms cpe-76-173-186-69.socal.res.rr.com [76.173.186.69] 2 * 9 ms 7 ms cpe-76-173-184-1.socal.res.rr.com [76.173.184.1] 3 99 ms 210 ms 11 ms gig0.breaca1-cda3.socal.rr.com [76.167.7.117] 4 61 ms 251 ms 10 ms 76.167.7.229 5 17 ms 18 ms 18 ms tge3-2-0.tustca1-rtr1.socal.rr.com [76.167.2.68] 6 24 ms 28 ms 24 ms GIG2-0.LSANCA1-RTR1.socal.rr.com [66.75.161.157] 7 25 ms * 20 ms pop1-las-P5-1.atdn.net [66.185.133.193] 8 24 ms 19 ms * bb2-las-P0-0.atdn.net [66.185.137.130] 9 * 28 ms 32 ms bb2-sjg-P7-0.atdn.net [66.185.152.23] 10 33 ms 28 ms 32 ms pop2-sjg-P1-0.atdn.net [66.185.150.99] 11 28 ms 28 ms 31 ms Teleglobe.atdn.net [66.185.150.106] 12 29 ms 30 ms 32 ms if-5-0-0.core4.SQN-SanJose.teleglobe.net [66.198.96.2] 13 29 ms 32 ms 28 ms if-5-0-0.mcore4.LAA-LosAngeles.teleglobe.net [216.6.85.33] 14 39 ms 35 ms 35 ms 10.icore1.LAA-LosAngeles.teleglobe.net [216.6.85.22] 15 * 75 ms 71 ms 2.icore1.DTX-Dallas.teleglobe.net [209.58.53.2] 16 63 ms 59 ms 58 ms if-1-0-0-40.core1.DTX-Dallas.teleglobe.net [66.198.1.9] 17 64 ms * * ix-5-0.core1.DTX-Dallas.teleglobe.net [216.6.53.2] 18 67 ms 63 ms 67 ms ge-1-1-0-p100.msr1.mud.yahoo.com [216.115.104.105] 19 72 ms 63 ms 68 ms te-9-1.bas-c2.mud.yahoo.com [68.142.193.11] 20 63 ms 82 ms 69 ms f1.www.vip.mud.yahoo.com [209.191.93.52] Trace complete. Tracing route to www.l.google.com [72.14.253.147] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms cpe-76-173-186-69.socal.res.rr.com [76.173.186.69] 2 9 ms 9 ms * cpe-76-173-184-1.socal.res.rr.com [76.173.184.1] 3 10 ms * * gig0.breaca1-cda3.socal.rr.com [76.167.7.117] 4 9 ms 9 ms * 76.167.7.229 5 18 ms * * tge3-2-0.tustca1-rtr1.socal.rr.com [76.167.2.68] 6 * 24 ms 29 ms tge1-2-0.lsanca1-rtr1.socal.rr.com [66.75.161.209] 7 21 ms 25 ms 24 ms 66.109.3.133 8 30 ms * 146 ms 66.109.0.21 9 31 ms 33 ms 28 ms 66.109.3.197 10 85 ms 84 ms 81 ms core2-1-1-0.pao.net.google.com [198.32.176.31] 11 86 ms 80 ms 79 ms 209.85.130.6 12 97 ms 93 ms 97 ms 66.249.95.135 13 * 95 ms 95 ms 216.239.46.203 14 * 93 ms 94 ms 72.14.233.29 15 100 ms 94 ms * 72.14.233.14 16 * 96 ms 90 ms po-in-f147.google.com [72.14.253.147] Trace complete. Pinging www.yahoo-ht3.akadns.net [209.191.93.52] with 32 bytes of data: Request timed out. Request timed out. Reply from 209.191.93.52: bytes=32 time=73ms TTL=49 Request timed out. Request timed out. Request timed out. Reply from 209.191.93.52: bytes=32 time=64ms TTL=49 Reply from 209.191.93.52: bytes=32 time=70ms TTL=50 Reply from 209.191.93.52: bytes=32 time=61ms TTL=50 Request timed out. Reply from 209.191.93.52: bytes=32 time=69ms TTL=49 Reply from 209.191.93.52: bytes=32 time=63ms TTL=50 Reply from 209.191.93.52: bytes=32 time=71ms TTL=50 Reply from 209.191.93.52: bytes=32 time=71ms TTL=49 Reply from 209.191.93.52: bytes=32 time=65ms TTL=49 Reply from 209.191.93.52: bytes=32 time=70ms TTL=50 Reply from 209.191.93.52: bytes=32 time=62ms TTL=50 Reply from 209.191.93.52: bytes=32 time=62ms TTL=50 Reply from 209.191.93.52: bytes=32 time=69ms TTL=50 Reply from 209.191.93.52: bytes=32 time=64ms TTL=49 Reply from 209.191.93.52: bytes=32 time=70ms TTL=49 Reply from 209.191.93.52: bytes=32 time=69ms TTL=50 Reply from 209.191.93.52: bytes=32 time=63ms TTL=50 Request timed out. Reply from 209.191.93.52: bytes=32 time=64ms TTL=49 Reply from 209.191.93.52: bytes=32 time=63ms TTL=50 Reply from 209.191.93.52: bytes=32 time=70ms TTL=50 Reply from 209.191.93.52: bytes=32 time=63ms TTL=49 Reply from 209.191.93.52: bytes=32 time=71ms TTL=49 Request timed out. Reply from 209.191.93.52: bytes=32 time=63ms TTL=50 Reply from 209.191.93.52: bytes=32 time=70ms TTL=49 Reply from 209.191.93.52: bytes=32 time=63ms TTL=49 Reply from 209.191.93.52: bytes=32 time=63ms TTL=49 Reply from 209.191.93.52: bytes=32 time=73ms TTL=49 Reply from 209.191.93.52: bytes=32 time=64ms TTL=50 Reply from 209.191.93.52: bytes=32 time=71ms TTL=50 Reply from 209.191.93.52: bytes=32 time=70ms TTL=49 Reply from 209.191.93.52: bytes=32 time=64ms TTL=49 Request timed out. Reply from 209.191.93.52: bytes=32 time=61ms TTL=50 Reply from 209.191.93.52: bytes=32 time=63ms TTL=49 Reply from 209.191.93.52: bytes=32 time=69ms TTL=49 Reply from 209.191.93.52: bytes=32 time=62ms TTL=50 Reply from 209.191.93.52: bytes=32 time=69ms TTL=50 Reply from 209.191.93.52: bytes=32 time=73ms TTL=49 Reply from 209.191.93.52: bytes=32 time=63ms TTL=49 Reply from 209.191.93.52: bytes=32 time=70ms TTL=50 Reply from 209.191.93.52: bytes=32 time=68ms TTL=50 Reply from 209.191.93.52: bytes=32 time=62ms TTL=50 Ping statistics for 209.191.93.52: Packets: Sent = 50, Received = 41, Lost = 9 (18% loss), Approximate round trip times in milli-seconds: Minimum = 61ms, Maximum = 73ms, Average = 66ms Active Connections Proto Local Address Foreign Address State TCP main:epmap main:0 LISTENING TCP main:microsoft-ds main:0 LISTENING TCP main:4446 main:0 LISTENING TCP main:4463 main:0 LISTENING TCP main:5225 main:0 LISTENING TCP main:5226 main:0 LISTENING TCP main:6646 main:0 LISTENING TCP main:mi-raysat_3dsmax8 main:0 LISTENING TCP main:8008 main:0 LISTENING TCP main:31038 main:0 LISTENING TCP main:netbios-ssn main:0 LISTENING TCP main:4460 host86-156-175-220.range86-156.btcentralplus.com:6667 ESTABLISHED TCP main:4461 cs43.msg.dcn.yahoo.com:5050 ESTABLISHED TCP main:4465 by1msg3175706.phx.gbl:1863 ESTABLISHED TCP main:4467 64.12.31.224:5190 ESTABLISHED TCP main:4468 205.188.9.89:5190 ESTABLISHED TCP main:4470 oam-m09b.blue.aol.com:5190 ESTABLISHED TCP main:4474 66.151.149.78:http TIME_WAIT TCP main:4481 po-in-f165.google.com:http ESTABLISHED TCP main:4482 dndorks.com:http ESTABLISHED TCP main:4483 po-in-f165.google.com:http ESTABLISHED TCP main:4484 by115w.bay115.mail.start.com:http ESTABLISHED TCP main:4487 dime134.dizinc.com:http ESTABLISHED TCP main:4488 by104w.bay104.mail.start.com:http ESTABLISHED TCP main:4491 by104w.bay104.mail.start.com:http ESTABLISHED TCP main:4492 by104w.bay104.mail.start.com:http ESTABLISHED TCP main:4495 64.86.142.73:http ESTABLISHED TCP main:4500 65.54.194.118:http ESTABLISHED TCP main:4501 207.68.178.134:http ESTABLISHED TCP main:4502 65.54.194.118:http ESTABLISHED TCP main:4503 207.68.178.134:http ESTABLISHED TCP main:4515 64.12.31.128:5190 ESTABLISHED TCP main:1026 localhost:32000 ESTABLISHED TCP main:1065 main:0 LISTENING TCP main:1089 main:0 LISTENING TCP main:1090 main:0 LISTENING TCP main:1133 localhost:5226 ESTABLISHED TCP main:1880 localhost:1881 ESTABLISHED TCP main:1881 localhost:1880 ESTABLISHED TCP main:1882 localhost:1883 ESTABLISHED TCP main:1883 localhost:1882 ESTABLISHED TCP main:5226 localhost:1133 ESTABLISHED TCP main:8005 main:0 LISTENING TCP main:32000 main:0 LISTENING TCP main:32000 localhost:1026 ESTABLISHED UDP main:microsoft-ds *:* UDP main:isakmp *:* UDP main:1033 *:* UDP main:1039 *:* UDP main:1088 *:* UDP main:1344 *:* UDP main:1366 *:* UDP main:2693 *:* UDP main:2694 *:* UDP main:3545 *:* UDP main:3552 *:* UDP main:4500 *:* UDP main:ntp *:* UDP main:netbios-ns *:* UDP main:netbios-dgm *:* UDP main:1900 *:* UDP main:6646 *:* UDP main:ntp *:* UDP main:1900 *:* UDP main:2281 *:* UDP main:4045 *:*

Time Warner Cable Internet Bandwidth Results Loaded 1327509 bytes in 21.375 seconds. Your throughput is 497 kilobits per second. Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms cpe-76-173-186-69.socal.res.rr.com [76.173.186.69] 2 * 8 ms * cpe-76-173-184-1.socal.res.rr.com [76.173.184.1] 3 8 ms * 7 ms gig0.breaca1-cda3.socal.rr.com [76.167.7.117] 4 10 ms 9 ms 10 ms 76.167.7.229 5 * * * Request timed out. 6 * 29 ms 29 ms tge1-2-0.LSANCA1-RTR1.socal.rr.com [66.75.161.209] 7 21 ms * 21 ms pop1-las-P5-1.atdn.net [66.185.133.193] 8 * 24 ms 21 ms bb2-las-P0-0.atdn.net [66.185.137.130] 9 * * * Request timed out. 10 32 ms 28 ms * pop2-sjg-P1-0.atdn.net [66.185.150.99] 11 33 ms 28 ms 31 ms Teleglobe.atdn.net [66.185.150.106] 12 * 29 ms * Vlan3.msfc2.SQN-SanJose.Teleglobe.net [64.86.82.195] 13 * * 83 ms 216.6.52.6 14 * 71 ms 69 ms g-0-0-0-p171.msr2.sp1.yahoo.com [216.115.107.83] 15 66 ms 69 ms 65 ms te-9-1.bas-a1.sp1.yahoo.com [209.131.32.21] 16 68 ms 74 ms 66 ms f1.www.vip.sp1.yahoo.com [209.131.36.158] Trace complete. Tracing route to www.l.google.com [72.14.253.103] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms cpe-76-173-186-69.socal.res.rr.com [76.173.186.69] 2 * 10 ms * cpe-76-173-184-1.socal.res.rr.com [76.173.184.1] 3 * * * Request timed out. 4 200 ms * 9 ms 76.167.7.229 5 * * * Request timed out. 6 27 ms * 27 ms tge1-2-0.LSANCA1-RTR1.socal.rr.com [66.75.161.209] 7 * 21 ms 24 ms 66.109.3.133 8 * 34 ms * 66.109.0.21 9 96 ms 46 ms * 66.109.3.197 10 80 ms 84 ms * core2-1-1-0.pao.net.google.com [198.32.176.31] 11 84 ms * 81 ms 209.85.130.6 12 * 92 ms 92 ms 66.249.95.135 13 98 ms 94 ms * 72.14.233.45 14 98 ms 90 ms * 209.85.250.69 15 95 ms 90 ms * 72.14.233.18 16 96 ms * 93 ms po-in-f103.google.com [72.14.253.103] Trace complete. Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data: Reply from 209.131.36.158: bytes=32 time=67ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=65ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 209.131.36.158: bytes=32 time=65ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Request timed out. Request timed out. Reply from 209.131.36.158: bytes=32 time=65ms TTL=50 Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Reply from 209.131.36.158: bytes=32 time=63ms TTL=50 Request timed out. Request timed out. Request timed out. Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Reply from 209.131.36.158: bytes=32 time=65ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Reply from 209.131.36.158: bytes=32 time=65ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=67ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Request timed out. Request timed out. Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Reply from 209.131.36.158: bytes=32 time=63ms TTL=50 Request timed out. Request timed out. Reply from 209.131.36.158: bytes=32 time=66ms TTL=50 Request timed out. Reply from 209.131.36.158: bytes=32 time=65ms TTL=50 Request timed out. Request timed out. Reply from 209.131.36.158: bytes=32 time=70ms TTL=50 Reply from 209.131.36.158: bytes=32 time=64ms TTL=50 Ping statistics for 209.131.36.158: Packets: Sent = 50, Received = 26, Lost = 24 (48% loss), Approximate round trip times in milli-seconds: Minimum = 63ms, Maximum = 70ms, Average = 65ms Active Connections Proto Local Address Foreign Address State TCP main:epmap main:0 LISTENING TCP main:microsoft-ds main:0 LISTENING TCP main:2531 main:0 LISTENING TCP main:4446 main:0 LISTENING TCP main:5225 main:0 LISTENING TCP main:5226 main:0 LISTENING TCP main:6646 main:0 LISTENING TCP main:mi-raysat_3dsmax8 main:0 LISTENING TCP main:8008 main:0 LISTENING TCP main:31038 main:0 LISTENING TCP main:netbios-ssn main:0 LISTENING TCP main:2542 cs53.msg.dcn.yahoo.com:5050 ESTABLISHED TCP main:2544 64.12.31.224:5190 ESTABLISHED TCP main:1026 localhost:32000 ESTABLISHED TCP main:1065 main:0 LISTENING TCP main:1089 main:0 LISTENING TCP main:1090 main:0 LISTENING TCP main:1133 localhost:5226 ESTABLISHED TCP main:1780 localhost:5225 CLOSE_WAIT TCP main:1880 localhost:1881 ESTABLISHED TCP main:1881 localhost:1880 ESTABLISHED TCP main:1882 localhost:1883 ESTABLISHED TCP main:1883 localhost:1882 ESTABLISHED TCP main:5226 localhost:1133 ESTABLISHED TCP main:8005 main:0 LISTENING TCP main:32000 main:0 LISTENING TCP main:32000 localhost:1026 ESTABLISHED UDP main:microsoft-ds *:* UDP main:isakmp *:* UDP main:1033 *:* UDP main:1039 *:* UDP main:1088 *:* UDP main:1344 *:* UDP main:1366 *:* UDP main:2693 *:* UDP main:2694 *:* UDP main:3545 *:* UDP main:3552 *:* UDP main:4500 *:* UDP main:ntp *:* UDP main:netbios-ns *:* UDP main:netbios-dgm *:* UDP main:1900 *:* UDP main:6646 *:* UDP main:ntp *:* UDP main:1900 *:* UDP main:2281 *:*

6-3-07:

1) Received an E-Mail from ISP instructing me to re-sweep computing systems of spyware




6-4-07:

1) Contacted ISP by phone
2) Technician scheduled to dispatch on Wednesday at 4:30 PM




6-6-07:

1) Technicians conducted tests, results were [I}Normal{/I]
3) Technicians claim the my Cable Modem is situated too far from my main cable line in my garage.
2) Technicians Suggested an upgrade to a better package- Turbo Charge (http://www.timewarnercable.com/Piedm...rrpricing.html)




6-11-07:

1) Reconducted step 2 on 6-2-07 at 6:30 PM. Results Below:

Time Warner Cable Internet Bandwidth Results Loaded 1327509 bytes in 17.625 seconds. Your throughput is 603 kilobits per second. Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms cpe-75-84-3-30.socal.res.rr.com [75.84.3.30] 2 * * * Request timed out. 3 * 10 ms 8 ms gig0.breaca1-cda3.socal.rr.com [76.167.7.117] 4 13 ms * 39 ms 76.167.7.229 5 * * * Request timed out. 6 * 26 ms 21 ms GIG2-0.LSANCA1-RTR1.socal.rr.com [66.75.161.157] 7 22 ms * * pop1-las-P5-0.atdn.net [66.185.143.5] 8 21 ms * * bb2-las-P0-0.atdn.net [66.185.137.130] 9 214 ms 207 ms 202 ms bb2-sjg-P7-0.atdn.net [66.185.152.23] 10 31 ms * 31 ms pop2-sjg-P1-0.atdn.net [66.185.150.99] 11 25 ms 25 ms 29 ms Teleglobe.atdn.net [66.185.150.106] 12 25 ms 29 ms * Vlan3.msfc2.SQN-SanJose.Teleglobe.net [64.86.82.195] 13 * * 67 ms 216.6.52.6 14 * * * Request timed out. 15 * 71 ms 63 ms te-9-1.bas-a1.sp1.yahoo.com [209.131.32.21] 16 * 67 ms 66 ms f1.www.vip.sp1.yahoo.com [209.131.36.158] Trace complete. Tracing route to www.l.google.com [72.14.253.99] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms cpe-75-84-3-30.socal.res.rr.com [75.84.3.30] 2 10 ms 8 ms * cpe-75-84-0-1.socal.res.rr.com [75.84.0.1] 3 10 ms 8 ms * gig0.breaca1-cda3.socal.rr.com [76.167.7.117] 4 * 11 ms 11 ms 76.167.7.229 5 14 ms 13 ms 16 ms tge3-2-0.tustca1-rtr1.socal.rr.com [76.167.2.68] 6 25 ms 26 ms 25 ms GIG2-0.LSANCA1-RTR1.socal.rr.com [66.75.161.157] 7 23 ms 21 ms * 66.109.3.133 8 31 ms 25 ms 25 ms 66.109.0.21 9 67 ms 29 ms 57 ms 66.109.3.197 10 84 ms * 82 ms core2-1-1-0.pao.net.google.com [198.32.176.31] 11 * 80 ms * 209.85.130.6 12 * * * Request timed out. 13 90 ms 94 ms 91 ms 216.239.46.211 14 * * * Request timed out. 15 * 92 ms 97 ms 72.14.233.18 16 93 ms * 88 ms po-in-f99.google.com [72.14.253.99] Trace complete. Pinging www.yahoo-ht3.akadns.net [209.131.36.158] with 32 bytes of data: Reply from 209.131.36.158: bytes=32 time=70ms TTL=49 Reply from 209.131.36.158: bytes=32 time=125ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=65ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=132ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=89ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=69ms TTL=49 Reply from 209.131.36.158: bytes=32 time=69ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=69ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=64ms TTL=49 Reply from 209.131.36.158: bytes=32 time=64ms TTL=49 Reply from 209.131.36.158: bytes=32 time=64ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=69ms TTL=49 Request timed out. Reply from 209.131.36.158: bytes=32 time=65ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=65ms TTL=49 Reply from 209.131.36.158: bytes=32 time=66ms TTL=49 Reply from 209.131.36.158: bytes=32 time=69ms TTL=49 Reply from 209.131.36.158: bytes=32 time=67ms TTL=49 Reply from 209.131.36.158: bytes=32 time=70ms TTL=49 Request timed out. Reply from 209.131.36.158: bytes=32 time=72ms TTL=49 Reply from 209.131.36.158: bytes=32 time=68ms TTL=49 Reply from 209.131.36.158: bytes=32 time=69ms TTL=49 Ping statistics for 209.131.36.158: Packets: Sent = 50, Received = 48, Lost = 2 (4% loss), Approximate round trip times in milli-seconds: Minimum = 64ms, Maximum = 132ms, Average = 70ms Active Connections Proto Local Address Foreign Address State TCP main:epmap main:0 LISTENING TCP main:microsoft-ds main:0 LISTENING TCP main:2667 main:0 LISTENING TCP main:2869 main:0 LISTENING TCP main:3689 main:0 LISTENING TCP main:4446 main:0 LISTENING TCP main:5225 main:0 LISTENING TCP main:5226 main:0 LISTENING TCP main:6646 main:0 LISTENING TCP main:mi-raysat_3dsmax8 main:0 LISTENING TCP main:8008 main:0 LISTENING TCP main:31038 main:0 LISTENING TCP main:1026 localhost:32000 ESTABLISHED TCP main:1105 main:0 LISTENING TCP main:1235 main:0 LISTENING TCP main:1255 main:0 LISTENING TCP main:1358 localhost:5226 ESTABLISHED TCP main:3081 localhost:5225 CLOSE_WAIT TCP main:4046 localhost:4047 ESTABLISHED TCP main:4047 localhost:4046 ESTABLISHED TCP main:4049 localhost:4050 ESTABLISHED TCP main:4050 localhost:4049 ESTABLISHED TCP main:5226 localhost:1358 ESTABLISHED TCP main:5354 main:0 LISTENING TCP main:8005 main:0 LISTENING TCP main:32000 main:0 LISTENING TCP main:32000 localhost:1026 ESTABLISHED TCP main:netbios-ssn main:0 LISTENING TCP main:1228 38.99.229.8:http ESTABLISHED TCP main:1238 38.99.229.8:http ESTABLISHED TCP main:1268 38.99.229.8:http ESTABLISHED TCP main:1289 da-in-f166.google.com:http ESTABLISHED TCP main:1343 digg.com:http TIME_WAIT TCP main:1344 digg.com:http ESTABLISHED TCP main:1345 digg.com:http ESTABLISHED TCP main:1348 digg.com:http ESTABLISHED TCP main:1349 digg.com:http ESTABLISHED TCP main:1350 digg.com:http ESTABLISHED TCP main:1351 ns-vip3.hitbox.com:http ESTABLISHED TCP main:1352 digg.com:http TIME_WAIT TCP main:1359 digg.com:http ESTABLISHED TCP main:1362 207.68.178.134:http ESTABLISHED TCP main:1365 12.120.29.14:http ESTABLISHED TCP main:1367 12.120.29.14:http ESTABLISHED TCP main:1374 216.246.93.67:http ESTABLISHED TCP main:2638 by2msg1104006.phx.gbl:1863 ESTABLISHED TCP main:2669 cs.sv.xfire.com:25999 ESTABLISHED TCP main:2674 cs43.msg.dcn.yahoo.com:5050 ESTABLISHED TCP main:2677 64.12.31.226:5190 ESTABLISHED TCP main:2678 205.188.9.88:5190 ESTABLISHED TCP main:2679 oam-m09b.blue.aol.com:5190 ESTABLISHED TCP main:2843 us.mcafee.com:https FIN_WAIT_2 TCP main:61269 192.168.0.1:http TIME_WAIT UDP main:microsoft-ds *:* UDP main:isakmp *:* UDP main:1037 *:* UDP main:1043 *:* UDP main:1288 *:* UDP main:1289 *:* UDP main:1308 *:* UDP main:1309 *:* UDP main:1327 *:* UDP main:1330 *:* UDP main:1331 *:* UDP main:1332 *:* UDP main:1333 *:* UDP main:1334 *:* UDP main:1335 *:* UDP main:1336 *:* UDP main:1337 *:* UDP main:1338 *:* UDP main:1339 *:* UDP main:1340 *:* UDP main:1341 *:* UDP main:1342 *:* UDP main:1343 *:* UDP main:1344 *:* UDP main:1345 *:* UDP main:1346 *:* UDP main:1347 *:* UDP main:1348 *:* UDP main:1379 *:* UDP main:1396 *:* UDP main:1397 *:* UDP main:1475 *:* UDP main:1484 *:* UDP main:1487 *:* UDP main:2666 *:* UDP main:3422 *:* UDP main:4327 *:* UDP main:4500 *:* UDP main:25002 *:* UDP main:25777 *:* UDP main:ntp *:* UDP main:1209 *:* UDP main:1351 *:* UDP main:1394 *:* UDP main:1900 *:* UDP main:discard *:* UDP main:ntp *:* UDP main:netbios-ns *:* UDP main:netbios-dgm *:* UDP main:1900 *:* UDP main:5353 *:* UDP main:6646 *:* UDP main:10756 *:* UDP main:19094 *:* UDP main:26047 *:*

--------------------------------------------------------

Running speed tests at www.speakeasy.net gave relatively normal cable results, 5440 kbps Down, 7 kbps Up at 6:30 PM today.

I need to get some opinions about this problem before I resubmit another complaint to my ISP.

[Floppyman]

Did that speed test really say only 7kbps (kilobits per second) upload speed? If so, that is way too slow for browsing the internet (remember your computer has to send requests to webservers as well to download the pages). Please confirm, and we'll go from there. HTH

[Tokenekie]

Yes, 7 kbps.

That seemed a bit surprising to me too but I always thought upload would be relatively slow.

*Update: as of right now, my internet seems to be working fine. These intermittent periods of "good" connection are common*

[gunrunnerjohn]

Wait until a "bad" period and do this.

Register at DSLReports and run their line quality tests. Post a link to the results here.

[Tokenekie]

I wasn't able to run a line quality test at that website.


"sorry, 75.84.3.xx is not pingable from www.dslreports.com."


This error occurred with and without the router attached. Maybe because Cable != DSL? I don't know, just a thought.

[glc]

Your up speed should be in the 300k range - 7 is worse than dialup.

Run your tests with the router out of the equation - connect the modem directly to a computer. You need to isolate the problem to a specific computer, the router, or the modem and everything upstream of it. Run your tests with 3rd party software firewalls disabled - use only the Windows firewall. When moving the modem output to different devices, it has to be powered off for a few minutes to reset the MAC.