Community Forum

Connectivity Issues

Regular Visitor

Connectivity Issues

Hello, 

I have been having issues with a slow connection for the last couple of weeks. I pay for Blast Tier internet (250 mbps) and have only been getting speeds of up to 10mbps. After a couple of calls to Comcast, they sent a tech out, who assured me that my signal was "almost perfect" and that the issue was my modem. Before buying a new one, I just wanted to confirm that this course of action makes sense to everyone. 

 

Thanks in advance!

 

My modem stats are as follows for the past couple of weeks: 

Downstream: 

1 Locked QAM256 9 625750000 Hz 5.5 dBmV 41.5 dB 0 0
2 Locked QAM256 1 577750000 Hz 7.4 dBmV 42.6 dB 0 0
3 Locked QAM256 2 583750000 Hz 7.2 dBmV 42.5 dB 0 0
4 Locked QAM256 7 613750000 Hz 6.4 dBmV 40.5 dB 0 0
5 Locked QAM256 8 619750000 Hz 6.0 dBmV 40.4 dB 0 0
6 Locked QAM256 15 661750000 Hz 6.2 dBmV 41.1 dB 0 0
7 Locked QAM256 16 667750000 Hz 6.5 dBmV 41.3 dB 0 0
8 Locked QAM256 21 697750000 Hz 6.5 dBmV 41.8 dB 0 0
9 Locked QAM256 24 715750000 Hz 5.4 dBmV 41.1 dB 0 0
10 Locked QAM256 25 721750000 Hz 5.6 dBmV 41.1 dB 0 0
11 Locked QAM256 26 727750000 Hz 5.2 dBmV 40.8 dB 0 0
12 Locked QAM256 28 739750000 Hz 5.0 dBmV 26.1 dB 1634933 3137166
13 Locked QAM256 29 745750000 Hz 5.1 dBmV 30.6 dB 3876993 2450761
14 Locked QAM256 30 751750000 Hz 4.9 dBmV 0.0 dB 94879 499589
15 Locked QAM256 31 757750000 Hz 4.9 dBmV 34.6 dB 9408432 2875493
16 Locked QAM256 32 763750000 Hz 4.5 dBmV 33.3 dB 4695543 7981606

 

Upstream: 

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 51 5120 Ksym/sec 23700000 Hz 40.5 dBmV
2 Locked ATDMA 49 5120 Ksym/sec 36500000 Hz 41.0 dBmV
3 Locked ATDMA 50 5120 Ksym/sec 30100000 Hz 41.0 dBmV

 

Recent events: 

Thu Jan 24 18:32:05 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 25 01:32:45 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 25 13:43:22 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 25 18:09:29 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 25 18:38:04 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 26 06:33:42 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 26 07:14:11 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Jan 26 17:58:34 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 27 05:24:52 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 27 13:26:38 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 27 14:17:46 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 27 18:55:26 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 27 19:14:43 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jan 27 21:54:54 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 28 08:45:52 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 28 14:51:17 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jan 28 15:15:56 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jan 28 18:59:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 28 19:14:15 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 29 05:00:49 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 29 06:50:16 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 29 08:52:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Tue Jan 29 15:40:50 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 01:20:14 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 01:30:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 04:55:18 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 05:44:22 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 06:16:36 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 06:32:01 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 07:58:51 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 11:09:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 15:45:15 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 22:13:11 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 22:34:13 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Wed Jan 30 23:17:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 00:47:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 02:33:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 03:04:37 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 05:30:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 05:35:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 10:07:40 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 10:17:30 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 11:27:09 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 13:44:49 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 31 22:11:52 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 01 01:08:13 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Fri Feb 01 01:09:28 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Fri Feb 01 12:24:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 01 13:49:59 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 01 16:32:06 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 01 17:38:32 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 01 20:09:11 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 02 09:52:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 02 10:54:17 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 02 13:03:05 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 02 13:26:54 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 02 14:28:31 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 03 09:24:25 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 03 17:19:38 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 03 22:41:10 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Feb 03 22:44:27 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Feb 04 16:05:46 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:05:53 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:06:20 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:14:06 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:14:27 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:14:28 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:15:30 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:15:37 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:15:41 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:15:42 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:18:26 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:18:28 2019 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 04 16:19:30 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9f:ba:7e;CMTS-MAC=00:01:5c:71:92:50;CM-QOS=1.1;CM-VER=3.0;

 

Regular Visitor

Re: Connectivity Issues

Should mention that my modem is an Arris sb6183. Thanks. 

Expert

Re: Connectivity Issues

Nope. Not "perfect". There is a signal / connection quality (SNR) problem from channel 12 on. I would get the techs re-involved until it is fixed right ! Show them this thread.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: Connectivity Issues

Really appreciate the response. Every time I call Xfinity, they continue to claim it's my modem and have not offered to send another tech out. Any Xfinity employees on this forum that can help me out?

Expert

Re: Connectivity Issues

Hi @icaforp

Thank you for visiting the forums!

I've asked an employee to assist you. You should expect a reply in this thread. 


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: Connectivity Issues

Thanks a million!

Official Employee

Re: Connectivity Issues

Hello @icaforp, thanks for reaching out and I can assist you with the connection issues you are experiencing! Can you please send me a Private Message including the full name as it appears on the account and your full name if different?

 

To send me a Private Message, please click my name “ComcastAmira” and click “send a message".


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: Connectivity Issues

@icaforp, I'm happy the tech came out and resolved the issue on your end! Please be sure to reach out to us for any future issues or concerns. Thank you! 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!