Frequently asked questions.

When a monitoring region sees a failure, other regions check immediately. An incident is confirmed when at least two separate regions agree the site is down. A failure contradicted by an up result is recorded as a false alarm without an outage email.

You can configure checks as often as every minute. Detection and email timing also depend on verification, request timeouts and any alert delay you set. A one-minute interval is not a one-minute alert guarantee.

Current monitoring regions are in the US: West, Central and Dallas. Region access and counts depend on your plan.

By email. Configure named recipient lists, rules by group or monitor, recovery notices and optional still-down reminders.

Web Images requires a plan with image capture or the Image Capture add-on, plus capture-enabled monitoring regions. Storage is plan-dependent.

A configured response-time threshold can mark a site as degraded on the dashboard. Slowness alone does not send an email alert.

Yes. Each group can publish its own public status page, either detailed (each monitor by name and status) or anonymous (overall health without names or URLs), with optional password protection.

Public HTTP and HTTPS websites or pages, with optional keyword checking and SSL checks for HTTPS. Ping, port, DNS, heartbeat and JSON-specific API monitoring are not currently supported.

Review monthly figures in the app. A PDF report is emailed on the first of each month. False alarms are excluded from downtime and availability calculations.

Sign up, choose a plan and manage billing through Press Mage; your workspace is provisioned automatically.

Yes. Customer groups keep sites and client details together. Application groups organize your own systems.

No. It checks public websites and refuses private networks, internal addresses and sensitive ports.