Website uptime monitoring that checks twice before it alerts
Asniher requests your website on a schedule, checks the status code and, if you want, the text on the page. A failed check is verified before anyone is paged, and the same checks feed a public status page your customers can follow.
What you get with website uptime monitoring
Status code and page content
An HTTP(S) monitor compares the status code with the range you expect. A keyword monitor also searches the page for text that must be there, such as “Add to cart”, or must not, such as “scheduled maintenance”, so an error page served with 200 OK still alerts.
Verified before you are alerted
A failed check is repeated after 30 seconds through a different DNS resolver. Where remote probes are available, other regions confirm the outage before an incident opens. A single dropped packet does not wake anyone up.
One alert down, one alert up
The down alert carries the reason, the recovery alert carries the downtime. Reminders while it stays down are optional. Email, Slack and Discord on every plan; Telegram and signed webhooks on Pro and Team.
Status page and badge included
Show the same monitors on a public status page with 90-day uptime bars and incident history, and embed a live SVG badge in your footer or README.
Set it up in a few minutes
Step 1
Create a free account
Sign up with an email magic link or GitHub. The Free plan needs no card.
Step 2
Add an HTTP(S) or keyword monitor
Enter your URL and pick an interval. Keep the default expected status of 200-299, or add a keyword for pages that can break while still returning 200.
Step 3
Connect an alert channel
Alerts go to your account email by default. Add Slack, Discord, Telegram or a webhook, then send a test notification to confirm it arrives.
Step 4
Publish a status page
Optional. Choose a slug, pick the monitors to show and share https://<slug>.status.asniher.com.
Limits by plan
Every plan includes false-alarm protection, incident history and the status badge. Annual billing gives two months free.
Free · $0/mo
- Uptime monitors (HTTP(S), keyword, SSL)
- 5
- Shortest check interval
- Every 5 minutes
- Status pages
- 1
- Alert channels
- Email, Slack, Discord
Pro · $2.99/mo
- Uptime monitors (HTTP(S), keyword, SSL)
- 50
- Shortest check interval
- Every 1 minute
- Status pages
- 3
- Alert channels
- Email, Slack, Discord, Telegram, Webhook
Team · $9.99/mo
- Uptime monitors (HTTP(S), keyword, SSL)
- 200
- Shortest check interval
- Every 30 seconds
- Status pages
- Unlimited
- Alert channels
- Email, Slack, Discord, Telegram, Webhook
| Limit | Free · $0/mo | Pro · $2.99/mo | Team · $9.99/mo |
|---|---|---|---|
| Uptime monitors (HTTP(S), keyword, SSL) | 5 | 50 | 200 |
| Shortest check interval | Every 5 minutes | Every 1 minute | Every 30 seconds |
| Status pages | 1 | 3 | Unlimited |
| Alert channels | Email, Slack, Discord | Email, Slack, Discord, Telegram, Webhook | Email, Slack, Discord, Telegram, Webhook |
Good to know
- Checks run from Germany. Remote probes in other regions confirm failures when they are available.
- Checks fetch the page without running a browser, so text added by client-side JavaScript is not visible to keyword monitors.
- Only public addresses can be checked. Private ranges such as 10.0.0.0/8, 192.168.0.0/16 and 127.0.0.1 are rejected; for internal services, use a heartbeat monitor and ping out from inside your network.
- Ping (ICMP), TCP port and DNS record monitors are not offered.
- Checks identify as AsniherBot/1.0. If bot protection blocks unknown clients, allow this user agent for the checked path.
Common questions
How often is my website checked?
Will a short blip wake me up?
Can I monitor a page behind a login?
Docs and free tools
Read the docs
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.