Docs
StatusTick documentation
How StatusTick works and how to set it up: monitors, alerts, private agents and more.
Get started
- How StatusTick worksThe core ideas in StatusTick: monitors, regions, checks, incidents, alert channels and status pages, and how they connect.
- Set up with an AI agentCopy-paste prompts for Claude Code and Cursor that add monitoring to your app, through the StatusTick MCP server or a statustick.yml file synced by the CLI.
Monitors
- Monitor typesWhat StatusTick can check: HTTP(S), TCP, ping, DNS, browser checks, heartbeats, SSL certificates, domain expiry and page assets, with the settings for each.
- Heartbeat monitorsWatch cron jobs, backups and workers: your job calls a secret StatusTick URL, and StatusTick alerts when the call does not arrive in time.
- Playwright checksMonitor full user journeys with Playwright: write a script, run it in real Chromium on a schedule from several regions, and debug with screenshots and traces.
- Private agentsRun a StatusTick agent inside your network to monitor internal services: install, network requirements, what leaves your network, and the security model.
- Agent securityHow the StatusTick private agent is kept safe inside your network: what it does, what never leaves, and what stops misuse of StatusTick or of a stolen token.
Alerts
- Avoiding false alarmsThe settings that decide when StatusTick opens an incident: confirmation from several regions, failures in a row, degraded and blocked states, maintenance.
- Alert channelsWhere StatusTick sends alerts: email, SMS, Slack, Microsoft Teams, Discord, Telegram, PagerDuty and webhooks, and how delivery, retries and acknowledging work.
- Alerts from other toolsOpen StatusTick incidents from alerts your other tools send: one webhook URL per source, for generic JSON, Alertmanager, Grafana, Datadog, Sentry or CloudWatch.
Reference
Status pages
API reference: a REST API with organization API keys, documented with OpenAPI, is available in your dashboard.