Catch every outage. Before customers do.

Uptime checks from six regions, incidents that open themselves, a status page in your brand. Try it live.

MonitorsIncidentsStatus pageLive demo · no sign-up1ACAvery ColeNorthwind FreightUptime · last 90 days99.983%Public API · checked every 30s88msPublic APIUp157msCustomer portalUp984msWebhooksDegraded90 days agoTodayResponse time88msPublic API, p95 107msLatest checksASap-southPublic API · HTTP 20072msOKEWeu-westPublic API · HTTP 200108msOKView check logOpen incident1.8sTracking webhooks p95, above 1sRecently resolvedCPCustomer portalCustomer portal returning 502…38mResolvedCRCarrier rates serviceRate quotes timing out in Asi…52mResolvedView incidentsResponse timesPortalPublic API250ms200ms150ms100ms50ms0PORTAL AVG157msAPI AVG88msProbe regions6 regionsLatest Public API check from eachus-east96msus-west83mseu-west108msme-south86msMonitor summary14%Monitors75 up · 1 degraded · 1 paused

Features

Six probe regions. One clear answer.

HTTP, TCP and ping probes from six regions, a response-time chart per monitor and a live log of every check.

Public API72msREGIONSUSEUSWEUWMES30sHTTPCustomer portal119msCarrier rates service182ms

Every monitor in one list

HTTP endpoints, TCP ports and ping hosts side by side, each with its status, latest response and interval.

Alerts where your team already works

Route each monitor to email, SMS, Slack or a webhook. Pick the channels in the demo; the full version delivers them.

Catch slowdowns before outages

Average and p95 response times per monitor, and a slow threshold that opens an incident early.

Webhooks p95, last 60 checks1.8s↗ avg 984msDegraded threshold is 1sAveragep95p95 against twice the 1s threshold88%02s

Your data stays on your servers

In the full version, check results, incident history and subscriber lists live in your own database.

Outages start quietly: one slow response, one failed check, one region timing out.

Catch it. Confirm it. Tell your customers. That's Pulsewatch.

Every failing check becomes an incident and a status update, before the support inbox fills up.

Why it works

Calmer on-call, clearer status pages

Customer portalDetailsUPTIME · 90 DAYS99.970%(60 checks)portal.northwindfreight.comResolved in 38m

Incidents that open themselves

A failing check opens an incident with the first update already written, and recovery resolves it.

Public API, average88ms107ms p95

Response times you can read

Average and p95 for every monitor, from its last 60 checks across every probe region.

Add serviceLivestatus.northwindfreight.com99.983%

A status page in your brand

Pick the services, name and colour. Customers see live status and 90 days of history.

In numbers

Counted straight from the live demo

Shortest Interval

30

s

Checks can run every 30 seconds, so a failure surfaces within half a minute.

Probe Regions

6

From Virginia to Singapore. Pick the regions each monitor checks from.

Days Of History

90

d

Daily uptime bars per monitor, on the dashboard and the public status page.

Seeded Monitors

7

The demo opens on Northwind Freight's workspace. No sign-up, nothing to install.

Incident log

Straight from the demo's incident log

Customer portal

Investigating · +0m · Pulsewatch

HTTP 502 Bad Gateway on every check.

+0mInvestigatingIdentifiedMonitoringResolved

Customer portal

Identified · +11m · Avery Cole

A load balancer health check pointed at a retired port after this morning's deploy. Rolling back.

+11mInvestigatingIdentifiedMonitoringResolved

Customer portal

Monitoring · +24m · Avery Cole

Rollback complete and error rates are back to normal. Watching closely.

+24mInvestigatingIdentifiedMonitoringResolved

Customer portal

Resolved · +38m · Avery Cole

Stable for 15 minutes. Postmortem and a deploy check for health-check ports are tracked in OPS-412.

+38mInvestigatingIdentifiedMonitoringResolved

Shipment tracking webhooks

Identified · +9m · Avery Cole

Queue consumers are lagging after a large carrier batch import. Scaling consumers from 4 to 12.

+9mInvestigatingIdentifiedMonitoringResolved

Carrier rates service

Identified · +14m · Avery Cole

An upstream carrier API is rate-limiting our Singapore egress IP.

+14mInvestigatingIdentifiedMonitoringResolved

Carrier rates service

Resolved · +52m · Avery Cole

Traffic now fails over to a second egress IP. Quotes are healthy in every region.

+52mInvestigatingIdentifiedMonitoringResolved

Public API

Monitoring · +13m · Avery Cole

An expired database credential was rotated. Error rates are recovering.

+13mInvestigatingIdentifiedMonitoringResolved

Showing update 1 of 8

Full version

From live demo to your own build

Try everything in the browser first. When you're ready, Randy See builds the full version around your systems.

Start Here
60
Seconds
To your first incident in the live demo
Talk to Us
1
Business Day
For Randy See's reply, with a plan

Feature

Full version

Probes

Real, multi-region

Alerts

Email, SMS, Slack

Escalation

On-call chains

Status domain

Yours, with TLS

Source code

Handed over

Prefer Email?
100
% Yours
Source code and data, on your servers

Get the full version. Built by Randy See.

Tell Randy See what you need to watch. We reply within one business day with a plan for your build.

The last 189 checks from the demo workspace: 153answered within their monitor's threshold and 36 were slow.