PulseWatch
Get started
LIVE · 0.3s global probes

Know when your site breaks before your customers do.

PulseWatch checks your websites every minute, detects incidents the moment they happen, and uses Claude to explain why things broke — not just that they did.

→ No account. No spam. Results in ~2 seconds.

pulsewatch · live feed
  • 200acme.shop142ms
  • 200greenleaf-law.com287ms
  • 200bistro-rouge.fr3140ms
  • 503luna-studio.co—ms
  • 200hart-dental.nl198ms
Claude analysis — 12s ago

luna-studio.co returned a 503 from Cloudflare. The origin appears unreachable — likely an exhausted worker pool or a stopped container. Check `systemctl` first.

01 · Flow

Three steps. No account.

The entire guest experience takes under five seconds.

  1. STEP 01

    Paste a URL

    No signup, no config. Drop any public URL into the field and we'll run a full probe.

  2. STEP 02

    Claude analyzes

    We check HTTP status, response time, SSL certificate, and security headers — then Claude interprets the signal.

  3. STEP 03

    Get answers

    See what's healthy, what's not, and what to do about it. Upgrade to watch continuously.

02 · Features

What an account unlocks

Everything that matters for keeping your clients' sites up. Set up in minutes.

Create a free account
60s
min interval

Continuous monitoring

HTTP probes every 60 seconds to 1 hour. Response time, status code, and SSL tracked for up to 10 sites.

Sonnet
+ Haiku fallback

AI incident analysis

When three consecutive checks fail, Claude Sonnet diagnoses the likely cause, impact, and next steps.

7d
digest

Weekly reports

A Monday-morning briefing on uptime, slowest endpoints, and the week's worst incidents — ready to share.

90d
history

Public status pages

Share a clean, brandable status URL with your clients. 90-day uptime history, no PulseWatch branding required.

03 · Inside your account

A glance is enough.

Once signed in, every site you own lives on a single board — uptime, latency, SSL, and AI-written incidents, all in one scroll.

Unlock the full dashboard
Dashboard · Overview
updated just now
Sites
8of 10
Uptime
99.94%30d
Avg latency
284msp50
Incidents
1open
SiteLatency
  • acme.shop142ms
  • greenleaf-law.com287ms
  • bistro-rouge.fr3140ms
  • luna-studio.co—
  • hart-dental.nl198ms
  • northwind.dev211ms
acme.shop · Response time
last 24h
284ms
p50 · peak 680ms at 14:20
↓ 8% vs. yesterday
00:0006:0012:0018:00now
Incident · luna-studio.co
opened 4m ago
DOWN · 5033 consecutive failed checks
Claude Sonnet · cause analysis

Origin returned 503 from Cloudflare. Likely an exhausted worker pool or a stopped container. Restart the app process and check `systemctl status`.

confidence 0.86impact: high
Email + Slack alert sent to 2 channels
LIVE · System status
  • APIoperational
  • Probe workersrunning
  • LLM pipelineready
  • Databaseconnected
READY WHEN YOU ARE

Try it on one of your sites.
Keep it running for the rest.

Guest checks are anonymous and ephemeral. An account unlocks continuous monitoring, alerts, and AI diagnostics.

Try without accountCreate a free accountView the source on GitHub