U

Friday, September 20th, 2024 2:10 AM

Internet Connection Drops Intermittently

I've been experiencing issues where my internet will drop for about 30 seconds at a time, multiple times a day. When I log into my modem (Netgear CM700), there are a lot of error messages and it seems like the problem may be somewhere between Xfinity and my modem. Everything was working great until recently, maybe the past 2 or 3 months. Can anyone help me with this?

There are no splitters between the Xfinity box and my modem.

The cable from the box to my modem appears to be in good condition with tight connections.

Time Priority Description
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 17:30:22 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 18:08:33 Critical (3) No Ranging Response received - T3 time-out
Sep 14 2024 18:08:37 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 14 2024 18:11:28 Critical (3) No Ranging Response received - T3 time-out
Sep 15 2024 09:33:36 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 15 2024 09:36:28 Critical (3) No Ranging Response received - T3 time-out
Sep 15 2024 10:28:45 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 15 2024 12:36:23 Critical (3) No Ranging Response received - T3 time-out
Sep 16 2024 12:47:33 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 16 2024 12:47:38 Warning (5) Lost MDD Timeout
Sep 16 2024 12:49:03 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 16 2024 17:51:34 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2024 09:55:45 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 17 2024 11:41:49 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2024 14:04:20 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 17 2024 18:45:20 Critical (3) No Ranging Response received - T3 time-out
Sep 18 2024 09:01:49 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 18 2024 09:12:45 Critical (3) No Ranging Response received - T3 time-out
Sep 18 2024 11:10:01 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 18 2024 11:37:58 Critical (3) No Ranging Response received - T3 time-out
Sep 18 2024 15:32:19 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 18 2024 16:36:46 Critical (3) No Ranging Response received - T3 time-out
Sep 18 2024 21:03:25 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 18 2024 22:10:23 Critical (3) No Ranging Response received - T3 time-out
Sep 18 2024 23:17:14 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 19 2024 01:27:48 Critical (3) No Ranging Response received - T3 time-out
Sep 19 2024 01:27:49 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 19 2024 03:29:39 Critical (3) No Ranging Response received - T3 time-out
Sep 19 2024 03:29:40 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 19 2024 03:50:00 Critical (3) No Ranging Response received - T3 time-out
Sep 19 2024 11:08:23 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 19 2024 11:08:24 Critical (3) No Ranging Response received - T3 time-out
Sep 19 2024 11:09:28 Critical (3) Ranging Request Retries exhausted
Sep 19 2024 11:09:28 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Sep 19 2024 11:09:52 Critical (3) No Ranging Response received - T3 time-out
Sep 19 2024 12:06:07 Critical (3) Ranging Request Retries exhausted
Sep 19 2024 12:06:07 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Sep 19 2024 12:06:28 Critical (3) No Ranging Response received - T3 time-out
Sep 19 2024 12:14:11 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Sep 19 2024 12:32:35 Critical (3) No Ranging Response received - T3 time-out

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 531000000 Hz Locked
Connectivity State Ok Operational
Boot State Ok Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables
1 Locked QAM 256 4 453000000 Hz 4.0 dBmV 40.3 dB 69602 328840
2 Locked QAM 256 5 459000000 Hz 3.9 dBmV 38.9 dB 59798 243838
3 Locked QAM 256 6 465000000 Hz 3.9 dBmV 38.9 dB 54900 225851
4 Locked QAM 256 7 471000000 Hz 3.9 dBmV 38.9 dB 60848 277979
5 Locked QAM 256 8 477000000 Hz 3.7 dBmV 38.9 dB 46269 168133
6 Locked QAM 256 9 483000000 Hz 3.9 dBmV 38.6 dB 47084 199705
7 Locked QAM 256 10 489000000 Hz 3.9 dBmV 38.9 dB 55244 222019
8 Locked QAM 256 11 495000000 Hz 3.7 dBmV 38.9 dB 39043 130399
9 Locked QAM 256 12 507000000 Hz 4.0 dBmV 38.9 dB 53486 255598
10 Locked QAM 256 13 513000000 Hz 4.0 dBmV 38.9 dB 37909 138366
11 Locked QAM 256 14 519000000 Hz 4.0 dBmV 38.9 dB 36943 163681
12 Locked QAM 256 15 525000000 Hz 3.9 dBmV 38.6 dB 48086 214614
13 Locked QAM 256 16 531000000 Hz 3.5 dBmV 38.9 dB 25640 61959
14 Locked QAM 256 17 537000000 Hz 3.5 dBmV 38.6 dB 33210 144665
15 Locked QAM 256 18 543000000 Hz 3.2 dBmV 38.9 dB 49706 234965
16 Locked QAM 256 19 549000000 Hz 3.2 dBmV 38.6 dB 28633 90150
17 Locked QAM 256 20 555000000 Hz 3.4 dBmV 38.9 dB 31547 150887
18 Locked QAM 256 21 561000000 Hz 3.5 dBmV 38.6 dB 40796 197615
19 Locked QAM 256 22 567000000 Hz 3.7 dBmV 38.6 dB 22513 72655
20 Locked QAM 256 23 573000000 Hz 3.9 dBmV 38.6 dB 22599 97733
21 Locked QAM 256 24 579000000 Hz 3.5 dBmV 38.9 dB 34034 158769
22 Locked QAM 256 25 585000000 Hz 3.7 dBmV 38.9 dB 16399 36283
23 Locked QAM 256 26 591000000 Hz 3.9 dBmV 38.6 dB 28636 139511
24 Locked QAM 256 27 597000000 Hz 3.7 dBmV 38.9 dB 32712 152685
25 Locked QAM 256 28 603000000 Hz 3.5 dBmV 38.6 dB 12857 34349
26 Locked QAM 256 29 609000000 Hz 3.5 dBmV 39.2 dB 4905 57973
27 Locked QAM 256 30 615000000 Hz 3.4 dBmV 38.6 dB 7270 65726
28 Locked QAM 256 31 621000000 Hz 3.2 dBmV 38.6 dB 9658 31574
29 Locked QAM 256 32 627000000 Hz 3.2 dBmV 38.6 dB 5672 61747
30 Locked QAM 256 33 633000000 Hz 3.5 dBmV 38.2 dB 6720 68302
31 Locked QAM 256 34 639000000 Hz 3.7 dBmV 38.2 dB 10443 21080
32 Locked QAM 256 35 645000000 Hz 4.0 dBmV 38.6 dB 5713 55363

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 2560 Ksym/sec 10400000 Hz 43.3 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 16400000 Hz 43.3 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 43.8 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 29200000 Hz 43.8 dBmV
5 Locked ATDMA 5 5120 Ksym/sec 35600000 Hz 44.3 dBmV
6 Locked ATDMA 6 2560 Ksym/sec 40400000 Hz 43.8 dBmV
7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV

