Skip to main content

GUIDE · UPTIME MONITORING

Know whether customers can reach your service.

Uptime monitoring requests a public URL on a schedule, records its response, and turns the results into a status page you can share.

What does it do?

Soroltech sends an HTTP GET request to your endpoint. Responses from 200 through 399 are marked operational; errors, timeouts, and other status codes are marked unavailable. Each check records response time and the HTTP status code.

Good uses

Websites and stores

Monitor a public page that represents the experience visitors depend on.

APIs and integrations

Point the monitor at a lightweight health endpoint such as /health that returns success only when essential dependencies work.

How to use it

Choose a meaningful endpoint

Use a public HTTPS URL. A dedicated health endpoint is usually clearer than a heavy homepage.

Add and name the monitor

Enter the URL in Uptime and use a customer-friendly service name.

Share and interpret

Open the public status page, share its address, and use response history to spot recurring slowdowns or outages.

Embed status on your own site

Pro and Max monitors include an Embed button. It copies a small asynchronous script that renders the current service state wherever you paste it. Use data-theme="light" for a light widget, data-lang="fi" for Finnish, or data-target="element-id" to render inside a specific element. Sites with a strict Content Security Policy must allow the Soroltech domain in both script-src and connect-src.

What it is not

A successful check confirms that the selected public endpoint responded. It does not prove every feature, region, or downstream dependency is healthy. Choose endpoints that reflect what matters to users.