Know what is down, slow or just blocked.
Websites, APIs, servers, DNS, certificates and cron jobs, checked as often as every 30 seconds. A slow answer shows as Degraded and a firewall as Blocked, so only a real outage pages you.
24 hours agonow
UpDegraded: slower than your thresholdBlocked: a firewall answeredMaintenanceDown
| 14:05:38 | 503 | 212 ms | Down |
| 14:05:08 | 503 | 198 ms | Checking again |
| 14:04:38 | 200 | 341 ms | Up |
| 14:04:08 | 200 | 4,210 ms | Degraded |
| 14:03:38 | 403 · challenge page | 88 ms | Blocked |
What you can monitor.
Websites and APIs
Any method, headers and body. Check status codes, response headers and text that must or must not appear.
Servers and ports
Databases, mail servers or any service that listens on a port, with TCP and ping.
DNS records
A, AAAA, CNAME, MX, TXT, NS and SOA records, with an optional expected value.
Cron jobs and backups
Your job calls a secret URL; StatusTick alerts when the call is late.
SSL and domains
Alerts before a certificate or domain expires, and at once when a certificate is invalid.
Page assets
Up to 30 images, scripts and stylesheets on a page, because a 200 can still be a broken page.
Playwright checks
A real Chromium browser runs your sign-in or checkout, with a screenshot and trace when a step fails.
How checks run.
Every failed check is read before anyone is paged. Here is what each answer means.
Every 30 seconds to 24 hours
Per monitor. Run a check now when you need an answer at once.
Failures in a row
Open an incident after 1 to 10 failed checks, and resolve it after the good checks you choose.
Slow is Degraded, not down
Set a response-time threshold per monitor, with its own alert rules.
Blocked is not down
When a firewall or bot protection answers instead of your site, the monitor shows Blocked.
Inside your network too
A private agent checks internal services and databases from inside your own network.
| What your server said | What it means for you | What happens |
|---|---|---|
| HTTP 503 · 2 checks in a row | Checkout is down for your customers. | Incident opened, on-call paged |
| HTTP 503 · then 200 | A restart, probably a deploy. Already back. | Noted on the timeline |
| HTTP 403 · bot challenge page | Your firewall is blocking our check, not your users. | One notice with the steps to allow us |
| HTTP 200 · 4,210 ms | Up, but slow enough that people notice. | Shown as Degraded |
| Any answer · maintenance window | Your planned work, doing what you planned. | Stays quiet |
| HTTP 503 · Stripe reports an incident | Down, and the cause is upstream. | Paged, with Stripe’s incident attached |
History and reports.
Every result for 14 days
And hourly uptime and response-time history for 13 months.
Uptime and response times
Uptime, average, p95 and p99 response time for any period up to 13 months.
Monthly uptime report
A summary per organization by email, for your team or your clients.
Questions.
- How often does StatusTick check?
- You choose per monitor, from every 30 seconds to every 24 hours.
- Can it monitor internal services?
- Yes. Run a private agent inside your network. It connects out on port 443, and nothing connects in.
- What does it cost?
- Nothing while in beta. Pricing comes with launch.
See it on your own product.
Point it at your product tonight. In the morning you’ll see what happened while you slept, and which of it needed you.