How do I see whether my scan agent is online?

Steps

The table has four parts: Name, Status, Last seen and an actions column.

STEPS

What each status means

The three states are simple.

Good to know

An online agent also raises your concurrent scan limit, since it brings its own capacity. An offline one does not help.

Offline usually means the container stopped, the host lost power, or outbound HTTPS is blocked. Start the container and refresh the tab. If it stays offline, check that the host can reach app.cyberlop.com on port 443.

The API shows live status too. GET /api/agents lists agents with their online or offline state, and needs the profile:read permission. That helps if you want to chart agent health yourself.

For the meaning of each state in more depth, see the status guide. To check timing, read when an agent last checked in. We are here on the contact page if the row never changes.

Check the tab before you schedule a big internal run, and again after any maintenance on the host. A pending row after a long wait usually means nobody has run the command yet, which is worth a quick message to whoever owns the machine. Add the check to your release routine, so that a dead agent never surprises a Friday release or a late-night scheduled run that nobody is awake to watch.

Keep screenshots out of tickets if they show the token. The status table does not hold it, but the Add agent screen does.

Related questions

• What do pending, online and offline mean for a scan agent?
• How do I see when my scan agent last checked in?
• What network access does a scan agent need?
• How do I add a self-hosted scan agent?
• Does adding a scan agent let me run more scans at once?

Full tutorial

Cyberlop self-hosted scan agents: scan private apps from inside your network

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre