Single-region uptime checks cry wolf; one bad network hop and your phone buzzes at 3 a.m. for nothing. This bot probes every endpoint from three regions and only pages when the failures actually agree.
Single-region uptime checks cry wolf; one bad network hop and your phone buzzes at 3 a.m. for nothing. This bot probes every endpoint from three regions and only pages when the failures actually agree.
When an outage is real, it opens a PagerDuty incident with the failing region, status code, and latency, then updates your status page. It pages with confidence, not noise, and closes the incident itself on recovery.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Treat a check as failed only when at least two regions agree, so one flaky probe does not page anyone.
pending
Open a PagerDuty incident with the failing region, response code, and latency when a real outage is confirmed.
pending
Update the public status page and close the incident automatically once checks recover.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Given multi-region probe results for one endpoint, decide UP or DOWN: report DOWN only if two or more regions failed within the same window, and return region, status code, and latency.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.