Contributor
•
24 Messages
Mysterious & Frustrating Intermittent Packet Loss & Disconnects
I've spent countless hours troubleshooting our Xfinity Internet, including multiple customer calls and a technician visit. We have the 1000Mbps service with unlimited data.
Here are the symptoms:
- When it's good, it's perfect. When it's not good, randomly for several hours at a time:
- League of Legends is unplayable: lags every few seconds, disconnects every minute or so, or even the Internet would just drop altogether.
- PingPlotter graphs look like this (this is a UDP ping, not ICMP): (top = to first hop outside the house; bottom = to google.com): https://imgur.com/a/zXE3EOx
I am a software engineer, so it was natural for me to try various setups and process of elimination to see where the problem is. Before I present my findings, a couple of things to note:
- All tests are done via Ethernet using a powerful PC built in 2020.
- Most test scenarios were repeated with a router behind and without a router behind the modem. The router used is Google WiFi (of course, the WiFi part is not used for testing).
Here is a summary of trying different scenarios:
Modem Used | Modem Used | Modem Used | Modem Used | ||
XB7 | SB8200 | SB8200 (inactive) | SB6121 | ||
Cable configuration | 4-way 5-1002MHz splitter, modem downstairs | Occasional packet loss (always) | Extreme packet loss (December) | Not tested | No issues |
Cable configuration | 4 way 5-1002MHz splitter, modem upstairs | Occasional packet loss (always) | Not tested | Not tested | No issues |
Cable configuration | 4 way 5-2500MHz splitter + MoCA filter, modem upstairs behind MoCA | Severe packet loss and disconnects (February) | Not tested | Severe packet loss (February) | No issues |
Cable configuration | No splitters, modem upstairs | Severe packet loss and disconnects (February) | Not tested | Severe packet loss (February) | No issues |
On the cable configuration:
- 4-way 5-1002MHz splitter refers to a splitter previously installed in the house whose history I don't know of.
- Downstairs and upstairs are just two different coax sockets on the wall. The upstairs coax at the TV box initially didn't have a connector, so I used a crimp tool to add a connector.
- 4-way 5-2500MHz splitter refers to a splitter I got from Amazon (yeah, maybe not great) for MoCA setup. The MoCA set up uses a Motorola MoCA adapter; it's not too important for the discussion here.
- "No splitters" means I directly connect my upstairs coax to the incoming cable (via a thing that looks like a MoCA filter or a ground block? Not sure).
On the modem used:
- XB7 is from Comcast. Arris SB8200 is a DOCSIS 3.1 modem; Arris SB6121 is a slow 4x4 DOCSIS 3.0 modem.
- I list "SB8200 (inactive)" as a separate case for clarity: it means that the SB8200 I'm currently using shows in Comcast's systems as "inactive", despite me having activated it via the xfinity.com/activate prompts when I switched from the XB7 to the SB8200 and having received an email that my services are ready.
Further, here are the signal levels as reported by SB8200 right at the cable coming into the house (yeah, I moved my modem and router down there just to test that.)
OK, next, a few more observations:
- The SB8200 has an Event log which shows a series of entries beginning with "MDD message timeout"; these events perfectly align with the packet loss spikes. Also, whenever this happens, the SB8200's downstream light turns from green to blue, and after a few seconds, from blue back to green (the latter event is when the packet loss happens). The manual for SB8200 indicate that blue means DOCSIS 3.1. All lights are normally green (i.e. I'm not getting DOCSIS 3.1?), but this itself is fine because I'm still getting gigabit speeds.
- Sometimes I get channels 3-34 and 48; other times I get channels 17-47 and 48. Channels 3-34 have much better SNR (because they are lower frequencies, I assume). However the packet loss issue seems to happen in both cases.
- The XB7 does not report any logs; when I try to grab the system logs it shows me nothing. The XB7 also tends to just gives up the connection entirely (goes back to the flashing light cycles). SB8200 does less of that and seems more stable overall, except in December when it was just dropping like, 2% of packets or something.
- Somehow, IPv6 tests perform better than IPv4 tests (but not completely immune from packet loss). No idea why.
Alright, now we can try to logically figure out what's going on here:
- It's not WiFi, because no tests used WiFi.
- It's not any of the Ethernet cables having issues, because the SB8200's errors and light changes correspond perfectly to the packet loss. Also, WiFi devices suffer from spotty Internet as well when it happens.
- It's not any of the coax cables I use to connect from the wall socket to the modem, because I have tried two coax cables, one of which is brand new.
- It's unlikely that the issue was due to the coax wiring in the walls in the house, because I had experienced packet loss both upstairs and downstairs. However I don't say impossible because there was a two month gap between the packet loss events and it's possible they were separate events. Still, this is a recent house (~15 years old) and it's hard to imagine that a wiring issue would cause packet loss attacks to come in waves instead of constantly happening all the time; it also doesn't quite explain why SB6121 never has any issues.
- It's not the modem, because two different modems have issues, one of which is the latest model from Comcast.
- It has something to do with either DOCSIS 3.1, or the higher downstream frequencies because the SB6121, which uses DOCSIS3.0 and only the lower downstream frequencies never suffer from the packet loss issue. Of course, that modem could only get 135Mbps down and 6Mbps up so I don't want to use that just for reliability.
- Some things the technician said:
- "Your SB8200 shows up as 'disabled' in the systems, so you're gonna have issues". Well... the XB7 also has issues, so I don't think that was relevant. And if the SB8200 would always have issues then I might believe that, but most of the time the SB8200 does perfectly fine except sometimes the spikes happen. If it's an activation issue I'd expect it to either work or not work, not sometimes work and sometimes not.
- "This connector you put on the cable yourself - the white part is not flush with the connector, so that's probably why you're having packet loss". Yeah I did that connector myself, and I admit I was bad at it, but this technician redid it himself, and right that night I have a packet loss attack again, and with the XB7. So it's not that connector. And even if it's a connector issue, it doesn't explain why these packet loss attacks happen continuously for hours at a time and then never happens for many hours. Shouldn't it happen once in a while all the time?
- "The signal levels are all green." Dear forum users, what do you guys think? Are my signal levels normal? Does channel 48 (the ODFM channel, I assume) having that many errors look right to you?
- "This splitter isn't compatible with Comcast." (he was referring to the 5-2500MHz splitter I bought from Amazon) He might be right, but it was working perfectly for quite some days before packet loss attacks came. And also, packet loss still happens without the splitter.
So at this point I have several different hypotheses:
- Channel 48 (850MHz ODFM channel) has unacceptable SNR and is the root cause of all issues. The fix would be for Comcast to fix that SNR because the cable coming into the house had only 10dB SNR there.
- Channel 48 is actually fine and all signal levels are fine, but Comcast's networking node at the street is faulty and sometimes does not send MDD messages properly for the higher channels. The fix is still on the Comcast side.
- Some other highly unlikely issue is the root cause, such as both modems being faulty, both downstairs/upstairs coax wiring being faulty and only in the high frequencies, etc. etc. To eliminate these I'd have to run wired Ethernet tests at the ground block which really isn't convenient especially since it may take a couple of days for the next packet loss attack to happen.
If Comcast and I can't work together to fix this issue, I'd have to sadly go back to 100Mbps plan and use an old modem 😞
What do you guys think?
scraig2
Contributor
•
60 Messages
4 years ago
Add me to this list. Same issues as you. Everything is good, until it comes to the 3.1 channels. Seems to me it's the sb8200 and Xfinity not playing well together. I had a tech out Saturday and then a line tech followed. The line tech did something and my Upstream powers all 5 hit 48 or higher. I was finally getting 1gb wired and 840 wireless speeds. 5 minutes later my modem resets and those power levels dropped to 36-40 on all 4 channels. Wired speeds fell to 800 and wireless to 600. I dont think it's a coincidence when the power on Upstream goes down, my speeds drop.
0
0
user_2d6d13
Visitor
•
5 Messages
4 years ago
Update for @realyc - I now have a new Netgear CM2000 connected, I am not having any issues with maintaining a solid 3.1 connection - 500-700Mbps down, 42Mbps up. So, per the latest Xfinity tech, they "killed off" the Arris/Motorola self-owned modems in my area with some update they pushed 2 weeks ago, and until they decide to send out the correct boot cfg to them they will continue to have the problems I described - unstable/unusable service. I've talked to 2 neighbors on my street, they all had the same exact issue at the same exact time that I did. Looks like they haven't killed off the Netgear modems yet, however they're clearly being throttled by Xfinity. Prior to this last 2 weeks, for the past year I was consistently getting 800 to 900Mbps down with my SB8200, no issue with my lines at all, and now I'm magically getting 500 to 700Mbps down with a superior modem (CM200) to the Arris SB8200 I had been using for the last year.
1
0
realyc
Contributor
•
24 Messages
4 years ago
That's very interesting @user_2d6d13. I was considering that too, but my tech was patient enough to keep testing the line. I believe the issue with my SB8200 is that, it's really fine to stay on 3.0, I will get gigabit speeds with that, but no, it decides to go up to 3.1 when it detects a good signal, but because the signal is not reliably good, it falls back to 3.0 soon after. The moment it falls back is when I get a spike/packet loss. So really, the modem should not go to 3.1 if the signal is unreliable. If it simply avoided doing that, it would totally be fine. That's why I think the tech did not think bad 3.1 signal was an issue. *Bad* 3.1 signal is probably not an issue, but *fluctuating* 3.1 signal is. And that can be totally solved by having a better modem firmware.
1
0
user_004de3
Visitor
•
1 Message
4 years ago
Same issues here but after I decided I was done withe modem/router provided by xfinity, all was fantastic. I have a netgear nighthawk cm1200 and a google nest wifi. And then the troubles started again. I call and I keep getting the same answer that the fault lies with my equipment. So over xfinity
2
0