All features
Availability

Uptime monitoring from 12 regions, every 15 seconds

Know an endpoint is down before a customer tells you. HTTP, TCP, UDP, DNS, ping, WebSocket and gRPC checks run in parallel from the regions you choose, on an interval down to 15 seconds, and only open an incident when the failure is real.

A single probe can be wrong — a routing blip, a regional CDN pop, a flaky path. PulseTrace runs every check from each selected region and applies your confirmation rule (for example, two consecutive failures from two regions) before it declares downtime, so the incident you get paged for is one you'd have found yourself.

Each check records status, latency and, for HTTP, the redirect chain, headers and body assertions you asked for. Results stream into the same timeline as certificate, DNS and security signals, so a downtime incident already shows what changed around it.

  • Intervals of 60 s (Free), 30 s (Team), 15 s (Pro) and 10 s (Enterprise).
  • Per-region results so a regional outage never reads as a global one.
  • Assertions on status, headers, body text and JSON fields, with pre-request scripts.
  • Private probe agent for services inside your own network.
app.pulsetrace.app · uptime monitoring

How it works

  1. 1Add a monitor: paste a URL or host, pick the type, interval and regions.
  2. 2Probes check in parallel and score each result; confirmation rules debounce flapping.
  3. 3A confirmed failure opens an incident, alerts your destinations and starts a recovery watch.

Plan availability

Free: 10 monitors, 1 region, 1-minute checks · Team: 50 monitors, 3 regions, 30 s · Pro: 200 monitors, all regions, 15 s · Enterprise: unlimited, 10 s.

Compare plans →

Questions about uptime monitoring

How fast will I know about downtime?
Within one check interval plus your confirmation rule — on Pro with 15-second checks and a two-failure rule, typically under a minute.
Does a single region failing count as downtime?
Only if your rule says so. Most teams require failures from at least two regions, so a local network problem doesn't page anyone; the per-region result is still recorded and visible.
What about services that aren't on the public internet?
Run the PulseTrace probe agent inside your network; it appears as a region and runs the same monitor types.