Uptime monitoring that detects outages in one second

A true 1-second engine, with intervals for every plan

Most “status page” products schedule checks a minute or more apart, so an outage can run for most of a minute before anything notices. PingInsight was built around a polling engine that can fire every second, and the interval is tunable per monitor so you spend frequency where it matters.

The interval ceiling scales with your plan: Free checks every 60 seconds, Pro every 30 seconds, Business every 5 seconds, and Enterprise every 1 second. Put your checkout flow or payments API on the tightest interval, and leave a marketing redirect on a relaxed one — you control it monitor by monitor.

Web and network checks

HTTP/API checks request any URL and validate the response — status code, latency, and the body or headers — which makes them the workhorse for websites and REST endpoints. Ping (ICMP) checks confirm a host is reachable at the network layer and measure round-trip latency, ideal for routers, gateways, and bare hosts. TCP port checks open a connection to a specific port to prove a service such as a database or message broker is accepting connections. UDP port checks probe connectionless services like game servers, VPN endpoints, or syslog where there is no handshake to rely on.

DNS, SSL, and domain checks

DNS checks resolve records and verify the answer matches what you expect, catching misconfigured or hijacked records before users hit a dead name. SSL certificate checks watch the served certificate and warn you well before it expires, so a forgotten renewal never takes the site down. Domain/WHOIS checks track the registration expiry of the domain itself — the slow-motion outage that bites teams who let a renewal lapse.

Mail, SSH, NTP, heartbeat, and group checks

Mail is monitored across all three protocols: SMTP checks confirm outbound mail can be sent, IMAP checks confirm a mailbox is reachable for sync, and POP3 checks confirm legacy retrieval still works. SSH checks verify that a server is accepting secure shell connections — useful for fleets and bastions. NTP checks measure clock offset so time drift never silently breaks auth tokens, certificates, or scheduled jobs. Heartbeat (cron) checks invert the model: instead of us calling you, your job calls us on a schedule, and a missed ping raises an alert — perfect for backups, ETL, and cron. Group (aggregate) checks roll several monitors into one health signal so a single component on your status page reflects the true state of a multi-part service.

Assertions: don't just check it's up, check it's right

A 200 response doesn't always mean the service is healthy. HTTP/API checks let you assert on what actually matters: the status code, a substring or pattern in the response body, a specific JSON field, response headers, and a latency ceiling so a degraded-but-up endpoint still trips. Stack several assertions on one check and the monitor only passes when every one of them holds — turning a shallow ping into a real synthetic test.

Multi-location quorum and consecutive-failure confirmation

PingInsight probes from three live regions — us-east-2 (Ohio), us-west-2 (Oregon), and eu-west-1 (Ireland). A single region seeing a timeout is often a transient network path problem, not your service being down. So before a monitor is marked DOWN, the outage must clear a quorum of regions (at least two agree) and persist across a configurable number of consecutive failures.

That two-stage confirmation is how you get fast detection without noisy false alarms: the 1-second cadence finds problems quickly, and quorum plus consecutive failures make sure what you're paged on is real.

Exact-second, millisecond-stamped timelines

Every probe is timestamped to the millisecond, so an incident is recorded as a precise interval rather than rounded to the nearest check window. Your timeline reads “down 14:02:09.3 → 14:02:13.5, 4.2s” instead of a vague one-minute bucket. That precision flows straight into your status page, your incident duration, and the uptime math — and it's the difference between guessing at an SLO and measuring it.

Alerts and history

When an outage is confirmed, PingInsight notifies you on any of eleven channels — email, Slack, Discord, Telegram, Microsoft Teams, PagerDuty, Google Chat, ntfy, Mattermost, Rocket.Chat, and signed webhooks. Raw check results are retained for 7 days on Free and Pro, with rolled-up history kept for 365 days on Pro, 730 days on Business, and 1095 days on Enterprise so you can report on trends over a year or more.