Observed by Atlas — nobody has proved they control this domain. Is it yours?
Gonewatch
OBSERVEDHeartbeat monitoring for cron jobs, backups, and pipelines
- FRESHNESS
- 0.99
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- AUG 25
- IN THE FLOW

Gonewatch lets developers register expected events like cron jobs, backups, and GitHub Actions, and POST a heartbeat when they succeed. If a window is missed, it sends an alert via email, Slack, Discord, Telegram, or a GitHub Issue before users notice. Optional JSON sent with the heartbeat becomes last values and charts on the dashboard.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
3 monitors · Email, Slack, Discord, and Telegram · 7 days of status history
15 monitors · Email, Slack, Discord, Telegram, GitHub Issues, and Linear · Alert reminders (up to 5) · 90 days of status history
60 monitors · Email, Slack, Discord, Telegram, GitHub Issues, and Linear · Unlimited alert reminders · 1 year of status history
Every crawl is diffed. Material changes are listed.
Nobody has vouched for Gonewatch yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about Gonewatch? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it