Official Employee

 • 

3K Messages

6 months ago

Hey there, user_i8pxu6, thanks for reaching out through Xfinity Forums regarding your internet connection. I rely on my connection for work, so we definitely want to ensure it is working properly for you! I would like to take a look at your connection on our end. 

 

To send a "Direct Message" to Xfinity Support:
Click "Sign In" if necessary
Click the "Direct Messaging" icon or  https://forums.xfinity.com/direct-messaging
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there
- As you are typing a drop-down list appears. Select "Xfinity Support" from that list
- An "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window
Press Enter to send it.

 

15 Messages

6 months ago

same thing has been happening with our Xfinity internet for weeks. Never happened before.

 Cannot get actual help from Xfinity for this, just hours and hours and hours on phone and chat support with people offshored around the world, who can only do limited things. Had a technician visit, he showed us that our modem had been disabled in the Xfinity system. A guy from corporate called and somehow re-enabled the modem, everything was great for about a day then the constant dropping began and has never stopped.

We're going to have to leave Xfinity, cannot work from home with this terrible internet. And Xfinity has wasted just a TON of our time.

3 Messages

It could possible be issues with your equipment. With all the errors in the error log on my modem, I ruled out my router (which is separate from the modem). I boiled it down to either my cable modem or interference in the lines somewhere between Xfinity and my modem. Once the tech tested that I was getting great signal to my modem, I decided that it must be the modem, since it was old and used older DOCSIS 3.0 technology. Since purchasing my new cable modem and getting it set up, my internet has been great. You can just activate it on the Xfinity app pretty easily.

Official Employee

 • 

2.1K Messages

6 months ago

Thanks again for reaching out to us @user_i8pxu6! I'm glad scheduling a technician was able to resolve the intermittent connection issues!

Expert

 • 

109.5K Messages

6 months ago

