URL monitoring for launch teams
Know the moment your public URLs change.
Keep the URLs your campaigns depend on honest: scheduled probes, DNS guardrails, and Slack alerts when pages fail—or recover—without a separate war room.
Built for GTM operators who ship URLs weekly
Know when launch URLs drift
Track the exact pages campaigns depend on—pricing, signup, and partner landing URLs—so a silent 404 does not burn ad spend.
Probes that mirror real checks
Run HTTP probes on your schedule, validate DNS where it matters, and keep results next to your app data for a single source of truth.
Slack-first incident signal
Get concise alerts when a probe fails and when it clears, so marketing and eng share the same timeline without a separate dashboard habit.
How it works
1. Add the URLs you trust
Paste landing, pricing, and partner pages. We keep each row tied to your project so swaps during a launch stay auditable.
2. Pick probe depth and cadence
Choose manual checks when copy changes, and scheduled probes when you need continuous signal without babysitting uptime tabs.
3. Route failures to Slack
Wire your webhook once. We send short messages on failure and recovery so marketing and engineering agree on when the incident started and ended.
FAQ
Is this only for marketing landing pages?
No. Any customer-facing URL you rely on for revenue—checkout, docs, or status pages—fits as long as outbound probes are allowed by your policy.
Do you hit my pages from the public internet?
Yes. Probes use the same network path a customer would. If you need allowlisting, track our egress IPs in the in-app setup checklist once billing is enabled.
How does alerting work?
Configure a Slack incoming webhook per project. We send compact messages when a probe fails and when it returns healthy so noisy flaps are easier to triage.
Can I export history?
Pro includes CSV exports of incidents for postmortems. Starter and Free keep the last two weeks inline in the dashboard.