Skip to content

Commit 77df825

Browse files
committed
fix(S2Svpn): statuses
1 parent bcefd6e commit 77df825

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

pages/site-to-site-vpn/reference-content/statuses.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,6 @@ This section explains the different statuses possible for a connection, and how
4444
| **Status** | **Description** |
4545
|------------------------|-----------------------------------------|
4646
| **Active** | The connection has been created, and the BGP session(s) between the two gateways are both up. Traffic can flow through the connection's tunnel(s). |
47-
| **Limited connectivity** | The connection has been created, but IP connectivity is limited. This may be the case if the connection is configured to route both IPv4 and IPv6 traffic, but only one of the two associated BGP sessions is up. |
47+
| **Limited connectivity** | The connection has been created, but IP connectivity is limited. This may be the case if the connection has both an IPv4 and an IPv6 routing policy attached, but only one of the two associated BGP sessions is up.|
4848
| **Down** | The connection has been created, but either a) the customer gateway device is not yet successfully configured and the tunnel(s) cannot be established, or b) no BGP sessions (neither IPv4 not IPv6) are up, and without route announcements no traffic can flow through the tunnel.|
4949
| **Locked** | The connection has been locked by the Trust and Safety team. You cannot carry out any actions on the connection. Open a support ticket. |

0 commit comments

Comments
 (0)