@XfinityAldrik When are you guys going to start sharing what the solutions are instead of just saying things are solved so that other readers here may benefit ??? After all, this is supposed to be a public help forum and not a private / internal platform.....

(edited)

15 Messages

There is a really extensive problem with XFINITY internet and you are correct, EG, they are not communicating publicly with their customers about this. 

My issue was resolved after FORTY SEVEN HOURS spent by me with XFINITY's "customer support" chat & phone centers. They are a complete & total nightmare. When you finally get through to someone they start at the beginning of their troubleshooting checklist. Never mind if you've JUST been through the steps with the XFINITY "Assistant" app *and* with multiple agents already. This happens over and over and over and over and no agent will ever escalate you to a supervisor, no matter how many times you ask. I've concluded they must get dinged in their job performance evaluations if they ever pass along a call. 

My internet issues started immediately after an area-wide outage that an XFINITY agent told me was probably due to XFINITY 'laying new fiber in your area.' After ** eight years ** of basically totally stable internet, my internet started dropping every 1-4 minutes. I'm a consultant and work from home and it cost me A LOT of income and I've lost some clients because I couldn't even remain on a Zoom or Teams meeting for more than a couple minutes for weeks.

It was a total nightmare. An XFINITY tech came out, the timing was a big inconvenience for me but okay ... and the minute he walked in he said oh! I see your problem, you're using your own equipment! And that was it. He didn't check the line coming into the house, nothing. But he did show me on his XFINITY tech app that it showed my modem had been disabled. He asked when I'd disabled it, and I said I had *never* disabled. it. Some guy later called me from "corporate" and it was a very weird phone call. He asked for my modem's MAC number (or whatever it's called) and after I read it off to him my internet suddenly started working. I asked what he did and he said oh nothing. Acted like it was just coincidental. Then my internet was great and stable -- for ONE DAY. Then the nightmare started all over again, XFINITY internet dropping every 1-4 minutes, total mayhem to my work... and I was back in the XFINITY "support" chat/call vortex.

FINALLY I cried UNCLE!!! And I drove to the nearest XFINITY store to just pick up their freaking equipment. Had to wait 30 minutes in the store to see an agent there, and they were empathetic and said to just contact them in the future. I told them I was losing my mind dealing with the XFINITY call/chat support. 

Set up the modem, then no internet at all. Another THREE HOURS with XFINITY "support" trying to get it fixed. The offshored agents just make stuff up. They said oh! it's your electricity, it's cutting out! (it wasn't, the lights never flickered even on the new modem, etc). FINALLY after three-plus hours, got to an agent who said they were in the Philippines & claimed to be a supervisor. After much time, and once I added a man (my brother) into the call ... they finally said they were "sending through a signal" on the internet line "that only the supervisors can do" ... and ten minutes later the modem started working and the internet has been steady ever since. (you apparently need a man to be talking to these people, there seems to be sexism going on for sure)

Who knows what actually happened to fix the connection. It was entirely an XFINITY line issue. But ... XFINITY has all the power in all of this, they can say whatever they want to show they don't have a problem, but they do.

Today I talked to a friend who lives 20 miles away... about other stuff in our lives, and out of the blue she started complaining that her XFINITY internet has been so bad the past weeks that she can no longer work from home. Said she can't deal with the call & chat agents, can't get anywhere with them.

Comcast/XFINITY needs to come clean with the issues going on everywhere with their equipment.

(and now an Comcast/XFINITY employee will delete this post, saying it's a "rant" -- watch it!) 

(edited)

3 Messages

The problem was solved. The tech came out to my house and tested my lines and my signal quality was great. The problem was my cable modem (Netgear CM700) which was about 5 years old and only a DOCSIS 3.0. I purchased a new cable modem (Motorola B12) from Amazon and have had no issues for the past 4 days.

Official Employee

 • 

2.1K Messages

Good evening @user_fqopy6! It is important to us to get your services working as they should be. I also work from home depend on my internet too. We regret to hear it took multiple attempts to resolve this issue. It should have been resolved within the first tech appointment. We are glad to hear your services are back online and would like to forward your feedback about this experience. Could you please send our team a direct message with your full name and full address? To send a "Direct Message" to Xfinity Support:


Click "Sign In" if necessary
Click the "Direct Messaging" icon or  https://forums.xfinity.com/direct-messaging
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there
 - As you are typing a drop-down list appears. Select "Xfinity Support" from that list
 - An "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window
Press Enter to send it.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

1 Message

30 days ago

We have been having issues with our connection intermittently dropping multiple times per day for many months. A modem reboot generally takes care of the issue, but we both work from home, so dropping out in the midst of almost every zoom meeting is not acceptable. I've had hours wasted with the dumb chat robot and with online technicians. Finally got elevated to a supervisor who admitted it had to be something with the incoming signal. Technicians came out multiple times within 10 days, but the problem persists and is maddening given the constantly increasing cost of the service.

MAC ID of the modem is registered to the account. 

Official Employee

 • 

1.8K Messages

 

NPOPA, Thanks for reaching out to Xfinity Support. Please let us know if your signal is still having trouble dropping. We are here to help. 

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Visitor

 • 

1 Message

1 day ago

We have been having intermittent drops for the last 3 months or a bit less. It is apparently random -- there are not any circumstances we can track that give us any indication of a problem occurring, or when one will occur. It just drops for anywhere between 20 seconds or so and 3 minutes. I wrote a Python program to ping google every second to be able to know how many times this is happening per day. Some days it will happen once, twice, or three or four times. One day it happened 9 times. One day this week it didn't happen at all. We just randomly lose signal, and the script I wrote tells us "100% packet loss" for a period of time. 

The last time this happened, I captured the log file. Unfortunately, it's not capturing the number of hops or any trace route information, or anything all that useful. It's mainly just logging how long our outage occurred. 

2025-04-01 12:25:56 - Ping successful
2025-04-01 12:25:57 - Ping successful
2025-04-01 12:25:58 - Packet loss detected
2025-04-01 12:25:59 - Packet loss detected
2025-04-01 12:26:00 - Packet loss detected
2025-04-01 12:26:01 - Packet loss detected
2025-04-01 12:26:02 - Packet loss detected
2025-04-01 12:26:03 - Packet loss detected
2025-04-01 12:26:04 - Packet loss detected
2025-04-01 12:26:05 - Packet loss detected
2025-04-01 12:26:06 - Packet loss detected
2025-04-01 12:26:07 - Packet loss detected
2025-04-01 12:26:08 - Packet loss detected
2025-04-01 12:26:13 - Packet loss detected
2025-04-01 12:26:38 - Packet loss detected
2025-04-01 12:26:43 - Packet loss detected
2025-04-01 12:26:48 - Packet loss detected
2025-04-01 12:26:53 - Packet loss detected
2025-04-01 12:26:58 - Packet loss detected
2025-04-01 12:27:03 - Packet loss detected
2025-04-01 12:27:08 - Packet loss detected
2025-04-01 12:27:13 - Packet loss detected
2025-04-01 12:27:18 - Packet loss detected
2025-04-01 12:27:23 - Packet loss detected
2025-04-01 12:27:28 - Packet loss detected
2025-04-01 12:27:33 - Packet loss detected
2025-04-01 12:27:38 - Packet loss detected
2025-04-01 12:27:43 - Packet loss detected
2025-04-01 12:27:48 - Packet loss detected
2025-04-01 12:27:53 - Packet loss detected
2025-04-01 12:27:58 - Packet loss detected
2025-04-01 12:28:03 - Packet loss detected
2025-04-01 12:28:08 - Packet loss detected
2025-04-01 12:28:13 - Ping successful
Loss from 2025-04-01 12:26:02 to 2025-04-01 12:28:13 (Duration: 0:02:11.489160)
2025-04-01 12:28:19 - Ping successful
Loss from 2025-04-01 12:28:18 to 2025-04-01 12:28:20 (Duration: 0:00:01.500341)
2025-04-01 12:28:21 - Ping successful
2025-04-01 12:28:22 - Ping successful
2025-04-01 12:28:23 - Packet loss detected
2025-04-01 12:28:24 - Ping successful
Loss from 2025-04-01 12:28:28 to 2025-04-01 12:28:32 (Duration: 0:00:03.498801)
2025-04-01 12:28:33 - Packet loss detected
2025-04-01 12:28:38 - Ping successful
Loss from 2025-04-01 12:28:37 to 2025-04-01 12:28:41 (Duration: 0:00:04.008519)
2025-04-01 12:28:42 - Ping successful
2025-04-01 12:28:46 - Packet loss detected

2025-04-01 12:28:51 - Packet loss detected
2025-04-01 12:28:52 - Packet loss detected
2025-04-01 12:28:53 - Packet loss detected
2025-04-01 12:28:54 - Packet loss detected
2025-04-01 12:28:55 - Packet loss detected
2025-04-01 12:28:56 - Packet loss detected
2025-04-01 12:28:57 - Packet loss detected
2025-04-01 12:28:58 - Packet loss detected
2025-04-01 12:28:59 - Packet loss detected
2025-04-01 12:29:00 - Packet loss detected
2025-04-01 12:29:01 - Ping successful
Loss from 2025-04-01 12:28:50 to 2025-04-01 12:29:41 (Duration: 0:00:51.070229)
2025-04-01 12:29:42 - Ping successful
2025-04-01 12:29:43 - Packet loss detected
2025-04-01 12:29:44 - Packet loss detected
2025-04-01 12:29:45 - Packet loss detected
2025-04-01 12:29:46 - Ping successful
Loss from 2025-04-01 12:29:47 to 2025-04-01 12:29:54 (Duration: 0:00:07.501180)
2025-04-01 12:29:55 - Ping successful
2025-04-01 12:29:56 - Ping successful
2025-04-01 12:29:57 - Ping successful

We have had someone check the signals, and replace our XFi gateway, and check our cabling. We have had someone install a powered splitter and rewire the cable inside our house. We have had someone put a new temporary line down, which they then dug to make permanent. Each time we had hopes that it would solve the problem, but the problem persists.

It is VERY intermittent. Some days it does not happen. Some days it happens several times through the day and night. It does not seem to be based on our usage, since it happens at night when we sleep as well.

We can't have this. We CAN'T.... my wife and I both work from home. Up until a couple of months ago, we NEVER lost Zoom calls or VPN connections, and we always had an always-on, persistent connection. For at least a dozen years or more. NEVER had any problems, and then in November of last year (2024) some guy from Xfinity stopped by to tell us we were on their list to check in with, while they were going to be doing some "upgrades" to the system and lines in the area. That's one thing I've seen other people post about here that we have in common. Several posts seem to indicate that in places or times when they said they were going to start doing "upgrades", these problems started occurring during that period or afterward. 

It's only been in the last 2 or 3 months, I think, that this has occurred. So we strongly believe the problem is not with our cabling, or our router, or anything inside our home. But we CANNOT keep having this problem -- it's putting me at problems with my job if it continues. Right now, I call in to Zoom calls on my cell phone in addition to joining on my computer, so that I can apologize to people on the call if and when my connection drops suddenly.

When they put in the temporary cable, things still were intermittent. The only time it seemed to be *slightly* more reliable was after we disconnected the router overnight and then reconnected it. Full disclosure: the reason we disconnected the router was because I'd ordered a T-Mobile 5G Internet Gateway to test it out, because we were SO frustrated with these problems that I was willing to test out another high-speed internet provider. But the bottom line is that the 5G signal from T-Mobile was even less reliable than Xfinity.  It dropped constantly, despite having halfway decent signal strength (it was never great signal strength). So we ditched the T-mobile gateway since we were still well within their 15 day return period, and plugged the XFi router back in. Well, when we did that, it worked with no issues for about 5 days. Didn't see any packet losses during that time. But then sure enough, it started up again just 5 days later. It may have been a total coincidence that we didn't have any signal loss during those 5 days... it doesn't seem logical to me that 5 days later, things would suddenly go bad again. Unless maybe Xfinity is doing something funky with IP address assignments, and we were somehow in an uncongested IP range or something during that time until things caught up with us. I don't know. I'm grasping at straws. I wish there were a way to figure out from here where the problem is, but I strongly suspect the issue is with Xfinity's INFRASTRUCTURE, since the signal loss happened after they said they'd be doing system upgrades in the area, AND since we'd had no problems before, AND since I see other people questioning this as well.

It's really awful. I would gladly update this post with the solution if we got one. If it gets resolved, I'd go back to loving Xfinity again, even though it's expensive. But I tell you what, if AT&T puts in the infrastructure here to give me comparable speed and better reliability, I'm gone.  We are stuck in an area that seems to be only serviced by Xfinity and T-Mobile for now, and even Verizon isn't an option at the moment. 

Anyone got any ideas on how to resolve this? Please? Anyone?

forum icon

New to the Community?

Start Here