Skip to content

Outage intelligence

Knowbeforeyourcustomerstellyou.

Monitor cloud provider outages, publish incident status pages, and understand your vendor dependencies before they affect your users.

Answers are grounded in live incident data. If a vendor isn't impaired, it says so.

pulsewatch · live

Active incidents detected

Incident feed

Recently resolved

History

Incidents closed after signals returned to baseline.

Signal volume · 24h

Hourly source signals across the most active services.

Most active vendors · 24h

Predictive ForecastingAWSAlert AutomationStripeDependency MappingSlackIncident AnalyticsGitHubWar RoomCloudflareStack ScanGoogle CloudTeam Status PagesOpenAIREST API & WebhooksFigmaPredictive ForecastingAWSAlert AutomationStripeDependency MappingSlackIncident AnalyticsGitHubWar RoomCloudflareStack ScanGoogle CloudTeam Status PagesOpenAIREST API & WebhooksFigma

Why PulseWatch?

Your site. Your vendors. One clear answer.

When something breaks, PulseWatch helps you quickly understand whether it is your website, your SSL/domain setup, or a third-party service your business depends on.

See what’s breaking now

Is your site down?

Check your own websites, SSL, and domain health before customers notice.

Or is it a vendor?

Spot issues with Stripe, Google, Microsoft, Avanan, AWS, and the tools your business relies on.

Know where to look

Get one clear answer, then route alerts to the right people before support tickets pile up.

What you can see

A clearer, friendlier way to understand service health.

Compare plans

Evidence

See what is actually happening, and what we cannot see

Vendor status, public reports, synthetic checks, and official signals in one view — with the monitoring limits stated instead of hidden.

  • Four explicit states, including insufficient monitoring
  • Watchlists that narrow the view to your own stack
  • Incident history with severity, duration and confidence

Incident states

  • Normal

    Report volume is within the expected baseline. No action required.

  • Possible issue

    Report volume is meaningfully above baseline. Early signal — not yet conclusive.

  • Major issue

    Sustained, high-confidence spike across multiple signals. Treat as a vendor incident in progress.

  • Resolved

    Volume returned to baseline range and incident closed.

Routing

Send it to the people who can act on it

Alert rules deliver meaningful incidents and recoveries to the tools your team already runs, with signed and logged webhook delivery.

  • Ten delivery channels, per rule
  • Thresholds, cooldowns and quiet hours
  • Grouping so one outage is not ten pages

Supported delivery channels

EmailIn-appWebhookSlackMicrosoft TeamsDiscordPagerDutyOpsgenieServiceNowDatadog

Your own surface

Monitor your own sites next to your vendors

Add your own URLs and PulseWatch checks them on the same schedule it watches third-party dependencies.

  • Your sites and your vendors in one dashboard
  • Certificate and domain expiry caught before customers notice
  • War Room, forecasts and the REST API on paid plans

Checks run per site

  • Reachability

    HTTP status and failure category per check

  • Latency

    Response time recorded per check

  • TLS certificate

    Grade and expiry assessment

  • Domain expiry

    Registration expiry reminders

How it works

Three simple steps to monitor your vendor stack.

Start simple. Advanced tools like War Room, webhooks, and forecasts are there when your team needs them.

Step 1

Scan your stack

Paste your tools and PulseWatch finds the vendors your business depends on.

Step 2

Watch key services

Save important vendors so your dashboard focuses on what can affect your team.

Step 3

Get useful alerts

Receive alerts when meaningful outages or recoveries happen across your stack.

Why teams trust PulseWatch

Operational rigor, not a vanity dashboard.

PulseWatch exposes evidence limits directly and records what was evaluated instead of presenting missing coverage as certainty.

Explicit coverage state

Every service distinguishes operational evidence, unknown status, and insufficient monitoring instead of assuming an all-clear.

Three classes of preventable outage, caught

Free TLS grading (A–F), SSL expiry alerts, and domain registrar reminders ship on every plan — even Free.

Recorded incident history

Stored incidents include timestamps, confidence, review state, and available evidence for later investigation.

Reliable alert delivery

Signed webhook deliveries with automatic retries. Delivery status is logged and auditable.

Developer access on paid plans

REST API, signed webhooks, and clear per-key rate limits on Pro and Business.

Replay-gated sources

Automated sources cannot influence incidents until their historical replay meets the configured evidence threshold.

Pricing

Start free, then scale your outage workflow.

Scan your stack first, save the vendors that matter, then upgrade when you need more watchlists, alerts, seats, or API access.

Free

Free

Explore the platform

  • 1 watchlist, up to 5 vendors
  • Monitor 3 of your own sites
  • 3 in-app & email alert rules
  • 30 days of incident history
Start free
Pro

Pro

$49/mo

For individuals & small teams

  • 5 watchlists, 30 vendors
  • Monitor 5 of your own sites
  • 25 alert rules across email, Slack & webhooks
  • Webhooks & REST API access
Choose Pro

Business

$149/mo

For operations & support teams

  • 50 watchlists, 100 vendors
  • Monitor 10 of your own sites
  • 200 alert rules
  • 10 team seats included
Choose Business

Need a different level of coverage? Talk to our team about Enterprise →