Website Uptime Checker — Status & Response Times
Check many URLs for uptime, HTTP status, and response time — with optional expected-status and keyword checks. Fails the run when a site is down so scheduled alerts fire. No auth.
Website Uptime Checker — Status & Response Times returns 9 documented output fields, including url, up, state, httpStatus and responseTimeMs. Every field carries a declared type, a written description and an example value. 32 runs are recorded on Apify.
- 9
- Output fields
- 7
- Inputs
- 32
- Runs
- 2026-10-15
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| url | stringnull | The URL this row describes. | https://example.com/pricing |
| up | booleannull | Whether the service responded successfully. | true |
| state | stringnull | State, province or region name. | active |
| httpStatus | integernull | HTTP status code returned by the request. | 200 |
| responseTimeMs | integernull | Time the request took, in milliseconds. | 0 |
| finalUrl | stringnull | URL of the final response after any redirects. | https://example.com/products/widget |
| contentType | stringnull | Content type of the response. | application/json |
| sizeBytes | integernull | Size in bytes. | 0 |
| checkedAt | stringnull | ISO 8601 timestamp of the most recent check. | 2026-10-16T09:12:44.000Z |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"url": "https://example.com/pricing",
"up": true,
"state": "active",
"httpStatus": 200,
"responseTimeMs": 0,
"finalUrl": "https://example.com/products/widget",
"contentType": "application/json",
"sizeBytes": 0
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| urls | arrayrequired | URLs to check. |
| expectStatus | integeroptional | Flag down if the status differs (e.g. 200). |
| expectText | stringoptional | Flag down if the page body doesn't contain this string. |
| failOnDown | booleanoptional | On: the run FAILs when any URL is down, so a Schedule's failure alert fires. |
| timeoutMs | integeroptional | Per-URL timeout. |
| useProxy | booleanoptional | For sites that block datacenter IPs. |
| maxItems | integeroptional | Hard cap. |
04 — run
Run Website Uptime Checker on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
9 of 9 fields described
- What does Website Uptime Checker — Status & Response Times return?
- It returns 9 documented output fields: url, up, state, httpStatus, responseTimeMs, finalUrl, contentType, sizeBytes and checkedAt. Each field declares its type, a description of what it holds, and an example value.
- What input does Website Uptime Checker — Status & Response Times require?
- urls is required. A further 6 inputs are optional. The full input schema, with types and defaults, is below.
- Does Website Uptime Checker — Status & Response Times need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Website Uptime Checker — Status & Response Times?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.