Introducing StatusTick: Uptime Monitoring That Only Wakes You for Real Outages

StatusTick is uptime monitoring, incident handling and status pages in one tool, for small teams whose users notice when things break. It launches in Q1 2027. This post explains why we are building it and what it does.

The problem: alerts you cannot trust

The most common complaint about uptime monitors is false alarms. A check fails once because of a network blip between one monitoring server and the site. A firewall or bot protection blocks the monitor while real users are fine. A deploy takes the site down for 20 seconds. Each of these can page someone in the middle of the night.

After a few false alarms, people start to ignore alerts. Then a real outage gets missed.

What StatusTick does

StatusTick is built around one promise: only real outages wake you up.

• Confirmation from more than one region. StatusTick checks from several regions at the same time. By default, a monitor is only marked down when at least two regions fail, and a single failing region is re-checked at once.
• Failures in a row. You choose how many failed checks in a row open an incident (1 to 10), and how many good checks close it.
• Blocked is not down. When a firewall or bot protection answers instead of your site, StatusTick shows Blocked, tells you how to allow our checks, and does not page you by default.
• Slow is not down. Set a response-time threshold, and slow responses show as Degraded instead of Down.
• Maintenance windows. Planned work, one-off or repeating, does not open incidents.

It checks websites and APIs over HTTP(S), TCP ports, ping and DNS, as often as every 30 seconds. It also watches cron jobs with heartbeat monitors, SSL certificates, domain expiry and the images, scripts and styles on a page.

Alerts go to email, Slack, Microsoft Teams, Discord, Telegram, PagerDuty or your own webhook. Failed deliveries are retried, and each alert has a link to acknowledge the incident. If nobody acknowledges it, StatusTick alerts a second set of channels.

More than public checks

• Status pages that update themselves. Components follow your monitors, and StatusTick drafts each incident post for you. Use your own domain and let users subscribe by email.
• Private agents. Run a small agent inside your network to check internal APIs, databases and intranets. It only connects out, and only results leave your network.
• Third-party monitoring. Follow the official status of OpenAI, Stripe and GitHub, and see their outages next to yours.
• An MCP server, so you can add and check monitors from Claude, Cursor or ChatGPT.

When and how

StatusTick launches in Q1 2027. Before that, we run a free closed beta with a small group of teams. Join the beta and tell us what you monitor today.