Visitor

 • 

1 Message

Thursday, November 19th, 2026

Internet drops: 54 outages in 29 hrs

·

Summary

My Cox Panoramic gateway keeps losing its connection to Cox while staying physically connected to my router. Between Nov 17 at 17:09 and Nov 18 at 21:56 (about 29 hours), automated monitoring recorded 54 outages totalling about 32 minutes. In 37 of them, Cox's first-hop gateway (184.181.66.1) and the internet (1.1.1.1) stopped answering at the same time.

  • The Ethernet link between the gateway and my router stayed up for 52 of the 54 outages, so the gateway is not rebooting and the in-home Ethernet is not the cause.
  • The outages happen most often in the afternoon and evening, peaking at 8 per hour on Nov 18 (13:00, 14:00, 17:00 and 21:00).
  • The gateway's Ethernet log also shows 19 drop clusters since July 18, 10 of them with the 41–77 second dead-link pattern of a modem reset.

Request: remote line diagnostics first (signal levels, SNR, T3/T4 timeouts, node noise and the gateway's reboot history), then a fix on Cox's side or a gateway swap. A technician visit only if the remote checks find a fault that needs one. Monitoring is still running, and the full logs are available on request.

Service and equipment

Item

Value

Account holder

Brandon Tucker

Cox account number

XXXXXX

Service address

XXXXXX

Cox gateway

Technicolor CGM4981COM (Panoramic Wifi Gateway), Cox rental, bridge mode

Gateway serial

xxxx8XXXXXXX

WAN IP (DHCP from Cox)

184.181.XXXXX

Cox default gateway

184.181.XXXX

Cox DHCP server / relay

172.19.121.111

Cox DNS

68.105.28.11, 68.105.29.11

Customer router

MikroTik hAP ac³, RouterOS 7.23.2, WAN port ether1 at 1 Gbps full duplex

How it was measured

The customer router pinged two targets every 10 seconds and logged each change between up and down, with timestamps (Central time).

Probe

Target

What a failure means

Cox first hop

184.181.66.1

No path from the gateway to Cox's network

Internet

1.1.1.1

No path to the internet

Ethernet link

Router ether1 to gateway

The gateway rebooted or its Ethernet port dropped

What was ruled out on the customer side:

  • Router: 10 weeks of uptime, no crashes, 72 MiB of 256 MiB memory free, 4% CPU, 180 tracked connections.
  • CGNAT / double NAT: the WAN address is the public IP 184.181.67.196, confirmed by an external lookup.
  • In-home Ethernet: the link stayed up at 1 Gbps full duplex during 52 of the 54 outages.

A single lost ping can register as a short outage, and Cox's gateway may give pings low priority. For that reason the 37 outages where both targets failed together are the strongest evidence.

Findings

The connection to Cox drops repeatedly while the gateway stays physically connected. It is quiet overnight and worst from midday through the evening.

 

Outage type

Count

What it indicates

Cox first hop and internet down together

37

No path from the gateway to Cox: the RF/DOCSIS side or the node

Cox first hop only

9

Possibly Cox's gateway dropping pings; weaker evidence

Internet only

8

A single lost probe or an upstream Cox issue; weaker evidence

Total

54

About 32 minutes of downtime; median about 18 s, longest 203 s

The gateway's Ethernet link to the router stayed up through 52 of the 54 outages.

Full outage log (Nov 17–18)

All 54 outages, newest first, Central time. Down events less than 60 seconds apart are merged into one outage. "Both" means Cox's first hop (184.181.66.1) and the internet (1.1.1.1) failed together.

Date

Start

End

Duration (s)

Failed targets

Ethernet link dropped

Nov 18

21:56:10

Still down at log export

—

Both

No

Nov 18

21:50:50

21:51:07

17

Both

No

Nov 18

21:45:10

21:45:19

9

Both

No

Nov 18

21:41:10

21:41:18

8

Both

No

Nov 18

21:37:20

21:37:57

37

Both

No

Nov 18

21:32:40

21:32:57

17

Both

No

Nov 18

21:17:19

21:17:37

18

Both

No

Nov 18

21:00:59

21:01:47

48

Both

No

Nov 18

20:11:38

20:12:46

68

Both

No

Nov 18

20:06:38

20:07:26

48

Both

No

Nov 18

19:46:28

19:47:45

77

Both

No

Nov 18

18:03:07

18:03:14

7

Cox first hop only

No

Nov 18

18:00:47

18:01:34

47

Both

No

Nov 18

17:56:57

17:57:04

7

Cox first hop only

No

Nov 18

17:54:19

17:55:56

97

Both

No

Nov 18

17:48:27

17:49:56

89

Both

No

Nov 18

17:44:59

17:45:14

15

Both

No

Nov 18

17:35:27

17:35:55

28

Both

No

Nov 18

17:33:08

17:33:54

46

Both

No

Nov 18

17:19:08

17:19:15

7

Internet only

No

Nov 18

17:05:17

17:05:24

7

Cox first hop only

No

Nov 18

15:59:47

16:01:04

77

Both

No

Nov 18

15:49:17

15:49:26

9

Both

No

Nov 18

15:27:27

15:27:34

7

Cox first hop only

No

Nov 18

15:05:18

15:05:35

17

Internet only

No

Nov 18

14:59:36

14:59:54

18

Both

No

Nov 18

14:57:27

14:57:35

8

Internet only

No

Nov 18

14:46:06

14:47:14

68

Both

No

Nov 18

14:35:46

14:37:35

109

Both

No

Nov 18

14:21:16

14:21:35

19

Both

No

Nov 18

14:14:46

14:14:54

8

Both

No

Nov 18

14:13:27

14:13:34

7

Internet only

No

Nov 18

14:06:37

14:07:03

26

Both

No

Nov 18

13:55:56

13:56:33

37

Both

No

Nov 18

13:53:27

13:54:13

46

Both

No

Nov 18

13:41:06

13:41:44

38

Both

No

Nov 18

13:15:06

13:15:14

8

Cox first hop only

No

Nov 18

13:10:47

13:10:54

7

Internet only

No

Nov 18

13:08:06

13:08:54

48

Both

No

Nov 18

13:05:37

13:06:03

26

Both

No

Nov 18

13:03:27

13:03:43

16

Both

No

Nov 18

12:59:57

13:00:06

9

Internet only

No

Nov 18

12:42:35

12:42:43

8

Cox first hop only

No

Nov 18

12:32:15

12:32:22

7

Cox first hop only

No

Nov 18

12:14:27

12:14:34

7

Internet only

No

Nov 18

11:24:54

11:26:14

80

Both

No

Nov 18

11:01:37

11:02:21

44

Both

No

Nov 18

10:51:53

10:52:26

33

Both

No

Nov 18

04:11:36

04:11:43

7

Internet only

No

Nov 18

03:51:51

03:51:58

7

Cox first hop only

No

Nov 17

21:34:40

21:34:47

7

Cox first hop only

No

Nov 17

21:21:39

21:22:06

27

Both

No

Nov 17

18:41:42

18:45:05

203

Both

Yes (6 drops)

Nov 17

18:11:57

18:14:49

172

Both

Yes (5 drops)

In both Nov 17 events with a link drop, Cox connectivity failed 14–22 seconds before the Ethernet link dropped. That points to the gateway losing its connection to Cox first and then resetting. These two events overlap a Cox support chat that evening; if Cox reset the gateway remotely at those times, they can be set aside. The other 52 still stand.

Gateway Ethernet link-drop history (Jul 18 – Nov 17)

The router logged 19 clusters of drops on the gateway's Ethernet link. Ten of them have a modem-reset signature: 41–77 seconds of dead link, then repeated short drops over 2–10 minutes. Four of those happened at about 3 AM.

Start

Drops

Cluster length

First outage

Reset signature

Nov 17 18:41:56

6

2 min 53 s

41 s

Yes

Nov 17 18:12:19

5

2 min 16 s

43 s

Yes

Nov 17 11:25:56

2

8 s

7 s

No

Oct 20 22:24:44

1

—

15 s

No

Oct 20 03:04:39

5

2 min 16 s

43 s

Yes

Oct 17 18:08:58

9

6 min 38 s

64 s

Yes

Oct 9 05:51:37

2

1 min 4 s

7 s

No

Oct 9 03:31:39

7

6 min 26 s

71 s

Yes

Sep 12 14:54:59

2

4 min 22 s

5 s

No

Sep 12 10:34:14

1

—

11 s

No

Sep 8 18:02:26

7

6 min 25 s

64 s

Yes

Sep 8 17:32:25

5

2 min 30 s

70 s

Yes

Sep 8 11:22:02

2

1 min 41 s

7 s

No

Aug 25 03:04:46

5

6 min 35 s

72 s

Yes

Aug 13 03:06:20

6

6 min 33 s

63 s

Yes

Aug 9 14:20:29

2

36 s

6 s

No

Jul 30 13:32:56

1

—

9 s

No

Jul 24 12:20:35

1

—

9 s

No

Jul 18 17:22:27

9

9 min 22 s

77 s

Yes

Not shown: the drops on Sep 8 between 12:57 and 10:54 (the clock was reset), which were a restart of the customer router, not a Cox issue.

Requested action

Please run these checks remotely first. A technician visit is a last resort, only if the results show a fault that can't be fixed from Cox's side:

  1. Downstream and upstream signal levels and SNR on all bonded channels, with the gateway's T3/T4 timeout counts and event log for Nov 17–18.
  2. The gateway's reboot history since July 18.
  3. Upstream noise and ingress at my node, especially in the afternoon and evening when outages peak, and any known outages or maintenance in my area on Nov 17–18.
  4. If the signal is clean but the gateway keeps losing its connection to Cox, approve a swap of the CGM4981COM, at a Cox store or by mail, with bridge mode re-applied.

The gateway must stay in bridge mode. A factory reset puts it back on 10.0.0.1/24, which conflicts with the customer's own network.

Customer-side steps already taken:

  • Router health checked and ruled out (no crashes, low load).
  • Public IP confirmed, so no CGNAT or double NAT.
  • Continuous monitoring of the Cox first hop and the internet since Nov 17 at 17:09.
  • In-home coax splitter: removed .

Monitoring is still running, and logs from after the splitter change can be sent on request.

Oldest First
Selected Oldest First

Moderator

 • 

759 Messages

9 hours ago

brandontict - We can definitely take a look at your equipment. Please reach out to us at https://www.facebook.com/Spectrum/ or http://m.me/Spectrum. Thank you! 
-Steff

Recent Discussions

View More

Loading...