Uptime monitors
Know when a public endpoint or connected service stops behaving normally.
Know when a public endpoint or connected service stops behaving normally.
What this feature is for
Uptime monitors sample public URLs and selected provider paths on the plan cadence. They capture availability and latency trends so a team can see the first regression. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
A stable URL, expected response behavior, and a cadence appropriate to the customer impact of failure.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Add the endpoint, set the assertion, run an initial sample, and watch the monitor after releases and provider changes.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
Each sample records response status, latency, timestamp, and the monitor state used for incident and alert decisions. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
Do not monitor a page that requires a fragile session unless the journey runner is the better tool. Investigate DNS, TLS, provider, and deploy evidence in that order.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Combine uptime with RUM for real-user impact and Alert delivery for notification. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.