Skip to content

Endpoint

An Endpoint is a single address that belongs to a subnet on an Endpoint Manager. Control Center creates it when you add a subnet — you do not order Endpoint from Add Service.

Open an Endpoint from Services, or expand a subnet on Endpoint Manager and click the address. You see whether the host is active or blocked, and you can block traffic for that address alone.

flowchart LR
    A(Endpoint Manager) --> B(Add subnet)
    B --> C(Endpoint appears)
    C --> D(Status and blocking)

    style A fill:#34ebb1
    style B fill:#34ebb1
    style C fill:#34ebb1
    style D fill:#34ebb1

Overview and status

The overview puts operational status first. At the top you see one of:

  • Active — the saved state allows traffic.
  • Blocked — blocking is saved for this host.
  • Blocked (entire subnet) — blocking is saved for the parent subnet and includes this host.
  • Ended — the service is no longer active.

The overview then shows:

  • Core service details (name, tags, deployment status).
  • Endpoint inventory — IP address, the related Subnet, and the parent Endpoint manager.
  • Custom fields — values you set on this host. If the Endpoint Manager has no fields yet, the card explains that.

Banners appear when something still needs attention:

  • The entire subnet is blocked — individual Block / Unblock on this endpoint is unavailable until the subnet is unblocked. Use Open related subnet.
  • Blocking is saved on this endpoint. It takes effect after you configure blocking on the Endpoint Manager. Use Open endpoint manager.
  • The service has ended, so these details are no longer active.

Blocking

Click Actions, then Block or Unblock. Control Center asks Block traffic for this endpoint? (or the unblock equivalent) before it applies.

Blocking one host does not block the rest of the subnet. To block every address in a prefix, block the subnet on Endpoint Manager instead.

When the whole subnet is already blocked, Block and Unblock on the endpoint stay unavailable.

Changes to endpoint and subnet blocking are saved immediately. With batching enabled, network synchronization waits for the next five-minute batch and then runs asynchronously. An earlier synchronization still running or a failure can extend the delay; five minutes is not an enforcement guarantee. The displayed blocking state is the saved state, not confirmation that every gateway has applied it. Confirm activation and timing with your service contact.

Open Subnet in the sidebar to see the related subnet (CIDR and whether it is enabled).

Open Accounting for usage on this address. Choose a period, switch between chart and table, and download CSV or Excel — the same pattern as on Endpoint Manager.

When the parent subnet is deleted

Deleting the parent subnet ends its endpoints and removes them from live management. Existing accounting history is retained. Creating the same CIDR again creates new subnet and endpoint records; it does not reactivate the old endpoints or move their history.

Note

Applying Changes: Like other services in Control Center, some configuration is not active until you deploy pending changes. See Workflows and Applying Changes.