Current stage, not just “running”
Your script reports meaningful stages, so you can see the last progress marker it actually reached.
Built for engineers and operators running scheduled or long-running unattended jobs. Unlike a simple heartbeat check, PingStep tracks the named stage your job reached, so lost visibility is always clear without you checking logs or guessing.
Monitor a jobSend a few small lifecycle events. PingStep never collects raw logs or your job's data — they stay wherever they already are.
Your script reports meaningful stages, so you can see the last progress marker it actually reached.
When updates stop, PingStep marks the run stale. It does not pretend that silence means healthy.
Send lifecycle events over HTTPS. PingStep does not need raw logs, payloads, SQL, credentials, or customer data.
Give it a simple, non-sensitive name and choose how often it normally reports an update.
Your script sends a start event, useful stages as it works, and a clear success or failure at the end.
Open PingStep to see the last reported stage. If updates stop, it becomes stale.
Start free, then pay only for the capacity you use.
US$0
1 job · 100 runs / 30 days
Use PingStep on a real job and see if it helps.
Start freeUS$19 / month
10 jobs · 10,000 runs / 30 days
Dependable visibility for one engineer or a small team.
Choose ProUS$49 / month
50 jobs · 50,000 runs / 30 days
For higher-volume recurring jobs.
Choose ScalePingStep reports what it has received. It does not guess whether a silent job is healthy.
Recent updates are arriving. The last reported stage is shown.
Updates stopped past the time you set. The job may still be running, but PingStep cannot confirm it.
The run has been active longer than expected. Late can happen alongside Running or Stale — it is a separate signal, not a replacement for either.
Your script explicitly sent a successful completion event.
Your script explicitly sent a failed completion event. It is never shown as complete.
PingStep stores your account email, job names, lifecycle events, timestamps, and token hashes so it can show a run’s status.
It does not collect raw logs, command output, SQL, credentials, or the files your job processes. Read the privacy details.