How Uptime Monitoring Works, Start to Finish
Zunoy Uptime is one connected platform, not five separate tools stitched together. This page walks through exactly how uptime monitoring works: setting up a monitor, turning it into a public status page, what happens when a check fails, and how planned work stays out of the way. Every piece here is live in the product today, not a roadmap.
The Flow
Walk Through the Monitor Workflow Step by Step
These three steps aren’t separate features, they’re one continuous path showing how uptime monitoring works. A monitor becomes a status page. That status page reflects an incident the moment one happens. And when work is planned ahead of time, maintenance keeps the whole chain quiet until it’s done.
STEP 1
Monitor Setup
Tell Zunoy what to watch and how often. Everything else on this page starts from this uptime monitoring setup.
- 1
Select Type
- 2
Target
A URL, a port and protocol, a keyword to match, or a script.
- 3
Check Interval
- 4
Regions
- 5
Advanced Settings
- 1
Page Details
An internal name, a public display name, and a custom slug.
- 2
Monitors
Pick from your existing list, and group them by tags or sections.
- 3
Branding
- 4
Access
Step 2
Status Page Sync
Take the monitor from Step 1 and turn it into something your customers can actually see.
Step 3
Incident Response
What happens the moment the monitor from Step 1 actually fails.
- 1
How It Starts
Automatically on a failed check, or declared manually by your team.
- 2
Incident Details
- 3
Tasks (Optional)
- 4
How It Resolves
The timeline closes, ready for a postmortem, written by you or drafted by Zunoy AI.
- 1
Schedule
- 2
Affected Monitors
Select one, several, or all at once.
- 3
Notifications
Each stage is toggled independently.Publish it, and a custom announcement shows on your status page instead of an outage banner.
ADDITIONAL
Maintenance Window
Keep the monitor, the status page, and the incident from Steps 1 through 4 quiet during planned work. Not every monitor needs this one, but it's there when you do.
The Glue
AI Setup That Connects Every Step
AI shows up at more than one point in this lifecycle, not just at setup.
MCP Server
Set Up Monitors by Asking
Ask it what to monitor, right from your terminal or IDE, and it handles the website monitoring setup for you, skipping the manual form entirely.
AI Agent
Explains What Just Broke
Once an incident opens, it explains the impact and suggests a next step, so your team starts fixing instead of reading logs.
AI SRE
Filters Out the Noise
It watches every check running in the background and filters out noise, so only a real spike actually reaches your team.
The same request also works from a chat interface, if that's where your team already lives.
Explore Every Feature in the Lifecycle
Monitor Types
Every check type Zunoy supports, from a simple ping to a full synthetic journey.
In Practice
How Teams Use This Monitor Workflow
- SAAS
SaaS Companies
A monitor catches a login failure, opens an incident, and updates the status page before a single support ticket comes in.
- PAYMENTS
Ecommerce Business
A checkout monitor pauses cleanly during a planned payment gateway migration, no false alarm, no confused customers.
- ENTERPRISE
Enterprise Teams
One workflow, cloned across a dozen client accounts, each with its own status page and escalation chain.
- DEVOPS
DevOps Teams
A failed deploy trips a monitor, pages the right engineer, and the whole incident timeline is there for the postmortem.
FAQ
Quick Answers About How Uptime Monitoring Works
Does every monitor need to be linked to a status page?
No. Linking is optional. A monitor works on its own, the status page is there when you want customers to see the same data your team does.
Is a maintenance window required for every monitor?
No. It's an optional add-on for planned work. Plenty of monitors run their whole lifecycle without ever needing one.
What actually flips a monitor from active to failing?
A check crossing your failure confirmation threshold, a set number of consecutive failed results, not a single blip.
What happens if I don't set up incident management?
The monitor still checks and alerts as configured. Turning on Incident Management adds automatic incident creation, ownership, and a timeline on top of that.
Can I skip straight to incident response without a status page?
Yes. Each step in the lifecycle is independent. Incident response works off the monitor directly, a status page just gives it a public face.
Can I change the workflow after a monitor is already running?
Yes. Link or unlink a status page, turn Incident Management on or off, or add a maintenance window at any point, none of it is locked in at setup.
All Connected
Everything Starts With One Monitor
Set up your first monitor, and the status page, incident routing, and maintenance controls are already there waiting, nothing else to configure separately.
One setup, the whole platform connected
Status page ready the moment you link it
Maintenance windows built in, not bolted on
Incidents route automatically from day one