Uptime Monitoring
Check your sites and servers, and get told when one goes down.
Jasper checks each monitor on a schedule from its own servers. When a check fails, Jasper opens an incident and alerts you in Jasper's notification bell, in Slack, at your own webhook and, if you tick it, by email. When the check passes again, the incident resolves and Jasper sends a recovery alert. Uptime monitoring is on team plans, with a 14-day trial.
Add a monitor
- Open the More menu and choose Uptime Monitoring.
- Click Add Monitor.
- Enter a Monitor Name and choose the Monitor Type (see below).
- Enter the URL or Hostname to check.
- Choose the Check Interval and the Timeout (seconds) (5 to 120, 30 by default).
- Set the Notification Threshold: how many failed checks in a row before Jasper alerts you (1 by default).
- Set up alerts (see Alerts).
- Leave Enable monitoring immediately ticked and click Create Monitor. The first check runs within about a minute.
Every member of your organisation can see monitors. Tick Private Monitor to keep a monitor out of other people's monitor list; its incidents and bell alerts are still visible to everyone in the organisation. You can't change a monitor's type after you create it. On a monitor's page, Test Check runs a check straight away, and Pause and Resume stop and restart its checks.
Check types that work today
| Monitor Type | What Jasper checks |
|---|---|
| HTTP/HTTPS | Sends a GET request to the URL and follows up to five redirects. A success or redirect status code counts as up. |
| Response Time | Loads the URL and times it. 2 seconds or more is degraded; 5 seconds or more is down. |
| Ping (ICMP) | Pings the hostname. |
| Domain Expiration | Looks up the domain's registration. From 30 days before it expires, the monitor shows as degraded. |
| DNS | Checks that the hostname has an A record. |
Checks run every 1, 5, 15 or 30 minutes. The 1-minute interval, and the domain, DNS and response-time types, depend on your organisation's uptime tier. SSL Certificate, Keyword and Port (TCP) monitors don't work yet: see the limits. The basic tier allows 10 monitors; the next tier allows 50.
Heartbeat monitors for cron jobs
A Heartbeat/Cron monitor waits for your job to check in. After you create one, its page shows a
Heartbeat URL: have the job send a POST to it each time it runs, for example
curl -X POST <Heartbeat URL>. No sign-in is needed, because the URL is the key, so keep it private.
The monitor is up while pings arrive, and goes down when none has come within its check interval.
Alerts
These alert settings on a monitor work today:
- Enable Email Notifications with Email Recipients. Email is off until you tick it. If you add no recipients, the person who created the monitor gets the email.
- Slack Webhook URL: paste a Slack incoming webhook to post alerts to a channel.
- Custom Webhook URL: Jasper sends each alert to this address as a JSON POST.
- Notification Threshold: the number of failed checks in a row before an alert.
Members who have this organisation selected also get an alert in the Jasper notification bell, subject to their own notification settings. The test buttons (Test Email, Test Slack and Test Webhook) are on the monitor's edit page. Test Email shows once email is ticked and has a recipient.
Jasper sends these alerts:
- Down or degraded: one alert per incident, once the threshold is reached. With the threshold at 1, the alert comes with the second failed check, not the first.
- Recovered: when the incident resolves.
- Domain expiry: from 30 days before the date, the monitor shows as degraded, which opens an incident and sends a degraded alert. There are no separate 30, 14 and 7-day warnings.
These settings don't take effect yet, so don't rely on them: Enable Notifications, the Notify When choices (every alert type is always sent), Notification Frequency, and everything on the Uptime Settings page.
Incidents
A failed or degraded check opens an incident. Jasper sets its severity: Major when the monitor is down, Minor when it is degraded, and Critical after 10 failures. When the monitor passes its checks again, the incident resolves by itself.
Open Incidents from the Uptime Monitoring sidebar. You can filter by status or severity. Open an incident to see its checks and history. Adding updates and reopening don't work yet: Post Update and Reopen Incident show an error page.
Limits
- Checks run from one location, Jasper's own servers.
- SSL Certificate monitors don't work yet. Jasper reads the certificate from a URL, but the form only saves a hostname, so they always report down.
- Keyword and Port (TCP) monitors don't work yet: the form has no keyword field, and no hostname for port checks, so they always report down.
- HTTP checks can't set the method, headers, body or expected status codes. DNS checks can't choose the record type.
- If Slack or your webhook rejects an alert, Jasper still marks it as sent, and the test buttons report success either way. Check the channel to be sure.
- There are no repeat reminders or escalations while an incident stays open, and no SMS, phone, PagerDuty or Microsoft Teams alerts.
- The Resolve Incident button only closes an incident once the monitor has passed its recent checks. Until then it says it did, but the incident stays open. Incidents close by themselves when the monitor recovers.
- Posting an incident update, reopening an incident and filtering incidents by monitor show an error page.
- Unticking Enable monitoring doesn't stop the checks. Use Pause on the monitor's page instead.
- Maintenance windows don't work yet. Opening a scheduled one shows an error, Start and Complete fail, and they don't pause checks or alerts.
- Anyone with the link can open a public status page, but visitors can't subscribe to updates yet.
- Check history is kept for 90 days.
- You set up and manage uptime monitoring in the web app. Its alerts also show in the desktop app's notifications.
Related
Last reviewed 5 October 2026