Features page (cron job monitoring) — Hyperping

Cited by

Facts read from this source

• Healthcheck description Report an error

  “Heartbeat monitoring for backups, reports and every scheduled task. Each job pings its own URL when it finishes, and your team is alerted when a run is missed.”

• Free included Report an error

  “Included on every plan, Free too. No credit card required.”

• Ping methods Report an error

  “A HEAD, GET or POST request from anything that speaks HTTP.”

• Start end ping Report an error

  “Ping /start when the job begins and the URL when it ends: every run’s duration is logged, and a run that never ends misses its deadline.”

• Simple mode Report an error

  “Expect a ping every so many minutes, hours or days, from 1 minute up. The clock restarts at each ping, which suits workers and syncs that run in a loop.”

• Cron mode Report an error

  “Paste the job’s five-field expression and pick its timezone. Each run is expected when cron would start it, weekends and daylight saving changes included.”

• Grace period Report an error

  “How long to wait after the expected time before alerting, 10 minutes unless you change it.”

• Alert once per missed run Report an error

  “it stays down until the job pings again: one alert per missed run, not one per minute.”

• Alert channels Report an error

  “Email and SMS reach every member of the project, and Slack, Discord and Telegram the channels you connected. Send it to PagerDuty or Opsgenie to page whoever is on call there.”

• Pagerduty auto close Report an error

  “The next ping resolves the incident and sends a recovery on the same channels. PagerDuty and Opsgenie alerts close on their own.”

• Status page healthchecks Report an error

  “Add a healthcheck to a status page next to your websites and APIs. Customers see the import, the sync or the report as one more service, up or down, with its uptime.”

• Ping logging Report an error

  “Each ping records its time, IP address, method and user agent, and the duration of the run when it started with /start. A 24-hour chart shows the runs hour by hour.”

• Ping history limit Report an error

  “Oct 06 02:48:21 · OK · 4m 09s last 20 pings kept”

• Uptime reporting Report an error

  “Healthcheck uptime is computed from its outages, over 30 days by default, exported to CSV and included in the weekly report next to your monitors.”

• Healthchecks API Report an error

  “POST name, a cron expression and its timezone, or period_value and period_type, plus the grace period. The response carries the ping URL to hand to your job.”

• Terraform Report an error

  “The hyperping_healthcheck resource keeps every job’s healthcheck next to the infrastructure that runs it, and outputs its ping URL as a sensitive value.”

• Mcp Report an error

  “The MCP server lists your healthchecks with their state, last ping and next deadline, so Claude, Cursor or another agent can answer “did last night’s jobs run?”.”

• Uptime monitoring regions Report an error

  “Uptime monitors call your websites and APIs as often as every 30 seconds, from up to 17 regions.”

• Essentials seats Report an error

  “healthchecks count toward the plan’s monitors, nothing is billed per job, and Essentials includes 3 seats.”

• 500 jobs Report an error

  “500 jobs $299 Business, $249 billed yearly”

• Plan monitor counts Report an error

  “Each healthcheck counts as one of the plan’s monitors: 20 on Free, 50 on Essentials, 250 on Pro and 1,000 on Business, shared with your uptime checks.”

• Grace period min Report an error

  “It starts at 1 minute and defaults to 10 minutes in the dashboard.”

• Grace behavior Report an error

  “The run is due and hasn’t pinged yet. The healthcheck stays up and nothing is sent until the grace period runs out, so a job that runs a few minutes long stays quiet.”

• Deadline from schedule Report an error

  “In cron mode the deadline follows the expression, not the last ping. A backup that pings at 02:04 tonight is still expected at 02:00 tomorrow, with 30 minutes of grace.”

• Exit code not stored Report an error

  “Hyperping doesn’t store the job’s exit code or output, so keep your logs for the why.”

• Github actions disable note Report an error

  “GitHub disables scheduled workflows in public repositories after 60 days without activity, and a CI runner can stay queued.”

• Opsgenie shutdown Report an error

  “Opsgenie shuts down on April 5, 2027, heartbeats included.”

• Entity Report an error

  “Hyperping SAS 50 Avenue des Champs-Élysées 75008 Paris, France”

• Legal pages Report an error

  “Privacy policy Terms of service Security DPA GDPR & EU data SLA”

• Comparison checked date Report an error

  “Prices checked on October 8, 2026 on each vendor’s pricing page.”

4 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The Agency Developer Checks, locations & failure confirmation
• The Agency Developer Alerting, escalation & on-call
• The Agency Developer Uptime reports, data & the vendor's own reliability
• The Customer Support Lead Alerting, escalation & on-call
• The Customer Support Lead Uptime reports, data & the vendor's own reliability
• The E-Commerce Operations Manager Alerting, escalation & on-call
• The E-Commerce Operations Manager Uptime reports, data & the vendor's own reliability
• The SaaS Platform Engineer Checks, locations & failure confirmation
• The SaaS Platform Engineer Alerting, escalation & on-call
• The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Alerting, escalation & on-call
• The Information Security Officer Uptime reports, data & the vendor's own reliability
• The Skeptic Checks, locations & failure confirmation
• The Skeptic Uptime reports, data & the vendor's own reliability