Content
# #south-county — 2026-03-18
**06:58 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773842331770589):**
![[F0AMRRTP5L1_Image_from_iOS]]
**06:59 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773842348104489):** These are going crazy. I'll take a look today and see what I can see
**08:10 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1773846602815409):** Appreciate it
**08:10 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1773846635116429):** Might need to reboot the switch in the influent PLC panel
**08:10 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1773846640682989):** Mike knows how
**08:11 [Kevin](https://slack.com/archives/C08G4KZG7D5/p1773846681764159):** Does the network monitor say what is failing?
**08:17 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773847049642279):** it looks like they are all ping down notifications
**08:18 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773847092391379):** 192.168.1.230, 10.10.10.142
**08:18 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773847100439479):** actually all of these alerts might be from these two IPs
**08:18 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773847105129109):** i can take a look today if you want
**08:18 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773847131688699):** but since we have so many it must be something going up and down
**10:41 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773855674447919):** thats weird
**10:41 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773855679689409):** those IPs are the EWS server
**12:10 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773861045561509):** after an EWS restart, and monitoring software update, the notifications have settled down.
**12:10 [Mason Radke](https://slack.com/archives/C08G4KZG7D5/p1773861050815839):** will continue to monitor