Website Uptime Monitor: What Went Down Since Last Run avatar

Website Uptime Monitor: What Went Down Since Last Run

Pricing

from $0.75 / 1,000 results

Go to Apify Store
Website Uptime Monitor: What Went Down Since Last Run

Website Uptime Monitor: What Went Down Since Last Run

Checks your sites like a Website Uptime Monitor should: status, response time, SSL days left and whether the page still shows your text, then flags what went down or recovered since the last run. Schedule it and export to CSV.

Pricing

from $0.75 / 1,000 results

Rating

0.0

(0)

Developer

ANVIL Tools

ANVIL Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Website Uptime Monitor - Check a list of sites on a schedule and see right away which ones went down, came back, lost their text or have an SSL certificate about to expire.

What does Website Uptime Monitor do?

Every row says what changed since the last run (went_down, recovered, status_changed, same) and shows SSL days left plus a 'page must contain this text' check per URL - the leading uptime checkers only return a status snapshot and ssl true/false.

  • Went down / recovered / status changed vs the last run, per URL
  • SSL expiry date, days left, issuer and an early warning
  • Per-URL 'must contain' text check (url | text)
  • Status, response time, redirects, page title, server
  • Run never fails on a dead site - it reports why (timeout, DNS, SSL)

Who uses Website Uptime Monitor, and for what

  • Agencies - see every morning which client site went down or lost its checkout button
  • Shop owners - get warned two weeks before an SSL certificate expires
  • Developers - run a post-deploy check that pages still show the right text
  • Indie hackers - a cheap scheduled stand-in for Datadog synthetic checks

Why this Website Uptime Monitor?

Low tools return a bare status code once, so the user still has to compare runs and track certificate dates by hand. This Website Uptime Monitor checks every run and tells you plainly when a page could not be read, instead of returning empty or wrong rows.

Data you get from Website Uptime Monitor

Every result is one flat row with these fields (values from a real run):

FieldExample
urlhttps://example.com
checkedAt2026-10-22T10:53:34+00:00
uptrue
healthytrue
healthIssues[]
expectedTextExample Domain
statusCode200
responseTimeMs42
finalUrlhttps://example.com
redirectedfalse
redirectCount0
pageTitleExample Domain
containsExpectedTexttrue
sslValidtrue
sslExpiresAt2026-12-25T22:56:35+00:00
sslDaysLeft64
sslIssuerSSL Corporation
servercloudflare
contentTypetext/html; charset=utf-8
contentLength577
changeSinceLastRunsame
previousStatusCode200
errornull
errorTypenull

How to use Website Uptime Monitor

  1. Press Start - the form already holds an example that works.
  2. Put in your own input (see the fields on the Input tab).
  3. Run it once, or put it on an Apify Schedule to get fresh rows every day.
  4. Download the results as JSON, CSV or Excel, or send them to Google Sheets, Zapier, Make, the Apify API or an AI agent (Apify MCP server).

Input example

{
"urls": [
"https://example.com | Example Domain",
"https://www.python.org | Python"
],
"mustContain": "",
"sslWarnDays": 14,
"maxResponseTimeMs": 0,
"timeoutSec": 15,
"maxItems": 50
}

Output example (a real run)

[
{
"url": "https://example.com",
"checkedAt": "2026-10-22T10:53:34+00:00",
"up": true,
"healthy": true,
"healthIssues": [],
"expectedText": "Example Domain",
"statusCode": 200,
"responseTimeMs": 42,
"finalUrl": "https://example.com",
"redirected": false,
"redirectCount": 0,
"pageTitle": "Example Domain",
"containsExpectedText": true,
"sslValid": true,
"sslExpiresAt": "2026-12-25T22:56:35+00:00",
"sslDaysLeft": 64,
"sslIssuer": "SSL Corporation",
"server": "cloudflare",
"contentType": "text/html; charset=utf-8",
"contentLength": 577,
"changeSinceLastRun": "same",
"previousStatusCode": 200,
"error": null,
"errorType": null
},
{
"url": "https://www.python.org",
"checkedAt": "2026-10-22T10:53:35+00:00",
"up": true,
"healthy": true,
"healthIssues": [],
"expectedText": "Python",
"statusCode": 200,
"responseTimeMs": 17,
"finalUrl": "https://www.python.org",
"redirected": false,
"redirectCount": 0,
"pageTitle": "Welcome to Python.org",
"containsExpectedText": true,
"sslValid": true,
"sslExpiresAt": "2027-02-14T13:03:45+00:00",
"sslDaysLeft": 115,
"sslIssuer": "GlobalSign nv-sa",
"server": "nginx",
"contentType": "text/html; charset=utf-8",
"contentLength": 52829,
"changeSinceLastRun": "same",
"previousStatusCode": 200,
"error": null,
"errorType": null
}
]

One flat row per result.

How much does Website Uptime Monitor cost?

You pay only per result (pay per event) - no monthly fee, no minimum, and the price per result is lower on Apify's Bronze, Silver and Gold plans. The exact price is on the Pricing tab. Apify's free plan credit is enough to try it on real input.

You wantWhat you pay for
A quick test with the examplea few results
A daily scheduled runonly the rows that run returns
A big one-off exportthe results delivered - set a maximum in the input

Also searched as

  • uptime checker
  • ssl expiry checker
  • website down checker
  • synthetic monitoring
  • website status checker

FAQ

Does Website Uptime Monitor need a login, cookies or an API key? No. It reads public pages only.

Can I run Website Uptime Monitor on a schedule? Yes - with Apify Schedules; each run returns fresh rows.

Can I call it from Python, JavaScript or an AI agent? Yes - through the Apify API, the Apify client libraries or the Apify MCP server.

Is it legal? It collects only data anyone can see without logging in. You are responsible for using it within the source site's terms and data protection law (GDPR, CCPA).

What if the site blocks a request? The run retries from a fresh connection and, if it still cannot read the page, stops with a clear message - never with made-up rows.

Do I need proxies? No setup needed - Website Uptime Monitor uses Apify Proxy by default where the site needs it.

Troubleshooting

  • No results: check the input (a public URL or a search term that returns results in a normal browser), then try the example input once.
  • Fewer results than expected: raise the maximum in the input; some sites show only a part of their data without logging in, and Website Uptime Monitor never logs in.
  • The run stopped with a message: the message says what the site answered; run it again later or with fewer items.

Your feedback

Missing a field, found a bug, or need another site? Open an issue on the Issues tab - issues are answered and fixed. If Website Uptime Monitor saved you time, a short review on this page helps others find it.

Data source: example.com

More tools from this developer