Skip to content

Commit cb1179b

Browse files
notifications edit
1 parent bb49186 commit cb1179b

File tree

1 file changed

+1
-6
lines changed

1 file changed

+1
-6
lines changed

src/content/notifications/index.yaml

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -511,12 +511,7 @@ entries:
511511
nextSteps: Monitor tunnel health over time and consider deploying [`cloudflared` replicas or load balancers](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/).
512512
otherFilters: None.
513513
additional_information: |-
514-
| <div style="width:75px">Health status</div> | Description |
515-
| ------------- | ------------ |
516-
| Healthy | The tunnel is active and serving traffic through four connections to the Cloudflare global network. |
517-
| Degraded | The tunnel is active and serving traffic, but at least one individual connection has failed. Further degradation in [tunnel availability](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/) could risk the tunnel going down and failing to serve traffic.|
518-
| Down | The tunnel cannot serve traffic as it has no connections to the Cloudflare global network.|
519-
| Inactive | This value is reserved for tunnels which have been created, but have never been run.|
514+
Refer to [Tunnel status](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors/#tunnel-status) to review the list of possible tunnel statuses (`Active`, `Inactive`, `Down` and `Degraded`).
520515
521516
- name: Device connectivity anomaly
522517
audience: Zero Trust customers who want to be notified when Cloudflare detects a spike or drop in the number of devices connected to the WARP client.

0 commit comments

Comments
 (0)