Documentation (cron monitoring) — updown.io

Cited by

Facts read from this source

• Pulse monitoring definition Report an error

  “Pulse monitoring (also called "cron" monitoring) is a special type of monitoring where your service calls updown.io regularly, instead of the opposite.”

• Pulse interval range Report an error

  “A time interval before notification. It can be any duration between 15 seconds and 1 month + a few days.”

• Pulse monthly tasks Report an error

  “After each pulse, updown will compute the alert time to be next month the same day instead of using a fixed number of day.”

• Pulse API creation Report an error

  “Pulse checks can also be created from the API using the type=pulse parameter.”

• Pulse endpoint security Report an error

  “Be careful the private pulse endpoint URL is ONLY accessible from the API after creation (or update). Otherwise it's redacted from any GET endpoint for security.”

• Pulse http methods Report an error

  “You can then query this URL (using GET, HEAD or POST) in your periodic tasks, at the end of your scripts, etc..”

• Pulse request body Report an error

  “You can optionally send a body with your request (use a POST request in that case). The body will be stored and can be displayed when you investigate downtimes.”

• Pulse string match Report an error

  “SINCE APRIL 2026You can also specify a string to match in the pulse body (in the "contains" field or via the string_match API parameter). When configured, updown will check the body of each received pulse for that string (case-insensitive).”

• Pulse third party client Report an error

  “Here is also a third-party client to wrap a command execution and send a pulse at the end (written in go): https://github.com/chialab/updownio-pulse”

• Pulse endpoint dns Report an error

  “the pulse endpoint (pulse.updown.io) is backed by at least 2 servers at the DNS level”

• Pulse credit cost Report an error

  “Each pulse request will cost 1 credit Each missed pulse (configured interval) will also cost 1 credit”

• Pulse daily example Report an error

  “That's at most 365 credits / year for this daily pulse example, or about 0.009€ / year maximum ! (even less if you buy credits in larger packs)”

• Pulse minute example Report an error

  “For a more expensive pulse check expected every 1 minute, it would be ~1.10€ / month maximum (see pricing table)”

• Pulse disabled check cost Report an error

  “If you disable a pulse check but keep sending the pulse requests, they'll still be processed, recorded and still cost you credits.”

• Pulse deleted check cost Report an error

  “If you delete a pulse check but keep sending the pulse requests, they'll return a 404 error and will not cost you credits.”

• Made in paris Report an error

  “Made with in Paris, France since 2012”

Scores citing this record

• The Agency Developer Pricing transparency
• The Customer Support Lead Pricing transparency
• The E-Commerce Operations Manager Pricing transparency
• The SaaS Platform Engineer Checks, locations & failure confirmation
• The SaaS Platform Engineer Pricing transparency
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Pricing transparency
• The Skeptic Pricing transparency