Know when a failure is real.
One failed location stays localized. A strict majority of fresh results confirms a regional incident.
Find the right monitoring feature
Focused pages explain every check, workflow, and public status surface.
One failed check isn’t a global outage.
Compare fresh checks from multiple locations and see how WebGuard classifies the result.
WebGuard classification
Localized degradation
One location is failing. It is shown as degraded; no incident opens.
A majority of fresh results must recover for WebGuard to close the incident.
Illustrative example · classification uses fresh location results.
Explore multi-location monitoringFrom setup to incident resolution
Create monitors
Add the check type, target, and regions that fit your service. Website and keyword checks run at least 15 minutes apart per selected location.
Define alerts
Choose notification channels and keep the right people informed.
Share status
Communicate incidents and maintenance through public status surfaces.
From signal to shared status.
See how monitoring checks become useful context for your team and customers.
01
See the overall picture
The operations overview brings monitor states and recent results into one place.
Operations overview 02
Understand one check
Open a monitoring detail to review the latest result, uptime history, and response time for a single target.
Monitoring detail 03
Prepare a public status page
Choose which service components to share so customers can follow status updates in one clear place.
Set up status pages
Four rules behind every signal
Know what confirms an incident, how often selected checks run, and what a slow response means.
- 01
A strict majority opens a regional incident
One failed location stays local. More than half of fresh results must fail for a regional incident; every location failing is global.
- 02
Website and keyword checks wait at least 15 minutes
The minimum interval applies independently at each selected location.
- 03
Availability and latency are separate signals
A slow response can trigger its own alert after the configured consecutive checks; it does not change the availability result.
- 04
No marketing or analytics tracking cookies
This site does not use marketing or analytics tracking cookies.
FAQ
Clear answers about monitoring
What is WebGuard?
WebGuard is a monitoring platform for websites, APIs, jobs, servers, certificates, domains, and public status communication.
Who is WebGuard for?
WebGuard is built for SaaS teams, developers, and individual projects that need clear operational signals without unnecessary complexity.
How does WebGuard help during an outage?
WebGuard combines checks, regional results, notifications, incident context, and public status surfaces so teams can detect, explain, and resolve service issues.
Use WebGuard for free
Register or explore the application directly with demo access.