Uptime Monitor
Agent. Confirms outages and sends the alerts.
Recipe
Website health watch: know when your site is down or slow
Hear about an outage or a slow page before your customers do, with the fix lined up for your approval.
Website health watch is a recipe in Ai1, the AI agent platform by MyZone AI, where several agents and skills work together to deliver one outcome. The Uptime Monitor checks your sites on your schedule and confirms a real outage before alerting, the Page Speed Monitor retests your key pages and flags slowdowns, and the Webmaster prepares the fixes you approve.
- Part of Ai1
- Outages confirmed before anyone is alerted
How the recipe works
Three agents, one watch on your site
Two monitors watch and one agent fixes. A fix reaches your live site only with your approval.
- 1Uptime MonitorUptime check
- 2
Page Speed MonitorPage speed check - 3
WebmasterFix list - ResultAn alert, and what to fix first
Know first
A confirmed outage alerts the right people, with a recovery notice when the site is back.
Slow pages caught
Key pages are retested on your schedule, with an alert on clear slowdowns and on recoveries.
Fixes in order
Ranked fixes go to the Webmaster if you ask, and a retest shows whether the change helped.
At a glance
Website health watch in short
| Agents | Uptime Monitor, Page Speed Monitor and Webmaster |
|---|---|
| Uptime checks | From every minute to once a week, chosen for each site |
| Before alerting | Two failed checks a few seconds apart confirm a real outage |
| Speed tests | Key pages retested on your schedule, at most once an hour |
| Changes | Only the fixes you approve |
Why watch both
A site can be up and still lose customers because a key page has become slow. Watching only uptime misses that, and watching only speed misses an outage. This recipe watches both and hands the fixes to the agent that looks after your site.
How this differs from the Uptime Monitor on its own: the recipe adds speed tests on your key pages, and a path from an alert to a fix.
How it works
How the recipe runs
A simplified view. The monitors only watch; fixes wait for you.
Step 1: Tell it your sites
Your site addresses, your key pages, how often to check each one and who should be alerted.
You approve
Step 2: Test the alerts
A test alert for each route, sent only after you say yes. A route counts as ready once its test arrives.
Step 3: Watch around the clock
Checks each site on your schedule and confirms a real outage with two failed checks before alerting.
Step 4: Retest key pages
Retests each key page on your schedule and alerts on clear slowdowns and on recoveries.
You approve
Step 5: Fix and prove
If you ask, ranked fixes go to the Webmaster, which shows you a preview first. A retest shows whether the change helped.
What one week looks like
Example: one week of health watch
Example with a fictional business. Names and figures are invented to show the kind of week you get.
What it was asked: Is our site up and fast, and what should we fix first?
| Outage | One confirmed outage on Tuesday night, lasting 14 minutes. An alert went out, then a recovery notice. |
|---|---|
| False alarms | None. A single failed check is checked again before anyone is alerted. |
| Slow page | The booking page slowed down on phones after a new photo gallery was added. |
| Fix first | Resize the gallery photos on the booking page. |
| After the fix | The Webmaster showed a preview, you approved it, and a retest confirmed the page was fast again. |
Run it on a schedule
It keeps running on your schedule
Once it is set up, health watch runs without anyone asking. Each site and each key page has its own schedule.
| Starts | The schedule you set for each site and page |
|---|---|
| Schedule | Uptime checks from every minute to once a week; key pages retested at most once an hour |
| Needs from you | Your site addresses, your key pages and who to alert |
| You get | Alerts on confirmed outages and clear slowdowns, recovery notices and ranked fixes |
| If it can't finish | If the checker stops, it says plainly that monitoring is not running and never claims your sites are fine. |
Built-in guardrails
You approve every fix
Here is how the recipe keeps you in control.
- Real outage alerts go out automatically. Test alerts are sent only after you say yes.
- Slack alerts go only to a private channel or a person, never to a public channel.
- The monitors never edit your site. Nothing reaches your live site without your approval, and every change has a tested way to undo it.
Better together
Works well with
The agents and recipes behind this recipe.
Page Speed Monitor
Agent. Tests your key pages and ranks the fixes.
Webmaster
Agent. Looks after your live site and its changes.
New page, tracked from day one
Recipe. Builds a page that is tracked and fast from the start.
Common questions
Frequently asked questions about the website health watch
How does it avoid false alarms?
Two failed checks a few seconds apart confirm a real outage before anyone is alerted.
Where do the alerts go?
To the people and routes you choose. While an outage lasts there is an hourly reminder, and a recovery notice when the site is back.
Does it fix the site on its own?
No. The monitors only watch and alert. Fixes go to the Webmaster if you ask, and nothing reaches your live site without your approval, apart from low-risk tasks you choose to allow up front.
What if a page is blocked from the speed test?
If your site's bot protection blocks the test browser, the Page Speed Monitor leaves that page out and explains how to let the test through.
Start watching your site
We will set up the watch on your own site and walk you through the first week.
- Your own private serverEvery Ai1 plan runs on a private server that belongs to your business alone.
- Your data stays yoursStored on your server, not used to train AI models, and you can export everything you build at any time.
- Choose your AI modelBring your own AI provider account and pay it directly, with no markup from us.
- No lock-inMonthly plans run month to month with no long-term commitment, and everything you build can be exported.