Enabling & Disabling Connections

Purpose

There are many situations where temporarily stopping traffic to a circuit is necessary without losing the configured access policies, IP rules, country blocks, and user allowlists. The backend service may be undergoing maintenance and users should not receive error pages. A vulnerability in the backend service may require immediate access termination during investigation. An issue may require isolation to determine whether traffic from Horizon is a contributing factor. In all of these scenarios, disabling the circuit is the appropriate approach - it instantly stops all traffic from reaching the backend while preserving every aspect of the circuit's configuration so that it can be re-enabled later with a single action.

How to Enable/Disable

To toggle a circuit's enabled state, use the Enabled switch in the connections table or in the circuit's settings panel. The change takes effect immediately - there is no delay or propagation period. When a circuit is disabled, its public domain stops serving traffic, and when it is re-enabled, traffic resumes with all previously configured policies and security rules intact. Disabled circuits retain their full configuration: access policies, IP blacklist and whitelist rules, country blocks, user allowlists, bot detection settings, and expiration dates are all preserved exactly as they were.

Behavior When Disabled

When a circuit is disabled, the public domain stops accepting and forwarding requests. Any user who attempts to access the domain will not reach the backend service. No new request log entries or access log entries are generated for the disabled circuit, since no traffic is being processed. The circuit remains visible in the connections table with a clear disabled status indicator, making it obvious that the circuit exists but is not currently active. Historical logs that were generated before the circuit was disabled remain accessible in the monitoring dashboard.