Know your site is broken before your customers do.
Tickline checks your sites from more than one location, reads the page that comes back, and alerts you the moment something breaks, even when the server still answers “200 OK”.
Free plan: 2 monitors, no card needed.
Other monitors see “200 OK”. Tickline reads the page.
A broken site often still answers with a success code, so a monitor that only checks the status stays green. Tickline looks at what the page says and how it is built, and names the cause.
-
What your visitors see“There has been a critical error on this website.”WordPressStatus code200 OKTickline saysDownWordPress critical error
-
What your visitors see“Error establishing a database connection”WordPressStatus code200 OKTickline saysDownWordPress database error
-
What your visitors see“Fatal error: Allowed memory size … exhausted”PHPStatus code200 OKTickline saysDownPHP memory exhausted
-
What your visitors see“Application error: a client-side exception has occurred”Next.jsStatus code200 OKTickline saysDownNext.js client-side exception
-
What your visitors seeA Node.js stack trace printed in the pageNode.jsStatus code200 OKTickline saysDownNode stack trace exposed
-
What your visitors see“This account has been suspended”HostingStatus code200 OKTickline saysDownHosting account suspended
-
What your visitors seeA white screen, or a page that stops halfwayAny siteStatus code200 OKTickline saysDegradedResponse much smaller than usual (blank or partial page)
-
What your visitors seeA quiet redirect to someone else’s domainAny siteStatus code200 OKTickline saysDownRedirected to a different domain
-
What your visitors seeCloudflare’s “Web server is down” pageCloudflareStatus code521Tickline saysDownCloudflare origin error (52x)
Blank, partial and redirected pages are compared with what the page normally looks like, which Tickline learns from its recent successful checks.
How it works
Paste your URL
No agent to install and no code to add. A URL is enough to start.
Tickline learns the site
It opens the page, detects how it is built (WordPress, WooCommerce, Next.js, Node.js, PHP, Cloudflare) and suggests what to watch for. You confirm.
Get told what broke
The alert names the cause, then a second message tells you when it recovered.
DOWN: blog.example.com · (WordPress critical error) · last: 412 ms
RECOVERED: blog.example.com · for 8m 0s
Everything you need to hear about a problem first
Detection, alerts and a public status page, without stitching three tools together.
Detection
- Checks from more than one location. A monitor goes down only when a second location confirms the failure, so one bad network route does not wake you up.
- Full timing for every HTTP check: DNS, connect, TLS, time to first byte and download.
- SSL certificate and domain expiry warnings.
- DNS checks, and keyword checks that a page still contains what it should.
- TCP port checks. Pro
- Heartbeat monitors for cron jobs and backups that should report in.
WordPress, and any PHP site
The free WordPress plugin reports health and catches fatal errors on any page, even pages you do not monitor.
- Health: database, WP-Cron and pending plugin updates.
- PHP fatal errors reported from any page, as they happen.
- Keeps reporting even when WordPress recovery mode turns the broken plugin off.
- Not on WordPress? A small PHP reporter does the same for any PHP site.
{
"ok": true,
"db_ok": true,
"db_query_ms": 3,
"wp_cron_overdue_count": 0,
"pending_plugin_updates": 2,
"fatal_count_last_5m": 0
}Alerts
- Email on every plan.
- Telegram, Slack, Discord and signed webhooks. Pro
- Each alert says what broke and why.
- One message per problem, then one when it recovers. No flood.
- Maintenance windows, one-off or recurring, keep planned work quiet.
Status pages Pro
- A public status page, on your own domain if you like.
- Visitors subscribe by email or Telegram.
- Post incident updates as you work on a fix.
Also
- An uptime badge to embed in a README or a footer.
- A weekly summary email.
- SLA reports as CSV and PDF.
- A private probe that you run on your own server. Pro
Pricing
Start on the free plan. Pro is for more sites and faster checks.
Free
$0No card needed
- 2 monitors
- Checks every 5 minutes
- Email alerts
- HTTP, JSON API, SSL, domain, DNS and heartbeat monitors
- 30 days of history
- No status pages
Pro
Coming soonNot on sale yet
- 20 monitors
- Checks every minute
- Every alert channel and every monitor type
- 3 status pages
- 1 year of history
- 2 private probes
Questions
Do I need a card?
No. You sign up with an email address, and the free plan has no payment step.
How is a site confirmed down?
Every check runs from more than one location. Tickline marks a monitor down only when at least two locations see the failure, so a problem on one network path does not trigger an alert.
Recovery works the same way: the monitor must pass again before you get the all-clear.
Does it work with sites behind Cloudflare?
Yes. Checks reach your site through Cloudflare, like a visitor. When Cloudflare shows one of its own error pages because your server is down, Tickline reports that as down and names the cause.
If Cloudflare’s firewall starts challenging the checks, Tickline reports the challenge page instead of calling the site up, so you can allow the checks with a firewall rule.
Do I need the WordPress plugin?
No. Tickline watches any site by its URL, and recognises WordPress error pages without the plugin. The plugin adds deeper checks: database, WP-Cron, plugin updates and PHP fatal errors on pages you do not monitor.
What happens to my data if I delete my account?
You can download your data as a JSON file in Settings first. Deleting the account stops every monitor at once and removes your monitors, their history, incidents, alert channels and status pages.
The short-term log of individual checks is no longer linked to anyone and expires a few days later.
Where are the checks run from?
From Tickline’s own probe servers, which are separate from your hosting. On Pro you can also run a private probe on a server of your own and have your monitors checked from there too.