diff --git a/release/models/network-instance/openconfig-network-instance-types.yang b/release/models/network-instance/openconfig-network-instance-types.yang
index ea4d1a2a5..0236f672f 100644
--- a/release/models/network-instance/openconfig-network-instance-types.yang
+++ b/release/models/network-instance/openconfig-network-instance-types.yang
@@ -19,7 +19,13 @@ module openconfig-network-instance-types {
   description
     "Types associated with a network instance";
 
-  oc-ext:openconfig-version "0.9.3";
+  oc-ext:openconfig-version "0.10.0";
+
+  revision "2026-08-04" {
+    description
+      "Add connection point operational status.";
+    reference "0.10.0";
+  }
 
   revision "2021-07-14" {
     description
@@ -196,6 +202,63 @@ module openconfig-network-instance-types {
       endpoint";
   }
 
+  identity CONNECTION_POINT_OPER_STATUS {
+    description
+      "Base identity for the operational status of a connection point.";
+  }
+
+  identity ADMIN_DOWN {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "The connection point is administratively down.";
+  }
+
+  identity CONFIG_CONFLICT {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "The connection point is down due to a configuration conflict.
+      Examples are: - Multiple endpoints configured with the same local
+      MPLS label. - A static endpoint configured with both a tunnel interface
+      and a nexthop-group transport.";
+  }
+
+  identity DOWN {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "The connection point is operationally down due to a forwarding plane
+      or transport failure. This is distinct from ADMIN_DOWN, UNPROGRAMMED
+      and CONFIG_CONFLICT. Typical causes include a failed transport tunnel,
+      loss of the remote signaling session, or the local interface being down.";
+  }
+
+  identity UNPROGRAMMED {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "The connection point configuration has been resolved and validated,
+      but the hardware programming has not completed or has failed.";
+  }
+
+  identity UP {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "The connection point is fully operational.";
+  }
+
+  identity PARTIALLY_UP {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "At least one endpoint is up and programmed while at least one other
+      endpoint is not fully up or programmed.";
+  }
+
+  identity STANDBY {
+    base CONNECTION_POINT_OPER_STATUS;
+    description
+      "The connection point is configured as a backup and is not actively forwarding
+      traffic. It will transition to UP upon failure of the primary
+      connection point.";
+  }
+
   identity LABEL_ALLOCATION_MODE {
     description
       "Base identity to be used to express types of label allocation
diff --git a/release/models/network-instance/openconfig-network-instance.yang b/release/models/network-instance/openconfig-network-instance.yang
index 2ecd63c64..1eb8abc81 100644
--- a/release/models/network-instance/openconfig-network-instance.yang
+++ b/release/models/network-instance/openconfig-network-instance.yang
@@ -50,7 +50,13 @@ module openconfig-network-instance {
     virtual switch instance (VSI). Mixed Layer 2 and Layer 3
     instances are also supported.";
 
-  oc-ext:openconfig-version "4.7.0";
+  oc-ext:openconfig-version "4.8.0";
+
+  revision "2026-08-04" {
+    description
+      "Add connection point operational status.";
+    reference "4.8.0";
+  }
 
   revision "2026-03-17" {
     description
@@ -1146,6 +1152,14 @@ module openconfig-network-instance {
     description
       "Operational state data relating to a forwarding-instance
       connection point";
+
+    leaf oper-status {
+      type identityref {
+        base oc-ni-types:CONNECTION_POINT_OPER_STATUS;
+      }
+      description
+        "Operational status of the connection point.";
+    }
   }
 
   grouping table-config {