Clients/Rancho-Ynecita/slack/2026/01/2026-01-16_rancho-ynecita.md

# #rancho-ynecita — 2026-01-16 **10:53 [Kevin](https://slack.com/archives/C09D358F91R/p1768589599240089):** comm fail alarm to Estes **10:53 [Kevin](https://slack.com/archives/C09D358F91R/p1768589613562429):** checking with Paul to see if they are doing something out there **11:01 [Kevin](https://slack.com/archives/C09D358F91R/p1768590112665019):** comm fail cleared **11:02 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768590125664129):** It's been coming in and out before today. **11:02 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768590147509529):** Comm fails were a severity 2 which gives a 5 minute delay before announcing. **11:02 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768590158572819):** So they've been clearing before we get notified. **11:02 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768590173195969):** I updated comm fails to severity 1. They seem important. **11:03 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768590200330349):** But there is often a delay > 5 minutes before that comm ok bit comes back **11:03 [Mason Radke](https://slack.com/archives/C09D358F91R/p1768590213764619):** At least that’s my current understanding of why that alarm is coming in **11:54 [Kevin](https://slack.com/archives/C09D358F91R/p1768593245676479):** coyp