Outage alerts for AWS, Slack, Stripe, and 1,700+ services your team depends on.
PulseWatch delivers real-time outage alerts the moment a third-party service starts misbehaving — Slack, email, signed webhooks, or in-app push, routed by severity. How far ahead of vendor status pages we land is measured per incident and published at /lead-time. Free forever, no card required.
Last updated
Free SSL + domain expiry monitoring. Because nothing kills trust faster than a green padlock turning red — or worse, your domain getting auctioned.
We inspect the TLS certificate on every site you monitor every day, grade your security posture A → F (TLS version, cipher strength, HSTS), and run a daily registrar lookup on your domain. You get email alerts at 30 / 14 / 7 / 3 / 1 days before your cert expires, and 60 / 30 / 14 / 7 / 3 / 1 days before your domain registration lapses. Plus a hard alert if either actually expires.
Four ways to get alerted
Pick the right channel for the right severity. Pages for major incidents, Slack for visibility, email for support digest, webhooks for everything custom.
Slack
Direct delivery to your incident channel. Filterable by severity. Ideal for support and ops visibility.
Signed webhooks
HMAC-SHA256 signatures, automatic retries, and a delivery health dashboard. Wire into PagerDuty, OpsGenie, or your own runbook.
Per-incident emails or a daily digest. Available on every plan including the free tier.
In-app + push
Real-time toasts in your dashboard plus opt-in browser push notifications when watched services go red.
How alerting actually works
Three primitives that turn raw detection into an alert your team trusts.
Watchlists scope WHAT to alert on
Group the services your team depends on (e.g. 'Production stack' = AWS, Stripe, Auth0, Slack, Cloudflare). Alerts fire only for services in your watchlist.
Severity thresholds scope WHEN to alert
Per-rule thresholds: "any change", "possible issue", "major issue only". Pair "major issue only" with paging channels and "possible issue" with Slack visibility — no fatigue.
Cooldowns prevent re-paging the same incident
Configurable cooldown per rule (default 30 minutes). One alert per channel per incident, plus an auto-resolve notification when the vendor recovers.
Get alerts for the vendors that actually run your stack
We monitor 1,700+ services. Here are the ones most teams build alerts on. Click any service to see its live status page.
Cloud & infrastructure
Communication & internal
Don't see a service? Browse all 1,700+ or request one.
Three alert configurations real teams ship
Customer support: front-line visibility
- › Watchlist: Stripe, Auth0, SendGrid, Slack
- › Severity: possible_issue + major_issue
- › Channel: Slack #support-ops
- › Cooldown: 30 minutes
Support sees vendor degradations 5–20 minutes before tickets land. Posts a banner before the wave hits.
On-call engineering: paging-grade only
- › Watchlist: AWS, Cloudflare, Auth0
- › Severity: major_issue ONLY
- › Channel: Webhook → PagerDuty
- › Cooldown: 60 minutes
On-call only gets paged when a third-party is the actual cause of a production issue. No fatigue.
Vendor management: weekly digest
- › Watchlist: Entire SaaS stack (30+ services)
- › Severity: any incident
- › Channel: Email digest, weekly
- › Use: Renewal conversations + SLA tracking
90-day rolling reliability evidence per vendor. Negotiate from data at renewal time.
Stop finding out from your customers.
Build your first watchlist, pick a delivery channel, and get your first alert in under five minutes.