New Contributor
•
2 Messages
Slow internet, high upload.
I've been experiencing very slow speeds for about two or three weeks now. This issue has not only affected my family, but also myself. At this point I have no idea what to do. I've gone through technician after technician. I've also been the online chat service pretty often this the occurrence of this issue. - To the curious, I'm in the Pensacola FL area.
Model: Cisco DPC3825
Router: None
Channel 1: -5.2 dBmV 37.6 dB
Channel 2: -5.0 dBmV 38.4 dB
Channel 3: -4.9 dBmV 38.3 dB
Channel 4: -5.5 dBmV 38.2 dB
Channel 5: -5.3 dBmV 38.3 dB
Channel 6: 0.0 dBmV 0.0 dB
Channel 7: 0.0 dBmV 0.0 dB
Channel 8: 0.0 dBmV 0.0 dB
[Channel] --> [Power Level] --> [Signal to Noise Ratio] Format
Here's my ping from 10/25:
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=206 ms
64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=170 ms
64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=1502 ms
64 bytes from 192.168.0.1: icmp_req=4 ttl=64 time=555 ms
64 bytes from 192.168.0.1: icmp_req=5 ttl=64 time=1458 ms
64 bytes from 192.168.0.1: icmp_req=6 ttl=64 time=459 ms
64 bytes from 192.168.0.1: icmp_req=7 ttl=64 time=179 ms
64 bytes from 192.168.0.1: icmp_req=8 ttl=64 time=118 ms
64 bytes from 192.168.0.1: icmp_req=9 ttl=64 time=339 ms
64 bytes from 192.168.0.1: icmp_req=10 ttl=64 time=475 ms
64 bytes from 192.168.0.1: icmp_req=11 ttl=64 time=3368 ms
64 bytes from 192.168.0.1: icmp_req=15 ttl=64 time=1059 ms
64 bytes from 192.168.0.1: icmp_req=16 ttl=64 time=55.6 ms
64 bytes from 192.168.0.1: icmp_req=17 ttl=64 time=428 ms
64 bytes from 192.168.0.1: icmp_req=18 ttl=64 time=458 ms
64 bytes from 192.168.0.1: icmp_req=19 ttl=64 time=41.7 ms
64 bytes from 192.168.0.1: icmp_req=20 ttl=64 time=2496 ms
64 bytes from 192.168.0.1: icmp_req=21 ttl=64 time=1489 ms
64 bytes from 192.168.0.1: icmp_req=22 ttl=64 time=482 ms
64 bytes from 192.168.0.1: icmp_req=23 ttl=64 time=601 ms
64 bytes from 192.168.0.1: icmp_req=24 ttl=64 time=234 ms
64 bytes from 192.168.0.1: icmp_req=25 ttl=64 time=166 ms
64 bytes from 192.168.0.1: icmp_req=27 ttl=64 time=2786 ms
64 bytes from 192.168.0.1: icmp_req=28 ttl=64 time=1779 ms
64 bytes from 192.168.0.1: icmp_req=29 ttl=64 time=778 ms
64 bytes from 192.168.0.1: icmp_req=30 ttl=64 time=540 ms
64 bytes from 192.168.0.1: icmp_req=31 ttl=64 time=470 ms
64 bytes from 192.168.0.1: icmp_req=32 ttl=64 time=1391 ms
64 bytes from 192.168.0.1: icmp_req=33 ttl=64 time=403 ms
64 bytes from 192.168.0.1: icmp_req=34 ttl=64 time=1115 ms
64 bytes from 192.168.0.1: icmp_req=35 ttl=64 time=130 ms
^C
--- 192.168.0.1 ping statistics ---
35 packets transmitted, 31 received, 11% packet loss, time 34104ms
rtt min/avg/max/mdev = 41.748/830.554/3368.597/830.678 ms, pipe 4
A few questions that I wouldn't mind answering:
Q: Are you wired or wireless?
A: I'm mainly wireless. Those tests that I have attached in the post were done using wireless. I was approximately near the modem while doing those tests too.
Q: Splitters/Filters
A: I cannot currently do these tests.
Q: Is phone/TV service effected?
A: My parents have no said anything about their TV service being effected at this time. We currently did away with phones when we got off AT&T DSL.
Q: Have I tweaked with anything?
A: No I have not.
----
I do have some questions and concerns. While my technician was out here last night (10/24/2013) he saw that my upload was at 11MB and my download was around 7MB. He's never in his career seen that. He did say some other things that this is 1% of his issues, and there was really no set in stone answer. We switched our gateway modem out with the same one, but it didn't do anything. It only temporarily fixed the issue.
I'm sorry for my saviness when it comes to networking. I'm the only person who knows what they're talking about in this house. I know that we're not getting speeds that we are purchasing, and I'm upset about it. (Our current plan is 35 down / 5mb up)
Thanks again,
Nasood
Source: http://www.dslreports.com/forum/r28766614-FL-Slow-Download-Stable-Upload
The last reply on that site I got was on the 30th, which was me. I'm very conerned because on the 30th of October, i received a ping over 6000+
ping 192.168.0.01
PING 192.168.0.01 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=7330 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=6380 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=5495 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=4500 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=3506 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=2510 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1612 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=671 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=86.0 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=14.8 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=3.54 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=16.8 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=29.5 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=61.1 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=44.1 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=145 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=272 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=1174 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=2148 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=1417 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=1031 ms
^C
----
We have the premier package if I'm not mistaken. (I've stated my plan above.) I'm not sure what to do at the moment. It's causing stress onto my family, and I myself. The internet is way to slow for my liking. Even when I plug into ethernet, I still lag which is just absurd. I've gotten to point where I might just drop it. A month or two of constant techs out here and slow internet is just getting to me.
EdwardH
Valued Contributor
•
755 Messages
12 years ago
When you mentioned you connected wired to the Gateway were you getting the similar ping times and dropped packets in the test or was it just sluggish without those same results?
Also if you can test with a different wireless connection close by or verify the wireless card in the device has the problem elsewhere it would pretty much tell us the Gateway is the problem. Your signal levels on the modems log appear to be fine.
0
0
RDCA
New Contributor
•
2 Messages
12 years ago
As far as i know, a ping to my gateway should NEVER be as high as 30ms. If I'm reaching 7000ms+, I personally believe that is a problem. I've also had new cabling installed. This house is a bit older, but we do have RG-6 cables installed.
0
0