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

Monitors

Configure a TCP port monitor

Check that a host accepts TCP connections on the port your service needs and flag slow or repeated failures.

Set the connection

  • Enter a hostname or IP address and a port from 1 to 65535. The form starts with port 80 as its default.
  • Choose a check interval from 1 minute to 1 hour. The default is 5 minutes.
  • Set the connection timeout from 1 to 60 seconds. The default is 10 seconds.
  • Set retries from 1 to 10 attempts. The default is 3.

Validate the connection

  • Add an optional expected response string, up to 1000 characters, when the service returns a banner or other predictable response.
  • Set the connection-time threshold from 100 to 60000 ms. The default is 5000 ms.
  • Set the failure threshold from 1 to 20 consecutive failures. The default is 3.

Related

  • Monitor types overview
  • Creating a monitor
  • Check intervals
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.