From 316c3ce23ef93a08b779f3be55ba948b56c23c09 Mon Sep 17 00:00:00 2001
From: Ashley Mensah <ashleyamo982@gmail.com>
Date: Mon, 20 Apr 2026 15:46:28 +0200
Subject: [PATCH] Added mention of peer disconnection notification feature to
 networks docs

---
 src/pages/manage/networks/index.mdx                           | 4 ++++
 .../networks/use-cases/by-scenario/cloud-to-on-premise.mdx    | 2 +-
 .../networks/use-cases/by-scenario/remote-worker-access.mdx   | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/src/pages/manage/networks/index.mdx b/src/pages/manage/networks/index.mdx
index 604805fa..606cbef7 100644
--- a/src/pages/manage/networks/index.mdx
+++ b/src/pages/manage/networks/index.mdx
@@ -34,6 +34,10 @@ You can add multiple routing peers using individual peers or groups to ensure hi
     <img src="/docs-static/img/manage/networks/index/add-routing-peer-1.png" alt="high-level-dia" className="imagewrapper"/>
 </p>
 
+<Note>
+To get alerted when a routing peer goes offline, enable the **Routing Peer Disconnected** event in [Notifications](/manage/settings/notifications). You can receive alerts via email, webhook, or Slack.
+</Note>
+
 <Note>
 A network resource policy grants access to the network **behind** the routing peer, not to the routing peer machine itself. If you need to access services running on the routing peer (for example, Pi-hole, Home Assistant, or a monitoring dashboard), add the routing peer to a group and create a peer-to-peer [access control policy](/manage/access-control) with that group as the destination.
 </Note>
diff --git a/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx b/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
index 42cf55a6..d39bc3eb 100644
--- a/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
+++ b/src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
@@ -189,7 +189,7 @@ Your cloud application can now securely access the on-premise database.
 ### High Availability
 
 - Deploy multiple routing peers and configure failover
-- Monitor routing peer health with your existing tools
+- Monitor routing peer health with your existing tools or set up [Notifications](/manage/settings/notifications) to get alerted when a routing peer disconnects
 - Use cloud-native load balancing where appropriate
 
 ### Performance
diff --git a/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx b/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
index 4dc8bdfd..41794624 100644
--- a/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
+++ b/src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
@@ -160,7 +160,7 @@ Alternatively, create a setup key with "`remote-workers`" as an auto-assigned gr
 
 For critical connections, consider:
 - Multiple routing peers at each location
-- Monitoring routing peer health
+- Monitoring routing peer health via [Notifications](/manage/settings/notifications) to get alerted when a routing peer disconnects
 - Automatic failover configuration
 
 ### Security