Skip to content
TunnelHQTunnelHQ Docs

TunnelHQ documentation

Open in ChatGPTOpen in Claude

TunnelHQ is uptime monitoring for VPN servers. Instead of pinging a port, it completes a real tunnel handshake across 11 protocols and tells you whether users can connect, from one location or many.

An open port doesn’t mean the tunnel works. Certificates expire, authentication breaks, an upstream route goes dark, or a region gets blocked, and a plain TCP check still reports “up”. TunnelHQ connects the way a real client does, so a passing check means people are getting through.

What you can do

Section titled “What you can do”

Most of this also works from the REST API and the MCP server. The CLI tests configs and manages API keys.

Quick startAdd your first monitor and run a live test in about five minutes.
Working with monitorsAdd a monitor, then tune its locations, interval, retries, and alerts.
VPN protocolsThe 11 supported protocols and the fields each check needs.
Import monitorsAdd many servers at once with AI-assisted paste or config file upload.
Locations and statusTest from several locations and see how aggregate status is calculated.
REST APIManage monitors, tests, and incidents over HTTP.
CLITest VPN configs and manage API keys from your terminal with thq.
MCP serverLet Claude, Cursor, or Windsurf run tests and work on incidents.
WebhooksReceive monitor.down and monitor.up events when status changes.
Uptime checksMonitor websites, keywords, hosts, TCP ports, DNS servers, and scheduled jobs.