Connections and traffic. Visible down to each device.
Find ingress, egress and relay nodes in the team topology and check their running versions and service health. For each individual terminal profile, you can check connection status, upload and download traffic, and usage logs.
View operational informationFollow the connection to find the specific node.
Connection topology, with node relationships preserved.
View the Gateway, the final Connector, and two-hop relays to see which nodes each Relay uses. Open a node or connection detail to view the corresponding service information.
Node health, shown layer by layer.
Public TCP/SSH active probes, Agent heartbeats, and data plane services each display their results and timestamps. Node resource reporting provides CPU, memory, and storage usage.
Versions and policies, as actually applied.
Nodes show the currently running and target firmware versions; the node routing release page displays application status and receipts, distinguishing the saved version from the configuration the node is currently using.
Each configuration, with its own connections and traffic.
Use the device name and configuration number to find a computer, router, or firewall. The terminal details show connection status, cumulative upload, download, and total traffic, and the Relay details also provide uplink and downlink rate charts.
Bandwidth charts show the average rate by sampling window; you can adjust the time range, zoom and pan, and view individual sampling points. Usage logs show the actual traffic increment in five-minute windows. The two are used respectively to observe speed changes and period-based usage.
Firmware that supports collection also provides terminal source and destination details. Records are generated after the sampling window completes; earlier history that was not collected cannot be recovered. These IP-layer observations are used for access analysis.
Destination access, viewed from the final egress.
When you need to know where access went, open the destination access audit for the final Connector to view domains, IPs, ports, protocols and connection counts by traffic or time, and you can also query archived dates. Cloud Pulse details provide the corresponding destination access records.
Learn about access audits →Frequently asked questions.
There were access records before — why is the device not connected now?
Access records describe the access that occurred during the selected period, while connection status comes from the corresponding reports. Use the access time, the latest heartbeat and the sampling time together to distinguish historical usage from the current status.
Does the bandwidth chart show the speed at each instant?
The chart shows the average rate over the sampling window, not an instantaneous value. The usage log, by contrast, shows the actual traffic increment within a five-minute window; when viewing, pay attention to the time range and the sampling window.
Can terminal access logs be used directly as a billing basis?
IP-layer access observability is used to analyse sources and destinations, not as a billing basis. Collection requires supported firmware and a completed window, and history that was never collected cannot be recovered. Plan and bill usage are viewed separately on the traffic metering page.