Website monitoring

Know when a public service stops behaving as expected.

Define a dependable HTTP check, retain the evidence behind every result, and follow failures through incident recovery from one operational workspace.

Start monitoring Read the documentation

Website monitorIllustrative setup

Public URL https://service.example.test/health

Method GETInterval 5 minutes

Expected status 200

Define healthy

Set the interval, method, expected status, and eligible content rules.

Retain every result

Review status context and response timing within plan-aware history.

Connect the incident

A failed check opens the record; a healthy result closes it.

Read the trend

Compare uptime, checks, failures, incidents, and response time.

01Monitor configuration

Define healthy on your terms.

Start with a public URL and a plan-aware interval. Add an HTTP method, expected status, alert contacts, and—when entitled—headers, a request body, and content rules.

GET, POST, PUT, PATCH, DELETE, and HEAD
Expected status and response-content validation
Workspace-scoped alert contacts

Monitor configurationPingBeacons

GEThttps://service.example.test/health

Check interval5 minutes

Expected status200 OK

Response must containok

Alert contactsOperations

Latest check200 OK · 184 msHealthy

02Check evidence

See every check in context.

Successful and failed checks retain response timing and status context. The monitor view connects the latest state with the history that produced it.

Check historyPingBeacons

14:08:02200 OK184 ms

14:03:02200 OK206 ms

13:58:01503412 ms

03Failure and recovery

Move from failed request to clear incident.

A failed check creates monitor-linked context. Notification preferences route the event, while the next healthy result resolves the active incident and preserves its duration.

Incident lifecyclePingBeacons

14:02Healthy request

14:04Failed check

14:04Incident opened

14:05Notification sent

14:08Recovery recorded

04Operational analysis

Understand performance beyond the latest check.

Reporting brings uptime, total checks, failures, incidents, response trends, status strips, and calendar context into one plan-aware range.

Monitoring reportPingBeacons

WeekMonthYearCustom

Uptime99.94%Checks8,912Failed7Incidents2

05Planned and public

Separate planned work, then communicate service health.

Maintenance windows can suppress ordinary checks for selected monitors. Public status pages can represent selected components, safe incidents, and maintenance state.

Public statusPingBeacons

Example Operations

All systems operationalUpdated moments ago

WebsiteOperational

Public APIOperational

Scheduled jobsOperational

SSL certificateOperational

API maintenance · Tomorrow, 22:00 UTC

Start with PingBeacons

Monitor the services your customers depend on.

Create a public HTTP check, define the response you expect, and keep the operational record when behavior changes.

Start monitoring Explore features