Uptime monitoring · Incidents · Status pages
Only real outages wake you up.
StatusTick checks your websites, APIs and cron jobs from several regions, confirms a failure before it alerts you, and keeps incidents and status pages in the same place.
Launching Q1 2027 · closed beta before then
| Monitor | Status | Response | 30 days |
|---|---|---|---|
Checkout API https://api.shop.example/health | Up | 212 ms | 99.97% |
Marketing site https://shop.example | Blocked | — | 99.99% |
Nightly backup Heartbeat · every 24 h | Up | — | 100.00% |
Search API https://search.shop.example | Degraded | 1,204 ms | 99.81% |
What it checks
- HTTP(S)
- TCP
- Ping
- DNS
- Heartbeats
- SSL expiry
- Domain expiry
- Playwright
- Private agents
- Third-party APIs
False alarms
Confirmed before anyone is paged.
A network blip, a firewall challenge or a short deploy should not wake anyone. StatusTick checks from several regions and confirms a failure before it alerts.
- A monitor is down only when two regions agree
- Choose how many failed checks in a row open an incident
- Blocked, Degraded and Maintenance are not Down
- 1EU West failed once. Re-checked at once: OK. No incident, no alert.
- 2Confirmed from 3 regions and 2 checks in a row. Incident opened, one alert sent.
403 from a bot challenge
Blocked. You get allowlist steps, not a page.
2.4 s answer, limit 1 s
Degraded. Slow, but not down.
Deploy window 02:00–02:30
Maintenance. No incident.
Playwright checks
Your Playwright tests, now watching production.
A 200 on the home page does not mean people can pay. Paste the Playwright tests you already have, and StatusTick runs them in real Chromium on a schedule, from several regions.
- Log in, search, check out: whole journeys, step by step
- Screenshot and full trace of every failure
- Web Vitals for every run, so slowdowns show early
1import { test, expect } from '@playwright/test';23test('customer can check out', async ({ page }) => {4 await page.goto('https://shop.example');5 await page.getByRole('button', { name: 'Add to cart' }).click();6 await page.getByLabel('Card number').fill(process.env.TEST_CARD);7 await page.getByRole('button', { name: 'Pay' }).click();8 await expect(page.getByText('Thank you')).toBeVisible();9});
- 1. Open shop.example640 ms
- 2. Add to cart310 ms
- 3. Fill card number220 ms
- 4. Pay → expect "Thank you"timeout 5.0 s
Private agents
Monitor services that are not on the internet.
Run a small agent inside your network to watch internal APIs, databases and intranets. It connects out over HTTPS, and only results leave your network.
- One Docker command; Kubernetes and Raspberry Pi too
- No inbound ports, VPN or firewall changes
- Agent down shows Offline, never a false outage
Your network · 10.0.0.0/8
Only results arrive: status, timings, status codes, short errors.
- Incidents
- Alerts
- Status pages
Third-party monitoring
See when a vendor is the cause.
Follow the APIs your app depends on, such as payments, cloud and AI providers. StatusTick checks them from several regions, reads their status pages, and shows a vendor problem on your own incident.
Follow your vendors →- Payments provider · APIElevated API errors · since 14:02 UTCIncident
- Cloud provider · eu-westAPI p95 88 ms from 3 regionsOperational
- AI model API · ChatAPI p95 410 ms from 3 regionsOperational
- SMS provider · MessagingAPI p95 120 ms from 3 regionsOperational
Possible vendor cause
Your payments provider reports elevated API errors since 14:02 UTC.
Status pages
A status page that keeps itself current.
Components follow your monitors and show 90 days of uptime. StatusTick drafts each incident post for you to review and publish, on your own domain, with email subscribers.
Explore status pages →- WebsiteOperational
- CheckoutDegraded
- DashboardOperational
- Payments provider (third-party)Incident
Some card payments fail
- Identified: our payments provider has elevated errors. Orders retry automatically.14:12 UTC · drafted by StatusTick
- Investigating: some card payments fail at checkout.14:06 UTC
Alerts
Alerts that say what broke.
Every alert names the monitor, the failing regions, the error and the start time, with one link to acknowledge. If nobody reacts, StatusTick escalates to a second set of channels. Failed deliveries are retried and logged.
- Slack
- Microsoft Teams
- Discord
- Telegram
- PagerDuty
- Webhooks
Down from EU West and US East since 14:05 UTC.
GET https://api.shop.example/health → 503 Service Unavailable
When does StatusTick launch?
StatusTick launches in Q1 2027. Before that, we run a free closed beta with a small group of teams. Join the beta list on the home page to get an invite.
How much does StatusTick cost?
The closed beta is free, and there is a free plan after launch. Paid plans and prices are published before launch. Nothing is charged unless you choose a paid plan.
What can StatusTick monitor?
HTTP(S) endpoints with status, header and keyword checks, TCP ports, ping, DNS records, cron jobs and backups with heartbeat monitors, SSL certificates, domain expiry and the assets of a page. IPv4 and IPv6 can be checked separately.
My firewall or Cloudflare blocks the checks. What happens?
StatusTick shows the monitor as Blocked, not Down, sends you one notice with steps to allow our checks, and does not open an incident by default. You can allow our published IP addresses or add a custom header.
How long do you keep check data?
Every check result is kept for 14 days. Hourly uptime and response-time history is kept for 13 months, so reports and status pages can show long periods. Alert delivery records are kept for 30 days.
Try StatusTick before launch.
The closed beta is free. Tell us what you monitor today, and help decide what gets built next.