Skip to main content

    Support

    Offers

U
user_ehxqie
1st Topic
1st Reply
Conversation Starter

10 Messages

Tuesday, June 10th, 2025 6:34 PM

Exact same intermittent drops/disconnects through the day which happened last year around the exact same time in the summer

Hello,

I posted about this last year and am having the exact same issues.  Throughout the remainder of the summer, after a technician visited and said that there was line work, which had nothing to do with my house or modem, throughout all of the fall, throughout all of the winter, and throughout all of the spring leading up to the beginning of summer when, coincidentally school are out, I have had little to no issues with my internet, during storms, snow, and all other inclement weather.  Around the beginning of June, which coincides with schools being out for the summer, I have had seemingly random disconnects and intermittent outages through the day, starting around 11:00 and ending around 17:00. 

I have been running WinMTR for the last two to three hours and have between 20-25% packet loss when pinging google at 15 second intervals with 64 byte packets.  Yet again, my modem's log shows the exact same Timing Synchronization Failures that it showed last year, which, up until the beginning of June, has not been happening consistently.

Event Log

   Log

Error! Filename not specified.

 

Error! Filename not specified.
  

 Time 

 Priority 

 Description 

 Tue Jun 10 12:34:23 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:34:24 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:36:16 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:36:19 2025  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:47:12 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:47:18 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:47:35 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:47:36 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:47:58 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:47:58 2025  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:48:02 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:50:00 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:50:02 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:59:13 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 12:59:17 2025  

 Critical (3) 

 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:05:16 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:05:20 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:05:31 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:05:33 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:06:02 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:06:09 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:06:09 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:06:10 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:06:40 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:07:16 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:07:16 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:07:18 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:07:28 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:07:33 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:08:07 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:08:08 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:08:18 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:08:19 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:11:35 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:11:37 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:12:06 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:12:08 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:13:24 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:13:24 2025  

 Critical (3) 

 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 Tue Jun 10 13:13:35 2025  

 Warning (5) 

 MDD message timeout;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.0; 

 

 

 

WinMTR statistics

Host

%

Sent

Recv

Best

Avrg

Wrst

Last

unknown

  0

519

519

  0

  1

 37

  0

192.168.0.1

  0

519

519

  1

  1

 28

  1

96.120.9.45

 23

612

472

  0

140

4650

 10

po-302-1222-rur02.140mkt.pa.pitt.comcast.net

 23

612

472

  8

122

4649

  9

be-27-rar01.lancaster.pa.pitt.comcast.net

 22

608

475

  0

144

4649

 10

be-34-ar01.mckeesport.pa.pitt.comcast.net

 25

620

469

  0

150

4652

 19

be-31611-cs01.pittsburgh.pa.ibone.comcast.net

 23

608

474

 17

137

4603

 21

be-1111-cr11.pittsburgh.pa.ibone.comcast.net

 21

602

477

 18

155

4799

 19

be-304-cr12.beaumeade.va.ibone.comcast.net

 26

625

466

 23

143

4668

 24

be-4412-pe12.ashburn.va.ibone.comcast.net

 23

611

473

 24

161

4667

 27

No response from host

100

1554

  0

  0

  0

  0

  0

192.178.45.33

 23

610

473

 26

146

4668

 27

192.178.242.24

 23

610

473

 27

150

4667

 28

142.251.49.189

 30

647

455

 26

146

4428

 29

142.251.69.20

 28

638

460

 27

138

4667

 28

142.251.69.0

 22

608

475

 27

163

4667

 28

192.178.106.19

 22

606

475

 27

145

4667

 28

142.251.65.115

 23

610

473

 26

140

4667

 28

lga34s36-in-f4.1e100.net

 22

604

476

 27

134

4668

 28

The WinMTR was pulled at 14:32.  The "No Response from Host" seems to be sending packets at an approximate 5 second interval and is not significant.

 

Question

 • 

Updated 

2 days ago

 • Edited

15

3

0

XfinityMarshante

Official Employee

 • 

135 Messages

2 days ago

Hello @user_ehxqie, Thank you for taking the time out of your day to leave a post. I hope your week is off to a great start. Thank you for providing the details about your issue.  Sorry to hear that the issue has returned. If you could send our team a direct message with your full name, the name listed on the account (if different), and the service address associated with your account, I'd be more than happy to look into this for you.

0

0

EG

Expert

 • 

111K Messages

2 days ago

@user_ehxqie @XfinityMarshante 

Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.

0

0

user_ehxqie

10 Messages

2 days ago

As a follow-up to my original post from earlier, it's 20:52 and here are the results of letting WinMTR run all day:

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
unknown 0 2045 2045 0 1 43 0
192.168.0.1 1 2046 2045 1 1 34 1
96.120.9.45 7 2141 1998 0 40 4650 9
po-302-1222-rur02.140mkt.pa.pitt.comcast.net 7 2139 1999 8 36 4649 8
be-27-rar01.lancaster.pa.pitt.comcast.net 7 2135 2000 0 43 4649 11
be-34-ar01.mckeesport.pa.pitt.comcast.net 8 2146 1995 0 50 4652 18
be-31611-cs01.pittsburgh.pa.ibone.comcast.net 7 2139 1998 17 47 4603 22
be-1111-cr11.pittsburgh.pa.ibone.comcast.net 6 2129 2003 18 52 4799 19
be-304-cr12.beaumeade.va.ibone.comcast.net 8 2153 1991 22 53 4668 27
be-4412-pe12.ashburn.va.ibone.comcast.net 7 2145 1995 24 60 4667 27
142.251.78.61 100 6130 3 0 26 27 26
192.178.45.33 7 2137 2000 26 56 4668 29
192.178.242.24 7 2139 1998 26 57 4667 28
142.251.49.189 16 2279 1929 26 57 4428 28
142.251.69.20 10 2176 1980 27 55 4667 29
142.251.69.0 7 2134 2001 23 61 4667 28
192.178.106.19 7 2134 2001 26 56 4667 28
142.251.65.115 7 2138 1999 25 55 4667 27
lga34s36-in-f4.1e100.net 7 2132 2002 25 53 4668 31

Event log from modem (truncated to 13:07:16 today):

Event Log
   Log  
  
 Time   Priority   Description 
 Tue Jun 10 13:07:16 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:07:16 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:07:18 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:07:28 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:07:33 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:08:07 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:08:08 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:08:18 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:08:19 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:11:35 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:11:37 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:12:06 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:12:08 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:13:24 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:13:24 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:20:38 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:20:56 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:21:46 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:21:47 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:22:04 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:22:17 2025    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:23:42 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:23:44 2025    Critical (3)   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
 Tue Jun 10 13:34:31 2025    Warning (5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.0; 
     

So after running for a little over 6 hours, we can see that WinMTR shows significantly less packet loss, which makes sense that it is skewed as well due to the sheer amount that were lost earlier today.  Again, this happened last summer around the beginning of June/end of May, was resolved, and started up again about a week ago, and has bothered me enough to create another thread.

(edited)

0

0

forum icon

New to the Community?

Start Here