Saved & scheduled checks

Any check can be saved with a name and its configuration — the target, the check type, and the regions to run it from. Once saved, you can re-run it whenever you like, without re-entering the same settings.

You can re-run a saved check from the UI, from the API with POST /api/checks/{id}/run, or from an MCP client with the run_saved_check tool.

A saved check can be turned into a scheduled check so it runs continuously in the background, rather than only when you trigger it. Scheduled checks are what power incident detection and status pages.

How many scheduled checks you can have, and how frequently they can run, depends on your plan: free allows 1 scheduled check with a minimum interval of 300 seconds, starter allows 25 checks at 300 seconds, team allows 100 checks at 60 seconds, and enterprise allows 1,000 checks at 30 seconds. See Plans & billing for the full comparison.

Every scheduled run is recorded so you can look back at how a target has behaved over time. How long that history is kept depends on your plan: 7 days on free, 30 days on starter, 90 days on team, and 365 days on enterprise.

To create a scheduled check from a saved check, call POST /api/checks/{id}/scheduled-check. To list your scheduled checks, call GET /api/scheduled-checks:

curl -s https://regioncheck.io/api/checks/{id}/scheduled-check \
  -H "Authorization: Bearer $REGIONCHECK_API_KEY" \
  -X POST -d '{"interval_seconds": 300}'

The MCP server exposes the same capability through the create_scheduled_check tool, so an agent can turn a saved check into ongoing monitoring directly.