Documentation menu
Documentation
Everything you need to set up monitors, alerts and status pages. New here? Start with Getting started.
Getting started
Create an account, add your first monitor, connect an alert channel and publish a status page in about five minutes.
HTTP(S) monitors
Check that a URL responds with an expected status code, with control over method, headers, body, timeout and redirects.
Keyword monitors
Alert when a page is missing expected text, or when an error message appears, even if the status code is 200.
SSL monitors
Get alerted before a TLS certificate expires, or as soon as it becomes untrusted.
Heartbeat monitors
Monitor cron jobs, backups and background workers by having them ping a unique URL. Get alerted when a ping is late.
Alerts
Send down and recovery alerts to email, Slack, Discord, Telegram or a signed webhook. Includes webhook payload and signature verification.
Status pages
Publish a public status page with live monitor status, 90-day uptime bars and incident history.
Custom domains
Serve your status page from your own domain, such as status.example.com, with automatic TLS. Available on Pro and Team.
Status badges
Embed a live SVG badge showing current status or 90-day uptime in your README, docs or website.
False-alarm protection
How Asniher verifies a failure with a delayed re-check, a different DNS resolver and remote probes before it opens an incident.
Plans and billing
Plan limits, annual billing, taxes, upgrades, downgrades, cancellation and refunds.
FAQ
Short answers to common questions about checks, alerts, status pages, billing and data.
Security and privacy
Where your data is stored, which providers process it, how long it is kept and how requests are signed.
Can't find what you need? Email support@asniher.com.