diff --git a/self-host/ha.mdx b/self-host/ha.mdx
deleted file mode 100644
index dd6764b..0000000
--- a/self-host/ha.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: "Highly Available Nodes"
-description: "How Pangolin can be deployed in a cluster for high availability"
----
-
-Pangolin's nodes are an ability to put strategically located servers around the world that serve as entry points for user traffic to your applications. They form the foundation of Pangolin's distributed architecture, providing high availability and optimal performance.
-
-## How Nodes Work
-
-
-
- Request is routed to the closest available node. If one goes down, there is always another node available.
-
-
-
- User identity is verified at the node before getting routed to your backend.
-
-
-
- Pangolin selects the optimal tunnel route to your backend service. Site tunnel clients (Newt) connect to the optimal node.
-
-
-
- If the primary tunnel fails, traffic automatically switches to an alternative route.
-
-
-
-## Advantages of Nodes
-
-
-
- Users connect to the geographically closest node.
-
-
-
- Automatic selection of the best available tunnel to route to your backend services.
-
-
-
- Provide ingress to thin-clients on private networks via tunnels.
-
-
-
- Each node continuously monitors its health and connectivity to your backend.
-
-
-
-
-
- Multiple nodes ensure your applications remain accessible during regional outages.
-
-
-
- No single point of failure - if one location goes down, there is always a way back to your application.
-
-