Skip to main content

Monitor Mesh

4 regions60s checksSSL watch
Status
GetPulseCheckLive

Uptime Monitor

OverviewAlertsConnectPlansStatus
99.98%
Log InStart Free
Log inSign up

Monitoring Overview

Everything critical, one swipe away.

All Systems Nominal

99.98%

Fleet Health

4

Regions

60s

Checks

  • Overview

    Live uptime, latency & alert surfaces

  • Alerts

    Rules, SSL tracking & status comms

  • Connect

    Email alerts now, webhooks next

  • Plans

    Plans for side projects through teams

  • Status

    Public service health & incident history

Start FreeView Status
Documentation navigation
Documentation home
  • Getting started

    • What is GetPulseCheck?
    • Quickstart: your first monitor in 5 minutes
    • Signing up, logging in & password reset
    • Understanding the dashboard
    • Plans & limits (Starter vs Pro)
  • Monitors

    • Monitor types overview
    • Creating a monitor (auto-detect + manual)
    • HTTP/HTTPS monitor guide
    • Ping monitor guide
    • TCP port monitor guide
    • SSL certificate checksPartial
    • Probe regions & multi-region confirmation
    • Check intervalsPartial
    • Managing monitors (edit, pause, bulk-delete)
  • Alerting & notifications

    • How alerting works
    • Email alerts
    • Slack notificationsPartial
    • Webhooks (custom integrations)
    • PagerDuty integration
    • Testing alerts & recovery
  • Escalation policies

    • Escalation policies overview
    • Building a multi-step escalation policyPartial
    • Assigning a policy to a monitor
  • Incidents

    • Incident lifecycle & statuses
    • Multi-region confidence scoring
    • Acknowledging & resolving incidents
    • Sharing an incident (public link)
    • Post-incident recapPartial
  • Status pages

    • Status pages overviewPartial
    • Building & publishing your status pagePartial
    • Sharing your status pagePartial
  • Reports & exports

    • Reports overviewPartial
    • CSV export availabilityComing soon
    • Report templatesPartial
  • Team & collaboration

    • Team roles explainedPartial
    • Inviting teammatesComing soon
  • Account & security

    • Your profile & contact settings
    • Account settings & maintenance windowsComing soon
    • Security: sessions, MFA & recoveryComing soon
    • Billing & plan managementPartial
  • Reference

    • FAQ
    • Probe locations & IP allow-listingPartial
    • Glossary
    • Troubleshooting

Escalation policies

Build a multi-step escalation policy

Create an ordered notification path in Dashboard Settings, then attach the policy to the monitors whose alerts should use it.

Create a policy

  1. Open Dashboard, then open Settings and find the Escalation Policies section.
  2. Select Create Policy. When no policies exist yet, the button is labelled Create First Policy.
  3. Enter a required Policy Name. Add an optional Description so teammates know when to use the policy. Leave the Active checkbox selected when the policy should be used for assigned monitors.

Configure each step

  1. Use Add Step to add the next responder path. You can configure up to five steps and move them with the step arrows.
  2. Choose a Notification Channel: Email, SMS, Voice Call, or Webhook.
  3. Enter the Recipients. Use comma-separated email addresses for email. For a webhook, enter one HTTP or HTTPS URL even though the form label mentions comma-separated emails.
  4. Set Delay Before This Step (minutes) to the number of minutes after the incident starts. Use 0 for immediate delivery when the incident opens.

Set repeat and ordering values

  • Repeat Interval (minutes) is optional. When set, it accepts a whole number from 1 to 1,440. Leave it empty for no repeat.
  • Max Repeats accepts 0 to 100 and defaults to 10. This is the maximum number of repeat attempts for a step.
  • Step orders must be unique and sequential, starting at 1. A policy can have no more than five steps.

Check channel availability

The builder exposes four channel options, but configuration visibility does not mean that every transport is available.

  • Email and Webhook steps can deliver notifications when their recipients are valid.
  • SMS and Voice Call are visible in the form, but their escalation transports are not implemented and do not deliver today.

Use immediate steps for current delivery. Steps with a delay or repeat interval are saved, but the current incident flow does not periodically re-evaluate them after the incident opens. A zero-delay step can be evaluated when the incident is created.

Save and verify the policy

  1. Confirm that the policy has at least one step, sequential step orders, and valid recipients for the selected channel.
  2. Select Create Policy. When editing an existing policy, select Update Policy.

Related

  • Escalation policies overview
  • Assign a policy to a monitor
  • Email alerts
  • Webhooks
GetPulseCheck

Global website monitoring, SSL tracking, and instant incident alerts for engineering teams who care about uptime.

Product

  • Features
  • Pricing
  • Integrations
  • Status page
  • ChangelogSoon

Company

  • AboutSoon
  • BlogSoon
  • CareersSoon
  • Contact

Resources

  • Documentation
  • System status
  • FAQ

Legal

  • Privacy policySoon
  • Terms of serviceSoon
  • SecuritySoon

© 2026 GetPulseCheck. All rights reserved.

Built with ❤ for engineers who care about uptime.