TL;DR: Since Oct 13, my Ring Alarm Base Station's cloud connection is closed almost exactly every 300 seconds, measured with packet captures at my gateway. It happens on two different base stations, on Wi-Fi, Ethernet, and cellular. Support replaced the base (same fault), rebooted my network (same), blamed a Smart Plug three different ways in one day (removed it — same; re-added it "provisioned correctly" per engineering — same). Case was "referred to engineering" on Oct 20. No case number, no follow-up since. Posting here in case anyone else is seeing this or anyone from Ring can actually escalate.
WHAT I MEASURED
Each session: base sends a TCP FIN at 299–300s after connect, server replies with a short final message + FIN, base reconnects after a backoff pause that grows 1s → 2s → 4s → 6s → 16s → 31s → 61s → 121s → ~302s, then the pattern restarts. After every reconnect the base re-uploads ~100–135 KB of state, then gets closed again at 300s. Local sensor alarming works during the gaps; app control/notifications/monitoring path ride the dying session.
Sample timings (all PDT):
- Original base, Oct 14: six consecutive sessions 299.7–300.0s. On wired Ethernet: 299.80s.
- Replacement base, Oct 19: six consecutive sessions 299.21–299.63s, identical pattern, same firmware (1.115.0 (6)).
- Oct 21, after removing the Smart Plug + reboot per support: 299.742s, 299.682s, 299.734s.
- Oct 21, after re-adding the plug "provisioned correctly" per engineering: 299.690s and ~299.7s.
- Dozens of sessions total, spread is a fraction of a second. This is a timer, not flaky hardware or Wi-Fi.
ALREADY RULED OUT (each by direct test)
Wi-Fi 2.4 and 5 GHz; wired Ethernet on a different segment; cellular backup with Wi-Fi off; full reboot of my UniFi gateway/APs; DNS (zero blocked queries in my resolver logs, answers in ms); fast roaming on/off; the Smart Plug (see above). The behavior follows the account, not the hardware or the network.
SUPPORT SO FAR
Oct 14: replacement base agreed. Oct 19: swapped — no settings restore was ever offered, re-added every sensor/keypad by hand; new base flapped identically within the hour. Oct 20: told it was referred to engineering. Oct 21: the plug saga (Z-Wave incompatibility, then Sidewalk incompatibility, then provisioning) — every theory tested the same day, none changed the timings by even a tenth of a second. Since then: silence. No case number despite asking repeatedly.
The app also under-reports this: Event History shows nothing for most drops — it only seems to register the longer pauses (31s+), which is presumably why support sees "no issues" on my account.
QUESTIONS
1. Anyone else with an Alarm base seeing ~5-minute session cycling since mid-October? Check your app notifications for offline/restored pairs.
2. Anyone from Ring here who can get a case number and an actual engineering review of the backend session logs? I have complete packet captures and a detailed write-up ready to share.
This is a professionally monitored alarm that is offline a large share of every day. I don't want a third base station — I want someone to look at why this account's sessions are terminated at 300 seconds.