Monitors
Add any API endpoint and PingRoot checks it automatically — every minute on Pro and Team, every 5 minutes on Free.
Monitor Status
Section titled “Monitor Status”Every monitor has one of three statuses:
| Status | Visual | Meaning |
|---|---|---|
| Up | Animated green pulse dot | Last check returned the expected status code |
| Down | Red indicator | Last check failed (wrong status code, timeout, or network error) |
| Pending | Gray indicator | No checks have run yet (newly created monitor) |
Each monitor card shows its status, URL, average latency, and uptime. Use the icons to edit, pause, manage alerts, view logs, or configure webhooks.
Creating a Monitor
Section titled “Creating a Monitor”- Click “Add Monitor” on the dashboard.
- Fill in the form:
- URL (required): The endpoint to monitor.
- Method (required): HTTP verb (default: GET).
- Expected Status (required): Expected HTTP status code (default: 200).
- Interval (required): Check frequency in minutes (minimum: 5 min on Free, 1 min on Pro/Team).
- Headers (optional): JSON object of custom headers.
- Click “Create Monitor”.
- The monitor appears in the grid with Pending status.
- Status updates to Up or Down after the first check runs.
Editing a Monitor
Section titled “Editing a Monitor”- Click the pencil icon on the monitor card.
- An edit dialog opens, pre-filled with current values.
- Modify any field (URL, method, expected status, interval, headers).
- Click “Save changes”.
- Changes take effect on the next check cycle.
Deleting a Monitor
Section titled “Deleting a Monitor”- Click the trash icon on the monitor card.
- A confirmation dialog appears: “Delete this monitor? This cannot be undone.”
- Confirm deletion.
- The monitor and all its historical logs are permanently deleted.
Pausing and Resuming a Monitor
Section titled “Pausing and Resuming a Monitor”Toggle the Active switch on the monitor card:
- Off (paused): Checks stop. No new logs are created. No alerts fire.
- On (active): Checks resume on the next scheduled run.
Pausing does not delete any data. All historical logs remain intact.
Viewing Monitor Logs
Section titled “Viewing Monitor Logs”Click the logs button on a monitor card to open the logs panel.
-
Shows the last 50 check logs for that monitor.
-
Each log entry displays:
- Status code badge: Green for 2xx responses, red for others.
- Response time: In milliseconds.
- Timestamp: Formatted as
MMM D, HH:mm:ss(e.g.,Jan 15, 14:32:07). - Error message: Displayed if the check failed (e.g., timeout, status mismatch).
-
Shows “No logs yet” if the monitor has never run.
Log Retention by Plan
Section titled “Log Retention by Plan”| Plan | Log Retention |
|---|---|
| Free | 7 days |
| Pro | 30 days |
| Team | 90 days |
Logs older than the retention window are automatically deleted.
Multi-Region Monitoring
Section titled “Multi-Region Monitoring”Every monitor is checked from three global regions simultaneously:
| Region | Location |
|---|---|
us-east | United States — East |
eu-west | Europe — West |
asia-pacific | Asia Pacific |
PingRoot uses 2-of-3 majority consensus to determine the final status — a single region reporting a failure does not trigger an alert. This eliminates false positives caused by regional network issues.
Timeouts and Failures
Section titled “Timeouts and Failures”- Requests timeout after 30 seconds — design your health endpoints to respond faster.
- A check fails if the response status code doesn’t match what you configured, or if the request times out.
| Failure Type | Error Message |
|---|---|
| Status code mismatch | "Expected {x}, got {y}" |
| Request timeout | "Request timed out after 30 seconds" |
| Network error | DNS failure, connection refused, etc. |