Skip to content

Know when a failure is real.

One failed location stays localized. A strict majority of fresh results confirms a regional incident.

WebGuard for iPhone and iPad

Your monitoring, wherever you are.

Review service health, inspect monitoring details, receive push alerts, and follow notification, maintenance, and incident workflows in the native iOS app.

  • Sign in to your WebGuard account and review monitoring status
  • Open service details and recent results
  • Receive push alerts and review them in Notification Center
  • Use available maintenance and incident actions
Product preview · sample data
WebGuard dashboard showing the actual product interface and monitoring status

One failed check isn’t a global outage.

Compare fresh checks from multiple locations and see how WebGuard classifies the result.

New YorkUS East
FrankfurtEU Central
SingaporeSoutheast Asia

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 monitoring

From setup to incident resolution

01

Create monitors

Add the check type, target, regions, and a 1, 5, 10, 15, 30, or 60-minute interval. New and existing monitors default to 15 minutes per selected location.

02

Define alerts

Choose email, chat, webhook, or push channels per monitor and keep the right people informed.

03

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.

  1. 01

    See the overall picture

    The operations overview brings monitor states and recent results into one place.

    Operations overview
    WebGuard operations overview with monitors and recent results
  2. 02

    Understand one check

    Open a monitoring detail to review the latest result, uptime history, and response time for a single target.

    Monitoring detail
    WebGuard monitoring detail with latest check, uptime history, and response time
  3. 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
    WebGuard status pages empty state, ready to set up a public status page

Four rules behind every signal

Know what confirms an incident, how often selected checks run, and what a slow response means.

  1. 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.

  2. 02

    Choose a website or keyword interval

    Select 1, 5, 10, 15, 30, or 60 minutes per monitor. New and existing monitors default to 15 minutes.

  3. 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.

  4. 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.