We ping your websites, APIs, certificates and cron jobs around the clock and tell you first when one stops answering, by email, Slack, Discord or Telegram.
Asniher: know it's down before your customers do. Uptime monitoring and status pages.
01Stats & facts
Uptime monitoring you can actually trust.
Every failure is re-checked through a second resolver and confirmed from another region before anyone gets paged. Real outages reach you in about 30 seconds. Blips never do.
- fastest check interval
- 30 sfastest check interval
- alerts per incident: down and recovered
- 2alerts per incident: down and recovered
- of uptime history on every status page
- 90 daysof uptime history on every status page
- hosted in Germany
- EUhosted in Germany
02What we watch
Everything you need to know about uptime, nothing you don't.
Four monitor types
HTTP(S) status codes, keyword present or absent, SSL certificate expiry and heartbeats. Custom methods, headers, bodies, timeouts and expected status ranges.
Read the docs about four monitor typesFalse-alarm protection
Every failure is re-checked after 30 seconds through a different DNS resolver, then confirmed by remote probes in other regions before an incident opens.
Read the docs about false-alarm protectionAlerts where your team works
Email, Slack, Discord, Telegram and HMAC-signed webhooks. One alert when it breaks, one when it recovers. No alert storms.
Read the docs about alerts where your team worksPublic status pages
Live status, 90-day uptime bars and incident history at your-name.status.asniher.com, or on your own domain with automatic TLS.
Read the docs about public status pagesEmbeddable status badge
An SVG badge for your README, docs or footer showing live status or 90-day uptime. Per page or per monitor.
Read the docs about embeddable status badgeHeartbeat monitoring for cron jobs
Backups, queues and scheduled jobs ping a unique URL. If a ping is late, you hear about it before the missing data does.
Read the docs about heartbeat monitoring for cron jobs
03Fewer false alarms
A failed request is a signal. A verified failure is an incident.
Flaky DNS, a dropped packet or a 2-second deploy blip should not wake anyone at 3 a.m. Asniher re-checks through a second resolver and asks probes in other regions before it opens an incident.
09:12:00
Check fails
503 from api.example.com, checked from Germany
09:12:30
Re-check
Different DNS resolver, still 503
09:12:34
Remote confirmation
Probe in another region sees the same failure
09:12:35
Incident opened
Slack and email alerted, status page updated
Step 1
Add a monitor
Paste a URL or create a heartbeat for a cron job. Check URLs every 30 seconds to 60 minutes, or give a heartbeat a period of up to 30 days or a cron schedule. The first check runs within one interval.
Step 2
Connect alerts
Your account email is ready by default. Add Slack, Discord, Telegram or a webhook in a few clicks and send a test notification.
Step 3
Publish a status page
Choose a slug and the monitors to show. Your customers see live status and history; your support queue sees fewer “is it down?” tickets.
04Status pages
A public status page that updates itself.
Live status, 90-day uptime bars and incident history at your-name.status.asniher.com, or on your own domain with automatic TLS.
Acme status
acme.status.asniher.com
- WebsiteHTTPS99.991%Up
- APIKeyword99.971%Up
- CheckoutHTTPS99.997%Up
- Nightly backupHeartbeat99.952%Up
05Pricing
Simple plans that scale with you.
Start free. Upgrade when you need faster checks, more monitors or a custom domain. Annual billing gets two months free.
Free
$0 /month
For side projectsFree forever, no card required
- 5 uptime monitors
- 20 cron job heartbeats
- Checks every 5 minutes
- 1 status page
ProMost popular
$2.99 /month
For production appsor $29.90 per year, billed annually
- 50 uptime monitors
- 100 cron job heartbeats
- Checks every 1 minute
- 3 status pages
Team
$9.99 /month
For teams on callor $99.90 per year, billed annually
- 200 uptime monitors
- 500 cron job heartbeats
- Checks every 30 seconds
- Unlimited status pages
06FAQ
Questions teams ask before switching.
Is the free plan really free?
How do you avoid false alarms?
Where is my data stored?
Can I use my own domain for the status page?
What happens if I downgrade?
Can I monitor cron jobs and internal services?
Start monitoring in under five minutes
Free plan includes 5 monitors, 20 cron job heartbeats, 5-minute checks and a public status page. No card required.