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

Reference

Troubleshoot a monitor or notification

Start with the symptom you can see, then verify the monitor configuration, regional evidence, and delivery channel before escalating the issue.

A monitor stays unknown

  1. Confirm that the monitor is not paused or deleted and that it has at least one configured region.
  2. Check whether the problem affects one region or every configured region. A single-region gap can indicate a placement or target-network issue.
  3. If this is local development, start the full probe fleet with docker compose --profile with-probe up -d.
  4. For preview or production, contact the platform operator to verify the corresponding Fly.io probe app and machine health.

The Go probe is the component that polls endpoints and writes monitor status. Without a running probe, no new result can move a monitor out of unknown.

A failure looks like a false positive

  1. Open the incident and compare the confirming regions with the monitor's configured regions.
  2. Check whether the target firewall or WAF allow-lists all required probe sources.
  3. Review the monitor's response-time, status-code, keyword, or packet-loss threshold and adjust it only when the threshold reflects the service's expected behavior.
  4. Use the monitor's test-alert and test-recovery actions to verify delivery separately from the target failure.

An SSL warning appears

Confirm that the target is an HTTPS monitor and that SSL validation is enabled. Check the certificate chain, hostname, validity period, and the remaining expiry window. SSL validation is currently an HTTP monitor option, not a separate certificate monitor type.

A notification did not arrive

  1. Confirm that alerts are enabled and that the incident reached the configured confirmation threshold.
  2. Verify the destination address, webhook URL, signing secret, or PagerDuty routing key without pasting credentials into a support request.
  3. Check the channel's delivery history or provider logs, then send a test alert from the monitor.
  4. If recovery is the missing message, verify that recovery notifications are enabled and that the incident has resolved.

Related

  • Probe regions and multi-region confirmation
  • SSL certificate checks
  • Testing alerts and recovery
  • Probe locations and IP allow-listing
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.