Visitor
•
7 Messages
Extreme Packet Loss (30+%) multiple hours per day
I was having high packet loss in the past and although it was never fully fixed, it got to the point where it wasn't bothersome enough to pester support about it when it was happening for 5 to 10 minutes every day. However, it has now gotten even worse for now multiple hours per day. It is at seemingly random times (1pm, 3:30pm, 5:15pm, 10:22pm, 1:54am, 4:17am) and it can last from anywhere from 5 to 45 minutes. It is happening every single day, with a bare minimum of 60 minutes per day. I find it highly unlikely it's a traffic issue when it's happening in the middle of the night. It has nothing to do with my devices. I have tested my desktop computer with multiple ethernet cables and wifi, my phone on wifi, and 2 laptops on wifi. They all have the same issue at the same time. This is NOT me saying I have the issue because all those are connected at once. They are tested individually while the others are disconnected. I have also tried swapping out the coax cable between my modem and my wall connection. That did not help.
I would also like to be very clear that this IS NOT a speed issue. When the internet is actually consistent, I get the speed I pay for. The problem is that I pay for consistently usable internet and it is completely unusable for anything requiring streaming for multiple hours per day. I work from home and am frequently in video calls so this makes work difficult. I also play online video games in my free time. So not only does it impact my general enjoyment, it is also impacting my work life.
When I am running tracert tests to the google dns (tracert 8.8.8.8) none of the nodes consistently cause the request to time out whenever I'm having packet loss. It is a seemingly random node every time I run it, so it's not likely it is an issue with any particular node on route to that ip.
As far as I can tell, all the power levels and signal to noise ratio are within acceptable ranges, even while this is happening. It seems clear to me that there is a hardware issue that is NOT in my apartment or anything to do with my setup. It is somewhere else in the equipment that is required for me to connect to the internet and it should be fixed.
Downstream
|
Channel Bonding Value | |||||||||||||||||||||||||||||||
Index |
24
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
33
|
34
|
48
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Lock Status |
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Frequency |
579 MHz
|
453 MHz
|
459 MHz
|
465 MHz
|
471 MHz
|
477 MHz
|
483 MHz
|
489 MHz
|
495 MHz
|
507 MHz
|
513 MHz
|
519 MHz
|
525 MHz
|
531 MHz
|
537 MHz
|
543 MHz
|
549 MHz
|
555 MHz
|
561 MHz
|
567 MHz
|
573 MHz
|
585 MHz
|
591 MHz
|
597 MHz
|
603 MHz
|
609 MHz
|
615 MHz
|
621 MHz
|
627 MHz
|
633 MHz
|
639 MHz
|
805000000
|
SNR |
41.5 dB
|
41.4 dB
|
40.9 dB
|
41.4 dB
|
41.2 dB
|
40.9 dB
|
41.5 dB
|
41.5 dB
|
41.7 dB
|
41.4 dB
|
41.8 dB
|
41.3 dB
|
41.4 dB
|
41.3 dB
|
41.4 dB
|
40.8 dB
|
41.2 dB
|
41.4 dB
|
41.5 dB
|
41.5 dB
|
41.2 dB
|
41.5 dB
|
41.3 dB
|
41.0 dB
|
40.9 dB
|
41.4 dB
|
41.4 dB
|
41.2 dB
|
40.9 dB
|
41.3 dB
|
40.9 dB
|
41.4 dB
|
Power Level |
2.3 dBmV
|
1.4 dBmV
|
1.4 dBmV
|
1.4 dBmV
|
1.4 dBmV
|
1.6 dBmV
|
1.9 dBmV
|
2.0 dBmV
|
1.9 dBmV
|
2.1 dBmV
|
2.2 dBmV
|
2.1 dBmV
|
2.1 dBmV
|
2.1 dBmV
|
2.1 dBmV
|
2.1 dBmV
|
2.1 dBmV
|
2.1 dBmV
|
2.3 dBmV
|
2.2 dBmV
|
2.2 dBmV
|
2.2 dBmV
|
2.2 dBmV
|
2.4 dBmV
|
2.4 dBmV
|
2.4 dBmV
|
2.4 dBmV
|
2.4 dBmV
|
2.5 dBmV
|
2.5 dBmV
|
2.5 dBmV
|
3.1 dBmV
|
Modulation |
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
256 QAM
|
OFDM
|
Upstream
|
Channel Bonding Value | ||||||
Index |
1
|
2
|
3
|
4
|
5
|
6
|
|
---|---|---|---|---|---|---|---|
Lock Status |
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
|
Frequency |
10 MHz
|
16 MHz
|
22 MHz
|
29 MHz
|
35 MHz
|
40 MHz
|
|
Symbol Rate |
2560
|
5120
|
5120
|
5120
|
5120
|
2560
|
|
Power Level |
42.3 dBmV
|
43.3 dBmV
|
43.3 dBmV
|
44.3 dBmV
|
44.3 dBmV
|
44.3 dBmV
|
|
Modulation |
QAM
|
QAM
|
QAM
|
QAM
|
QAM
|
QAM
|
|
Channel Type |
ATDMA
|
ATDMA
|
ATDMA
|
ATDMA
|
ATDMA
|
ATDMA
|
CM Error Codewords | ||||||||||||||||||||||||||||||||
Index |
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
32
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Unerrored Codewords |
379817337
|
397012998
|
397019987
|
397009646
|
397032311
|
397038605
|
397045304
|
397050761
|
397057486
|
397063794
|
397069693
|
397076868
|
397083580
|
397089173
|
397094877
|
397101810
|
397109739
|
397116349
|
397122562
|
397127696
|
397134373
|
397140520
|
397147584
|
397153972
|
397159582
|
397166249
|
397173252
|
397180669
|
397186650
|
397207541
|
397194179
|
379817337
|
Correctable Codewords |
369203650
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
369203650
|
Uncorrectable Codewords |
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
0
|
Izik
Visitor
•
3 Messages
2 years ago
Same issue, said dns needed to be changed on a call, they did that and issue still occurred
0
0
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Is this a straight modem or gateway? Does it have an event log, or does the next device have any network logging capability (if using a router/firewall)?
The equipment used and network topology is often useful to know.
2
0
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Ok....well. You just don't have much to work with then, and no debug capability.
I don't use Xfinity gear and don't know what the current crippled firmware looks like if you log into the gateway locally these days -- should be at http://10.0.0.1 if you are on your local network. Username/Password == admin/password is the default unless you changed it.
In the past, if you click around in there a bit, perhaps under an "advanced" tab, they had an event log you could look at. I don't know if it's still there or not. Perhaps another forum reader can chime in on that and tell us where it is (if it still exists).
If we just pick a random post from another user like this one: https://forums.xfinity.com/conversations/your-home-network/frequent-t3t4-time-outs-after-severe-weather/64aecf706059bc2b7f1d4474 You can see the log format. I don't know how they got there from the gateway interface.
If it is there, are there any DHCPv6 or DHCP messages, or any other messages? If you can see a log, if you post it, you have to redact the MAC addresses -- alpha numeric strings that have the format "xx:xx:xx:xx:xx" or the forum bot will mark it private and hide your post (personal information).
If there is no log anyplace, when you DO notice a problem, log into the gateway. It should tell you (perhaps on the first page??) what your external IPV4 and IPV6 address is currently. Look for that now. I don't know if it just shows you the IPV6 now or not. If you have a problem, and it's blank -- that's not good, and may help point out an issue.
5
0
XfinitySara
Official Employee
•
1.7K Messages
2 years ago
Hey, @user_9e68ac! Thanks for creating this post about your intermittent connectivity issues. I'm sorry to hear about the increase in frequency (and time), and I would love to help however I can! I see that you've been working with one of our awesome Problem Solvers, which is great :) Our Digital Care Team is here, too, if you decide you'd like to have us run some diagnostics, troubleshoot with you directly, and/or schedule a Trouble Call (tech visit). Just let us know how things are going when you get a chance, and we'll be here for you!
2
0