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

Incidents

Incident lifecycle & statuses

Use the incident timeline to distinguish a confirmed monitor failure from an individual failed check, then follow the event through acknowledgement and recovery.

Understand the incident states

Open
The configured number of probe regions has confirmed that the monitor is failing. The incident needs a responder.
Acknowledged
A responder has taken ownership. The acknowledgement records the user and time, but it does not mean that the monitor has recovered.
Resolved
Probe results confirm recovery. The incident keeps its timeline and records the time that the service was restored.

How an incident opens

  1. Set the monitor's confirmation threshold when you configure its probe regions. The default is 2 confirming regions.
  2. Wait for probes to report results. GetPulseCheck correlates regional results in a 90-second window so nearby failures can be evaluated together.
  3. When the threshold is reached, GetPulseCheck creates one open incident for the monitor. A failure below the threshold is not promoted to a confirmed incident.

The incident record is protected against duplicate open incidents for the same monitor. A later failure after recovery creates a new incident with its own start time.

Check an incident

  1. Open Incidents from the dashboard.
  2. Use the status filters to show Open, Acknowledged, or Resolved incidents. Search by monitor name or confirming region when needed.
  3. Select an incident to open its detail page. The timeline shows when it started, whether someone acknowledged it, and when the probe confirmed recovery.

How an incident resolves

Resolution is automatic. When the correlated probe results return to an up state, GetPulseCheck sets the incident to resolved and recordsresolvedAt. The detail page calculates the total duration from the incident start and recovery timestamps. An acknowledgement remains visible in the timeline after recovery.

Related

  • Multi-region confidence scoring
  • Acknowledging and resolving incidents
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.