Frequent Visitor
•
36 Messages
Arris SB8200 and Linksys CM3024
I have two different cable modems. I recently decided to replace the Linksys CM3024 because of the Intel Puma 6 chipset issue(s).
Starting around 3/10/2020, on the Linksys CM3024, my internet has been spotty. I'm on a 500 plan now, but likely moving to Gigabit soon. Sometimes speed is okay, but over the past few weeks, things are hanging, loading slow, and video conferencing with work is very choppy. Doesn't matter what device - Iphone 11 Pro, Macbook Pro, Macbook Air, Ipad Air, etc.
I then switched to Arris SB8200, called Comcast to register, and the same problems persist. Can't be my equipment since I've confirmed with two different cablem modems now.
Here are logs. Can anyone provide some insight?
https://www.dropbox.com/s/bibf96yfbxb8m9l/Picture1.jpg?dl=0
https://www.dropbox.com/s/dx9nne9oowpxsbm/Picture2.jpg?dl=0
https://www.dropbox.com/s/d9o53j4flnc5ugo/Picture3.jpg?dl=0
https://www.dropbox.com/s/fjdagjs5qtwdsoc/Picture4.jpg?dl=0
https://www.dropbox.com/s/oqg8lcgm0y4xsfg/Picture5.jpg?dl=0
https://www.dropbox.com/s/uqlr90idm48iso4/Picture6.jpg?dl=0
EG
Expert
•
103.5K Messages
4 years ago
Can't see your pics. Since you are a new poster, they need to be approved by a Forum Admin. That could take some time. In the interim, you could try hosting them at one of those free third-party pic hosting sites like Imgur or Photobucket and post the link to them here.
0
0
Robirob22
Frequent Visitor
•
36 Messages
4 years ago
@EG Thanks for quick reply. I added links for the attachments. Appreciate your help.
0
0
Robirob22
Frequent Visitor
•
36 Messages
4 years ago
Update: Comcast technician came to my house this afternoon. Checked wiring from tv outlet, main hub in the house, all lines looked fine, he ran some tests, etc. He determined I am getting packet loss and then went to the outside of the house, and then to the street. After about 20 minutes he came back to the door, said he called another tech and said everything he checked out looks good, and wanted to know if the other tech knew anything going on in this area. The other tech told him he had been in our neighborhood a few times over the past few weeks and basically our nieghborhood is consuming about 90% of the total lines capacity. Comcast is aware and planning to upgrade the line/add a line and working on permitting. He said there is nothing he can do. ...???
1. Does this sound right?
2. I'm on a 500 plan now, does anyone think if I upgraded to gigabit plan it would help?
...Obviously need to call back now and work out some bill credits or something.
0
0
EG
Expert
•
103.5K Messages
4 years ago
So the signal stats looked o/k. The error log entries, not so much. It is possible to be a capacity / congestion problem. Especially now with everyone being at home using atypical amounts of bandwidth due to the Corona Virus issue.
And as far as upgrading your speed tier goes, if the lines can't handle the current load, they won't be able to deliver double your speed.
0
0
Robirob22
Frequent Visitor
•
36 Messages
4 years ago
@EG Thanks.
Just for kicks, i thought I would check after 11pm PST. Assumption is all the kids and parents are off internet for work, streaming 4k movies, etc. Well, same problems, ACTUALLY slower! Here are some updated screen shots. The event log is crazy now...
Everything around 1-3pm was when the tech was here, but you can see 3 entires after that.
I honestly dont know how I will work from home or kids will do school online. I had to use my cell phone's personal hotspot just to post this. It's 1130pm PST - my neighborhood can't be consuming all the bandwidth at this hour.
Should I ask to see if one of their modems would work better? Again, very odd that i have one modem (Linksys CM30240 barely 3 years old that was working fine up to about 2-3 weeks ago) and a brand-new one (Arris SB8200).
https://www.dropbox.com/s/o5equ2l8f1rp06g/new_Picture1.png?dl=0
https://www.dropbox.com/s/gpa1tmtpj9dbxue/new_Picture2.png?dl=0
https://www.dropbox.com/s/72t9lkjgbcp8wi3/new_Picture3.png?dl=0
0
0
Robirob22
Frequent Visitor
•
36 Messages
4 years ago
Sorry, here is ping info
Ping has started…
PING e7010.dscg.akamaiedge.net (184.50.208.177): 56 data bytes
64 bytes from 184.50.208.177: icmp_seq=0 ttl=52 time=91.649 ms
64 bytes from 184.50.208.177: icmp_seq=1 ttl=52 time=373.515 ms
64 bytes from 184.50.208.177: icmp_seq=2 ttl=52 time=333.186 ms
64 bytes from 184.50.208.177: icmp_seq=3 ttl=52 time=223.017 ms
64 bytes from 184.50.208.177: icmp_seq=4 ttl=52 time=95.198 ms
64 bytes from 184.50.208.177: icmp_seq=5 ttl=52 time=197.589 ms
64 bytes from 184.50.208.177: icmp_seq=6 ttl=52 time=280.425 ms
64 bytes from 184.50.208.177: icmp_seq=7 ttl=52 time=171.533 ms
Request timeout for icmp_seq 8
64 bytes from 184.50.208.177: icmp_seq=9 ttl=52 time=227.682 ms
64 bytes from 184.50.208.177: icmp_seq=10 ttl=52 time=277.337 ms
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
64 bytes from 184.50.208.177: icmp_seq=13 ttl=52 time=198.864 ms
64 bytes from 184.50.208.177: icmp_seq=14 ttl=52 time=102.198 ms
64 bytes from 184.50.208.177: icmp_seq=15 ttl=52 time=199.530 ms
64 bytes from 184.50.208.177: icmp_seq=16 ttl=52 time=218.869 ms
64 bytes from 184.50.208.177: icmp_seq=17 ttl=52 time=241.192 ms
64 bytes from 184.50.208.177: icmp_seq=18 ttl=52 time=96.616 ms
64 bytes from 184.50.208.177: icmp_seq=19 ttl=52 time=99.040 ms
Request timeout for icmp_seq 20
64 bytes from 184.50.208.177: icmp_seq=21 ttl=52 time=209.713 ms
64 bytes from 184.50.208.177: icmp_seq=22 ttl=52 time=99.367 ms
64 bytes from 184.50.208.177: icmp_seq=23 ttl=52 time=108.352 ms
64 bytes from 184.50.208.177: icmp_seq=24 ttl=52 time=115.014 ms
64 bytes from 184.50.208.177: icmp_seq=25 ttl=52 time=140.447 ms
64 bytes from 184.50.208.177: icmp_seq=26 ttl=52 time=153.919 ms
64 bytes from 184.50.208.177: icmp_seq=27 ttl=52 time=218.439 ms
Request timeout for icmp_seq 28
64 bytes from 184.50.208.177: icmp_seq=29 ttl=52 time=142.272 ms
64 bytes from 184.50.208.177: icmp_seq=30 ttl=52 time=155.946 ms
64 bytes from 184.50.208.177: icmp_seq=31 ttl=52 time=138.219 ms
64 bytes from 184.50.208.177: icmp_seq=32 ttl=52 time=116.952 ms
64 bytes from 184.50.208.177: icmp_seq=33 ttl=52 time=160.879 ms
64 bytes from 184.50.208.177: icmp_seq=34 ttl=52 time=184.383 ms
64 bytes from 184.50.208.177: icmp_seq=35 ttl=52 time=136.712 ms
64 bytes from 184.50.208.177: icmp_seq=36 ttl=52 time=176.109 ms
64 bytes from 184.50.208.177: icmp_seq=37 ttl=52 time=151.699 ms
64 bytes from 184.50.208.177: icmp_seq=38 ttl=52 time=95.143 ms
64 bytes from 184.50.208.177: icmp_seq=39 ttl=52 time=204.125 ms
64 bytes from 184.50.208.177: icmp_seq=40 ttl=52 time=111.185 ms
Request timeout for icmp_seq 41
Request timeout for icmp_seq 42
Request timeout for icmp_seq 43
Request timeout for icmp_seq 44
64 bytes from 184.50.208.177: icmp_seq=45 ttl=52 time=154.609 ms
Request timeout for icmp_seq 46
64 bytes from 184.50.208.177: icmp_seq=47 ttl=52 time=161.190 ms
64 bytes from 184.50.208.177: icmp_seq=48 ttl=52 time=108.655 ms
--- e7010.dscg.akamaiedge.net ping statistics ---
50 packets transmitted, 39 packets received, 22.0% packet loss
round-trip min/avg/max/stddev = 91.649/171.045/373.515/66.462 ms
0
0