Shawn Mervin

Status

I don't just build these systems, I run them in production. Every five minutes a Lambda in AWS us-east-1 checks each one, and this page shows what it found, live. If one goes down, my phone knows about it.

Checking the systems

Loading the latest runEvery 5 minutes from AWS us-east-1 (Lambda on an EventBridge schedule)

Up now
—
Median response
—
Next check
—

Systems

Up Some checks failed Down No data yet Response lines share one scale.

Reading the last run from DynamoDB.

Checks started on 12 October 2026, so most of each 30-day strip is still empty. An empty day means no data yet, never down. Hover, tap or use the arrow keys on a strip to read a day.

How it works

Small, boring, and running outside the systems it watches.

  1. ScheduleEventBridgerate(5 minutes)
  2. RunnerLambdaAWS us-east-1
  3. ProbesHTTPS probefollows redirects, 10 s timeout
  4. StorageDynamoDB24 h of detail, 30-day daily rollup
  5. YouThis pagethrough CloudFront

When something changes, my phone hears about it. If a system goes from up to down, or comes back, the Lambda pushes a notification to my phone through ntfy.

The probes run in AWS, not on the servers they check, so a server that has fallen over can't vouch for itself. Certificate expiry is read once an hour.

Want your systems watched like this?

I can set up the same for your sites and APIs: checks from outside, a status page you can share with customers, and an alert to whoever needs to know. I'm in the Lower Mainland, BC, and work with businesses across Canada and the US.

Got an operation that's outgrown its spreadsheets?

Tell me what your business does and where it's jamming up. If I'm not the right person for it, I'll say so and point you somewhere better.

What to send, and what happens next