Checkpoints & agents

Website, Port, Ping, and UDP monitors run from a checkpoint — a vantage point that actually performs the check. There are two kinds.

Shared probe locations

CuliPulse runs public checkpoints in Singapore, Frankfurt, Montreal, and Sydney. Pick one or more when you create a monitor — no setup, no install. Watching from several at once also protects you from false alarms (see down-quorum).

Use shared locations for anything reachable from the public internet.

Your own agent

An agent is a small program you run on your own infrastructure so CuliPulse can check things that shared locations can’t reach — an internal API, a database behind a firewall, a service on your office LAN or inside your VPC.

• It only needs outbound HTTPS to CuliPulse — no inbound port to open, no VPN, no firewall changes.
• It appears in your Agents list and is selectable as a checkpoint on any monitor, right alongside the shared locations.
• An agent can run HTTP/TLS, TCP, Ping (ICMP), and UDP checks; you choose which when you enroll it. Certificate-expiry checks run on agents only.

See Installing an agent to set one up.

How many, how much

Private agents are unlimited on every plan — there’s no cap on how many you run, and no per-agent throughput limit by default. Run one per network you need to reach.

Managing agents

From the Agents list you can see an agent’s version and whether it’s up to date, watch its check rate, and revoke it. You can also regenerate its token — the old token stops working immediately, so use this if a token may have leaked (then restart the agent with the new one).

When an agent goes offline

If an agent stops checking in for about 10 minutes, CuliPulse marks it offline and sends an agent.offline alert (and agent.online when it returns) to your notification destinations, noting how many monitors it affects. Monitors that relied only on that agent become unknown rather than falsely down.