Everything you need to get
the most out of Pulse

Getting Started

Pulse is a lightweight uptime and response monitoring tool for developers. Add your API endpoints, and Pulse pings them on a schedule — alerting you instantly when something goes down or recovers.

There's nothing to install. Everything runs in the browser and through our hosted worker. You'll be monitoring your first endpoint in under a minute.

How it works

1. 01Sign up for free — no credit card required
2. 02Add your first endpoint — give it a name, URL, HTTP method, and expected status code
3. 03Pulse pings it every 5 minutes automatically from our worker
4. 04Get notified instantly via push notification or webhook if it goes down

Free tier limits

Monitors

A monitor is an endpoint Pulse regularly pings to check if it's responding as expected. Each monitor tracks a single URL and reports its status, response time, and uptime history.

Adding a monitor

Click Add Monitor on the dashboard. Fill in:

Editing a monitor

Click the Edit link on any monitor row (visible on hover on desktop, always visible on mobile). You can update any field including the webhook URL. Changes take effect on the next ping cycle.

Pausing a monitor

Click Pause on any monitor row to stop pinging it. No alerts will fire while paused, and the monitor will disappear from your public status page. Resume anytime with Resume.

False positive protection

Pulse requires 2 consecutive failed pings before firing a down alert. A single timeout or network blip won't wake you up at 3am. Once 2 pings in a row fail, an alert fires immediately and is logged to your incident history.

Anomaly Detection

Pulse monitors response time trends and alerts you when performance degrades — even before your endpoint goes down. If your API's response time is consistently 2x slower than its 7-day baseline for 3 or more consecutive checks, you'll get a push notification and a warning on your dashboard. Anomaly alerts appear in your monitor's incident log alongside regular down/recovered events.

Health Score

Every monitor gets a live health score — Healthy, Degraded, or Critical — shown as a badge on your dashboard and monitor detail page. The score factors in recent uptime, consecutive failures, and whether response times are stable. It gives you an at-a-glance signal beyond just up/down.

Response Time Graph

The monitor detail page includes a response time chart with two views: Timeline plots every recorded ping over the last 7 days so you can spot spikes at a glance, and Daily Average shows a bar chart of average latency per day. Min, avg, and max for the period are shown above the chart.

Monitor detail page

Click any monitor name to open its detail page. Here you can:

• →View the 7-day uptime bar with daily breakdown and hover tooltips
• →See response time trends — timeline chart and 7-day daily average bar chart
• →Check your monitor's health score (Healthy / Degraded / Critical)
• →See full ping history with status codes and response times
• →Review incident reports — timeline, root cause analysis, response time comparison, and estimated impact per outage
• →Copy a post mortem report to your clipboard with one click
• →Trigger an immediate manual ping with Check Now

Incident Reports

Every time a monitor goes down and recovers, Pulse automatically generates a structured incident report. No configuration required — reports appear in your monitor's detail page as soon as the outage is resolved.

What each report contains

Root Cause Analysis

Pulse classifies HTTP errors to surface the most likely explanation for each incident. Examples:

Post Mortem Reports

Expand any incident report and click Copy incident report to copy a formatted plain-text post mortem to your clipboard. The report includes monitor name, URL, full timeline, root cause, response time comparison, and impact estimate — ready to paste into Slack, Notion, a ticket, or an email.

Where to find them

Open any monitor's detail page and scroll to the Incidents section. Each resolved incident appears as a collapsible card showing the start time, duration, and HTTP status. Click a card to expand the full report.

Notes

• ·Incident reports are only generated for resolved incidents — an ongoing outage shows the start time and "Ongoing" for the end time
• ·Reports require the 2-consecutive-ping confirmation — a single blip will not generate an incident
• ·If anomaly detection flagged the monitor before the outage, the incident report will note this

Notifications

Pulse sends browser push notifications the moment a monitor changes status — no app required, no email setup needed.

Enabling push notifications

1. 01Click the bell icon 🔔 in the dashboard header
2. 02Click Allow when your browser prompts for notification permission
3. 03You'll receive a system notification when any monitor goes down or recovers

Browser support

Re-enabling blocked notifications

If you accidentally blocked notifications, go to your browser settings → Site permissions → Notifications → find this site → change to Allow. Then click the bell icon again to re-subscribe.

Webhooks

A webhook is a URL on your server or a third-party service that Pulse will POST to whenever a monitor changes status. One webhook URL per monitor.

Adding a webhook

When adding or editing a monitor, paste a URL into the optional Webhook URL field. Pulse will POST to that URL on every status change — both when a monitor goes down and when it recovers.

Discord webhooks

Pulse auto-detects Discord webhook URLs and sends a formatted embed message instead of a raw JSON body.

1. 01Open your Discord server
2. 02Go to channel settings → Integrations → Webhooks
3. 03Create a new webhook and copy the URL
4. 04Paste the URL into the Webhook URL field on any monitor

You'll get a red embed when a monitor goes down and a green embed when it recovers.

Slack webhooks

Pulse auto-detects Slack incoming webhook URLs and sends a formatted attachment message instead of a raw JSON body.

1. 01Go to api.slack.com/apps → Create an app → Incoming Webhooks
2. 02Enable Incoming Webhooks and add it to your workspace channel
3. 03Copy the Webhook URL (starts with hooks.slack.com)
4. 04Paste it into the Webhook URL field on any monitor

Generic webhooks

For custom servers, Zapier, Make, or any other service, Pulse sends a JSON body:

{
  "monitor_id": "uuid",
  "monitor_name": "My API",
  "monitor_url": "https://api.example.com",
  "type": "down" | "recovered",
  "status_code": 503,
  "last_response_time_ms": 1240,
  "expected_status_code": 200,
  "timestamp": "2026-01-01T00:00:00.000Z"
}

Notes

• ·One webhook URL per monitor
• ·Webhook failures are logged but do not affect monitoring or alerts
• ·Webhooks fire on every status change — both down and recovered

Status Pages

Every Pulse account comes with a public status page — a live URL you can share with your users, clients, or team. No login required to view it.

Finding your status page URL

On the dashboard, scroll down to the Share status page section. Your URL looks like:

/status/[your-user-id]

Click the copy button next to the URL to copy it to your clipboard.

What the status page shows

• →Overall system status banner — All systems operational, Degraded, or Outage
• →Each active monitor with name, current status indicator, and uptime %
• →A 7-day uptime bar (4 segments per day showing 6-hour windows)
• →Auto-refreshes every 60 seconds

Notes

• ·Paused monitors do not appear on the status page
• ·No login or account required to view a status page
• ·The status page is publicly indexed — share the URL freely

What's Coming in V2

These features are planned for upcoming releases. The free tier stays free.