Your vendor is up. Is your endpoint?

Yes. A provider’s status page may be green while your own URL fails because of an application error, account restriction or configuration issue. An uptime monitor requests your public HTTPS URL and checks its response time, expected status code or range, and optional text or JSON body rules. This can surface a failing response independently of vendor reports; it does not identify the cause or verify a complete login or checkout.

Use vendor monitoring to follow incidents a third-party provider reports. Use uptime monitoring to check whether your own public HTTPS website or API returns the response you expect. Use a heartbeat to detect a cron job, backup or sync that stops checking in after successful work. You can combine them in one Statusfield workspace and route their alerts to the people responsible.

Yes. These are synthetic HTTP checks: Statusfield makes scheduled requests to publicly reachable HTTPS URLs and evaluates status codes, response time and optional text or JSON body rules. Browser tests and multi-step user journeys are not included.

Publicly reachable HTTPS websites and API endpoints. Set the request method, expected status code or range, response-time threshold and optional text or JSON body checks. Private-network endpoints are not reachable through these external checks.

Add a text or JSON response-body rule for the content you expect. A failed body check marks the check as an outage even if the status code matches. Choose a response that represents the condition you need to monitor, such as a health endpoint’s result; this does not validate every business operation behind the API.

No. Statusfield checks one endpoint against your configured response rules, including optional text or JSON assertions. It does not run a browser through a multi-step login or checkout.

Yes. Set a slow-response threshold to classify checks as degraded, and a timeout for an outage. Choose notification rules for each status. Response times stay in the check history so you can investigate changes.

Configure notification rules and destinations for the monitor, including recovery updates. Available channels and destination limits depend on your plan. Detection and delivery timing depend on your setup.

Each selected check location uses one monitor unit. Checking the same URL from three locations uses three units. SSL certificate and domain expiry checks are separate monitors and each uses its own unit.

Pro is our recommendation for small engineering and IT teams coordinating checks, on-call alerts and incident reviews. At $60/month, it combines 40 monitor units, 10 alert destinations and 4 workspace seats with PagerDuty routing, API and MCP access, reports and priority support. Share monitoring responsibility, send relevant changes to chat or on-call, and bring recorded history into your reviews. Reports require at least 30 days of workspace monitoring history. Basic covers a small email-only setup; Starter adds chat and API/MCP access. Team expands capacity to 90 units and 8 seats.