Uptime is table stakes. PulseTrace also watches the things that quietly break you — certificates, DNS, security headers, infrastructure — from 12 regions, and tells you the exact moment any of it drifts.
Paste a URL or import an OpenAPI spec. Each monitor runs in parallel from the regions you choose, on an interval down to 15 seconds, with status, latency, redirects and body assertions on every check.
A failing check becomes an incident the moment it trips your rule — debounced against flapping, grouped with related failures, and carrying its own timeline of what changed around it.
Beyond “is it expired”: transport TLS, chain trust and revocation, HTTP security headers, cookies, CORS and redirects roll into one A+–F grade per endpoint; registrar, DNSSEC and email authentication into one per domain.
Pick the monitors, choose a slug (or your own domain on Pro), and the page updates itself — uptime bars, open incidents, maintenance — so customers hear it from you first.
Every type shares the same scheduling, regions, incidents, alerts and reports — a DNS check and a multi-step API journey sit on the same timeline.
Static thresholds miss the slow creep and the quiet swap. On every check PulseTrace fingerprints DNS, the TLS chain, HTTP responses and content, and learns a baseline per signal — then surfaces the moment anything steps outside its own normal.
Ten destinations and four developer surfaces, all fed by the same incident timeline. Choose per monitor, so production pages while staging only posts.
A versioned REST API with scoped keys, service accounts and per-key rate limits covers every screen. And because PulseTrace ships an MCP server, an AI assistant can add monitors, read incidents and pull reports under OAuth grants you control.
curl -s https://api.pulsetrace.app/api/v1/monitors \
-H "Authorization: Bearer pt_live_4f2a…" \
-d '{
"name": "Checkout API",
"type": "http",
"target": "https://api.example.com/health",
"interval_seconds": 30,
"region_codes": ["us-east", "eu-west", "ap-south"],
"config": { "assertions": [{ "type": "status", "equals": 200 }] }
}'
# …or, from an MCP client:
> Add an HTTPS monitor for api.example.com/health from three
regions and alert #incidents on two failed checks.
✓ Created monitor "Checkout API" · rule: down after 2 → SlackPaste a URL or import an OpenAPI spec. Required fields are marked; everything else has a sane default.
The fleet starts checking from every region in parallel, on the interval you choose.
Downtime, anomalies and external changes open incidents and route to your channels.
Availability, SLA and performance reports — plus a public status page — generated for you.
Every plan includes the uptime and protocol monitors, per-region checks and a public status page. Paid plans buy faster checks, more regions, security grading, intelligence, incidents, reporting and the API.
Add a monitor, watch it light up across regions, and see what a real trace feels like. Free to start — no card, no sales call.