# StatusTick

> StatusTick checks your websites, APIs and cron jobs from several regions, confirms a failure before it alerts you, and keeps your users informed with a status page. Launching Q1 2027; a free closed beta runs before launch, and there is a free plan after launch.

Products (each works on its own and together):
- [Monitor](https://statustick.com/features/uptime-monitoring): Know when your site, API or scheduled job stops working.
- [Status](https://statustick.com/features/status-pages): Tell your customers what is working, on your own status page.
- [Incidents](https://statustick.com/features/incidents): Get the right person on an incident, with alerts and escalation.
- [Vendors](https://statustick.com/features/third-party-monitoring): See when the services you depend on have problems.

Key facts:
- Monitor types: HTTP(S), TCP, ping, DNS, heartbeat (cron), SSL certificate expiry, domain expiry, page assets, IPv4/IPv6.
- Intervals from 30 seconds to 24 hours; checks run from several regions in parallel.
- Browser checks: Playwright scripts in real Chromium, with screenshots, traces and Core Web Vitals.
- False-alarm controls: confirmation from 2+ regions, N failed checks in a row, Blocked (firewall) and Degraded (slow) states, maintenance windows.
- Alert channels: email, SMS, Slack, Microsoft Teams, Discord, Telegram, PagerDuty, webhooks.
- Status pages with custom domains, email subscribers and incident posts drafted from incidents.
- Private agents: monitor internal services from inside your network (outbound HTTPS only, results only).
- Third-party monitoring: follow the official status of OpenAI, Stripe and GitHub.
- Pricing: free during the closed beta; free plan after launch; paid plans published before launch.
- For AI agents: an MCP server at https://mcp.statustick.com (OAuth sign-in or an API key), a REST API documented with OpenAPI at https://api.statustick.com/docs, and monitors as code in a statustick.yml file synced with the statustick CLI.

## Features
- [Uptime monitoring for websites, APIs and cron jobs](https://statustick.com/features/uptime-monitoring): HTTP(S), TCP, ping, DNS, heartbeats, SSL and domain expiry, every 30 seconds from several regions.
- [Your Playwright tests, now watching production](https://statustick.com/features/browser-checks): Playwright scripts in real Chromium: logins, sign-ups and checkouts, with screenshots and traces.
- [Alerts that only fire for real outages](https://statustick.com/features/alerts): Confirmation from more than one region, failures in a row, blocked and degraded states, and seven channels.
- [Incident management without another tool](https://statustick.com/features/incidents): Incidents open and resolve from monitors, with acknowledge, assign, severity, comments and escalation.
- [Status pages that update from your monitors](https://statustick.com/features/status-pages): Live component status, 90-day uptime, drafted incident posts, custom domains and subscribers.
- [Monitor what is not on the internet](https://statustick.com/features/private-agents): An agent inside your network for internal services. Outbound-only, results-only.
- [Is it us, or is it them?](https://statustick.com/features/third-party-monitoring): Follow OpenAI, Stripe and GitHub; see vendor outages next to your own.

## Check types
- [Cron job and heartbeat monitoring](https://statustick.com/monitoring/cron-job-monitoring): Know when a cron job, backup or queue worker did not run. Your job pings a StatusTick URL when it finishes; a missing ping opens an incident.
- [SSL certificate and domain expiry monitoring](https://statustick.com/monitoring/ssl-certificate-monitoring): StatusTick reads your TLS certificate and your domain registration and alerts before either expires, and at once when a certificate is invalid.
- [API monitoring: methods, headers, bodies and keyword checks](https://statustick.com/monitoring/api-monitoring): Check that an API answers correctly, not only that it answers: method, headers and body, expected status codes, response text and response headers.
- [TCP port and ping monitoring](https://statustick.com/monitoring/tcp-and-ping-monitoring): Check that a database, mail server or game server accepts connections, and that a host answers ping, from several regions.
- [DNS record monitoring](https://statustick.com/monitoring/dns-monitoring): Resolve a record (A, AAAA, CNAME, MX, TXT, NS or SOA) from several regions and check that the answer is the one you expect.

## Docs
Every docs page is also Markdown at its URL with .md added. All docs in one file: https://statustick.com/llms-full.txt

- [How StatusTick works](https://statustick.com/docs/how-statustick-works.md): The core ideas in StatusTick: monitors, regions, checks, incidents, alert channels and status pages, and how they connect.
- [Set up with an AI agent](https://statustick.com/docs/set-up-with-an-ai-agent.md): Copy-paste prompts for Claude Code and Cursor that add monitoring to your app: through the StatusTick MCP server, or as a statustick.yml file you sync with the CLI.
- [Monitor types](https://statustick.com/docs/monitor-types.md): What StatusTick can check: HTTP(S), TCP, ping, DNS, browser checks, heartbeats, SSL certificates, domain expiry and page assets, with the settings for each.
- [Heartbeat monitors](https://statustick.com/docs/heartbeat-monitors.md): Watch cron jobs, backups and workers: your job calls a secret StatusTick URL, and StatusTick alerts when the call does not arrive in time.
- [Playwright checks](https://statustick.com/docs/browser-checks.md): Monitor full user journeys with Playwright: write a script, run it in real Chromium on a schedule from several regions, and debug failures with screenshots and traces.
- [Private agents](https://statustick.com/docs/private-agents.md): Run a StatusTick agent inside your network to monitor internal services: install, network requirements, what leaves your network, and the security model.
- [Agent security](https://statustick.com/docs/agent-security.md): How 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.
- [Avoiding false alarms](https://statustick.com/docs/avoiding-false-alarms.md): The settings that decide when StatusTick opens an incident: confirmation from several regions, failed checks in a row, degraded and blocked states, and maintenance windows.
- [Alert channels](https://statustick.com/docs/alert-channels.md): Where StatusTick sends incident alerts: email, SMS, Slack, Microsoft Teams, Discord, Telegram, PagerDuty and webhooks, and how delivery, retries and acknowledging work.
- [Alerts from other tools](https://statustick.com/docs/alerts-from-other-tools.md): Open StatusTick incidents from the alerts your other tools already send: a webhook URL per alert source that reads generic JSON or the webhook format of Prometheus Alertmanager, Grafana, Datadog, Sentry or AWS CloudWatch.
- [Allowlisting StatusTick](https://statustick.com/docs/allowlisting-statustick.md): How to let StatusTick checks through your firewall, WAF or bot protection, so blocked checks do not hide the real status of your site.
- [Status page feeds, badge and widget](https://statustick.com/docs/status-page-feeds-and-embeds.md): Show your status page's state in your app, docs or README: JSON, RSS and Atom feeds, an SVG badge and a one-line widget.

## Optional
- [FAQ](https://statustick.com/faq)
- [Pricing](https://statustick.com/pricing)
- [Introducing StatusTick: Uptime Monitoring That Only Wakes You for Real Outages](https://statustick.com/blog/introducing-statustick)
- [How to Set Up Uptime Alerts That People Don't Ignore](https://statustick.com/blog/smart-uptime-alerts)
- [How to Choose an Uptime Monitoring Tool: 12 Questions to Ask](https://statustick.com/blog/choosing-uptime-monitoring-tool)
- [Why Uptime Monitoring Matters: The Failures Your Users Find First](https://statustick.com/blog/why-uptime-monitoring-matters)
- [How to Work Out What Downtime Costs Your Business](https://statustick.com/blog/cost-of-downtime-2025)