Forum Discussion

paddle_thud's avatar
paddle_thud
New Contributor
9 months ago

Intermittent connectivity in Tulsa

Hi all, since last Sunday's storm, I am getting constant drops in connectivity.  

Modem is SB6190.  It was provisioned in January and was working ok.  I don't believe anything has changed on my end.  No splitter used in modem connection.

Ping Potter snapshot:  https://ibb.co/fSzPb2T

Time Priority Description
Sat Jun 24 17:06:13 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:06:23 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:06:28 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:06:48 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:06:49 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:07:13 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:07:23 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:08:16 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:08:19 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:08:54 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:08:58 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:09:03 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:09:10 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:11:19 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:11:24 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:14:29 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:14:48 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:15:09 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:15:12 2023 5 RCS Partial Service;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 24 17:17:06 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a8:97:cd:e3:60:93;CMTS-MAC=00:59:dc:78:ce:b4;CM-QOS=1.1;CM-

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked 256QAM 21 903.00 MHz -4.50 dBmV 38.61 dB 50831 405534
2 Locked 256QAM 1 783.00 MHz -4.10 dBmV 38.61 dB 4 0
3 Locked 256QAM 2 789.00 MHz -3.70 dBmV 38.61 dB 10 0
4 Locked 256QAM 3 795.00 MHz -5.00 dBmV 38.98 dB 3 0
5 Locked 256QAM 4 801.00 MHz -4.30 dBmV 38.98 dB 31 0
6 Locked 256QAM 5 807.00 MHz -5.00 dBmV 38.61 dB 0 0
7 Locked 256QAM 6 813.00 MHz -4.90 dBmV 38.98 dB 0 0
8 Locked 256QAM 7 819.00 MHz -5.10 dBmV 38.61 dB 0 0
9 Locked 256QAM 8 825.00 MHz -5.00 dBmV 38.98 dB 0 0
10 Locked 256QAM 9 831.00 MHz -5.40 dBmV 38.98 dB 0 0
11 Locked 256QAM 10 837.00 MHz -4.00 dBmV 38.61 dB 3 0
12 Locked 256QAM 11 843.00 MHz -4.60 dBmV 38.61 dB 16 0
13 Locked 256QAM 12 849.00 MHz -4.50 dBmV 38.61 dB 10 0
14 Locked 256QAM 13 855.00 MHz -3.40 dBmV 39.85 dB 18 0
15 Locked 256QAM 14 861.00 MHz -4.10 dBmV 38.61 dB 11 0
16 Locked 256QAM 15 867.00 MHz -3.80 dBmV 38.98 dB 9 0
17 Locked 256QAM 16 873.00 MHz -4.50 dBmV 38.98 dB 19 0
18 Locked 256QAM 17 879.00 MHz -5.10 dBmV 38.61 dB 115 1126
19 Locked 256QAM 18 885.00 MHz -4.50 dBmV 38.61 dB 154 1064
20 Locked 256QAM 19 891.00 MHz -5.20 dBmV 38.98 dB 0 0
21 Locked 256QAM 20 897.00 MHz -5.00 dBmV 38.98 dB 0 0
22 Locked 256QAM 22 909.00 MHz -4.60 dBmV 38.98 dB 75291 576867
23 Locked 256QAM 23 915.00 MHz -4.60 dBmV 38.61 dB 82366 614956
24 Locked 256QAM 24 921.00 MHz -3.50 dBmV 38.98 dB 71249 561489
25 Locked 256QAM 25 927.00 MHz -3.70 dBmV 38.60 dB 301 8856
26 Locked 256QAM 26 933.00 MHz -3.80 dBmV 38.20 dB 21 0
27 Locked 256QAM 27 939.00 MHz -2.00 dBmV 38.90 dB 8 0
28 Locked 256QAM 28 945.00 MHz -2.80 dBmV 38.90 dB 0 0
29 Locked 256QAM 29 951.00 MHz -1.70 dBmV 39.20 dB 8 0
30 Locked 256QAM 30 957.00 MHz -1.00 dBmV 38.60 dB 11 0
31 Locked 256QAM 31 963.00 MHz -1.50 dBmV 39.50 dB 9 0
32 Locked 256QAM 32 969.00 MHz -1.90 dBmV 38.90 dB 13 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 3 5120 kSym/s 20.70 MHz 40.25 dBmV
2 Locked ATDMA 4 5120 kSym/s 27.10 MHz 40.25 dBmV
3 Locked ATDMA 2 2560 kSym/s 15.90 MHz 40.25 dBmV
4 Locked ATDMA 1 2560 kSym/s 12.60 MHz 39.75 dBmV

6 Replies

Replies have been turned off for this discussion
  • WiderMouthOpen's avatar
    WiderMouthOpen
    Esteemed Contributor

    Looks like noise/ingress in the 900Mhz range, probably from cellular. My guess is damage to the lines out on the street from the storm. I would give it a few days and then call in to schedule a technician. They are probably crazy busy right now.

    Does it still show as a outage when you sign into Cox.com? Any obvious damage to the line going from the street to your house?

    • paddle_thud's avatar
      paddle_thud
      New Contributor

      Thanks for the reply.  Last reported outage from Cox in my area was either Mon or Tue.   As of about 1pm today, the connection has stabilized (no more lost packets).  Had to do a reboot...connection was totally lost.  I tried for days to get Cox to confirm there was a connectivity issue but you know how that goes. Whatever they fixed/remedied was a covert op.

      • WiderMouthOpen's avatar
        WiderMouthOpen
        Esteemed Contributor

        Glad it worked itself out. I kind of had a feeling it would in a couple of days. Let us know if the problem returns.

    • Darkatt's avatar
      Darkatt
      Valued Contributor III

      900mhz could ALSO be a very old cordless phone, 2 way communications/ some of the older wireless headsets. 

      • WiderMouthOpen's avatar
        WiderMouthOpen
        Esteemed Contributor

        I doubt it's local/nearby ingress considering OP said nothing on their side changed and they just had a huge storm. Also considering we had another post mentioning disconnects in Tulsa I think they have an area wide issue. See post here and here. For every post we see I guess the call centers see 100+ calls.