Skip to content
Downtime alerts

When your site goes down,hear about it right away.

Chekaav checks your site and API from vantage points inside and outside Iran and tells you, on the channel you picked, as soon as it detects a problem — what broke, where it was seen from, and since when.

Free plan: 3 monitors and one vantage point · 14-day Pro trial

How it works

Three steps, with nothing installed on your server.

  1. You add an address

    A site, API, port, DNS record, SSL certificate or domain expiry. You choose the interval and the vantage points.

  2. We check from outside

    Every check runs from vantage points inside and outside Iran, recording the response, the timing and the failure reason.

  3. We alert on detection

    After several consecutive failed checks an incident opens and the alert goes out; when the service returns you get a resolved message.

Where you get told

A workspace can use several channels at once.

Email

The simplest start, for everyone on the team who needs to know.

Telegram and Bale

A message in a private chat or a team group, connected from the panel.

SMS

For outages that must not be missed. The recipient must be a verified number of a team member.

Slack and Mattermost

Posted to your team channel through an incoming webhook.

Webhook

The event sent to your own service, signed so you can verify it came from us.

On-call shifts

Besides the team channels, whoever is on call at that moment is told personally.

What the alert says

Enough to understand the situation without opening the panel.

What and what state

The monitor name, the kind of incident (outage, slowdown or approaching expiry) and the current state.

The failure reason

For example no response within the timeout, an unexpected status code, a DNS error or an SSL certificate problem.

Affected regions

Which vantage points could not reach the service, so you can tell a regional problem from a global one.

Time and duration

Times in Tehran time, and on the resolved message, how long the outage lasted.

Keeping the noise down

An alert that always rings stops being read.

Confirmation thresholds

An incident opens after several consecutive failures, and recovery must be confirmed by several successes, so a momentary blip does not page anyone.

Maintenance windows

For planned work, define a quiet window: checks keep running but alerts are held back.

Reminders when you want them

You can repeat the alert while an incident stays open; by default you get one outage alert and one resolved message.

Slowdowns kept separate

If the service is up but slow, a separate performance incident is raised instead of mixing it with an outage.

Things worth knowing

Detection speed follows your interval

A monitor checked every 5 minutes is seen within that window. Shorter intervals come with higher plans.

SMS has a monthly allowance

Each plan includes a number of sends; beyond that it is charged from your wallet. Email and messengers have a larger allowance.

Voice calls are not offered yet

We are working on it; for now SMS is the fastest channel for critical outages.

We watch from outside

Chekaav connects like a visitor would; it does not report your server's CPU or memory.

Get your first alert working in minutes

Create one monitor, connect a channel and send a test message so you know it works before you need it.

Create a free account