Connecting to your dashboard…

Add a monitor

Monitor a public website, a host by ping, or a TCP port. Only monitor systems you own or have permission to check.

A public HTTP or HTTPS URL.

Monitoring locations

Choose where this website is checked. An outage requires failure from every selected location in the number of consecutive windows configured below (two by default). One location provides less independent confirmation.

Advanced check and alert settings

Every selected location must confirm a failure. Lower confirmation counts respond sooner but are more sensitive to brief interruptions.

Comma-separated codes or ranges, such as 200-299, 404. Redirects are followed; this checks the final response.

Optional, case-sensitive text in the first 256 KiB of the response. Use GET for content checks.

Turn off only for hosts whose certificate name does not match, such as a server hostname behind a load balancer.

Optional, HTTPS only. Clear the username to remove saved credentials.

Stored encrypted and never shown again.

Checks run 24x7 either way. Outside these hours alerts wait; an outage that recovers before the window opens is not announced.

Sent by email while every selected location still reports the outage.

Checks run every minute; result collection and email delivery add time. A one-minute setting is not an instant-alert guarantee.

Domain expiry reminders

Uses public registry (RDAP) data, refreshed daily. Not every domain ending has an RDAP service; when expiry cannot be read no reminder is sent. Same recipients as the certificate reminders below.

Certificate expiry reminders

Use up to five different day counts from 1 to 90. Reminders go to the verified recipients selected below. One reminder is scheduled per certificate threshold; a newly enabled website gets the closest applicable warning, not a burst of missed reminders. Scheduled maintenance holds delivery. No fresh certificate observation means reminders wait for fresh evidence.

Alert recipients

Only verified contacts can receive alerts. Manage contacts in Account settings. If your last contact opts out, alerts return to your account email.

Maintenance

Checks continue during maintenance. Covered minutes are labeled maintenance and excluded from observed uptime and coverage. Alerts are held; an existing incident is never automatically marked recovered.

Recurring schedules

Add recurring maintenance

Repeat weekly on the days you select. Choose all seven for daily maintenance. Future occurrences continue until you cancel this schedule.

Days

Up to five schedules per monitor. Starts follow the selected time zone; duration is elapsed time. A clock time skipped by daylight saving is skipped that day. A repeated time runs once, at its first occurrence. Upcoming dates below are displayed in your browser’s local time zone.

Individual occurrences

Schedule a maintenance period

Times use your browser’s local time zone. Up to seven days per period.

Check history

Delete this monitor?

Account settings

API access

Read data or automate monitors from your own scripts. Choose only the permissions your script needs. Keep them private; use only in trusted server-side tools. API documentation

Create an API token
Permissions

Up to ten active tokens. Password resets revoke all tokens. Signing out does not revoke tokens; revoke them below when no longer needed.

Alert contacts

Invite up to ten email contacts. Each person must verify and agree before you can select them on a website. A contact receives alerts, not account access.

Two-factor authentication

Use an authenticator app such as Google Authenticator, Microsoft Authenticator, 1Password, or another app supporting time-based codes. Password resets do not turn off two-factor authentication.

Lost your authenticator? Use a recovery code at login. If you have neither, contact support; an email password reset alone cannot bypass two-factor authentication.

Your public status page

Choose the information you want anyone with the link to see. Your website URLs, account details and private maintenance notes are never included automatically. Use public-safe titles and labels.

Public components

Select up to five monitors and write a public label for each. Unselected monitors are never included.

Unpublishing stops future access, but cannot remove copies already saved by visitors.

Add a webhook

HTTPS on port 443 and a public domain name. Slack, Discord and Teams URLs are secrets: they are stored encrypted and never shown again.

Send events for

Each request carries Pulse-Webhook-Id, Pulse-Webhook-Timestamp and Pulse-Signature: v1= HMAC-SHA256 of timestamp.id.body with your signing secret. Reject timestamps older than five minutes and deduplicate by ID. Failed deliveries retry for about 8.6 hours.

Add a heartbeat

The first check-in is due one interval plus grace after creation. Each successful check-in starts the next interval. Times use elapsed seconds, not a calendar or cron schedule. Alerts are processed by the worker and email queue; they are not instantaneous.

Heartbeat alert recipients

Paused heartbeats count toward your allowance. Resuming or changing the schedule starts a fresh interval. If all selected contacts opt out, future outage evaluation restores owner delivery.

Heartbeat history

Up to 50 recent incidents. Closed incidents are retained for 30 days; open incidents remain until resolved or explicitly changed.