1. Extract
The generator reads the current detector source and extracts its check interval and status multipliers.
60sdetector check interval
1.5xlate threshold multiplier
2xdown threshold multiplier
Detection timing by expected heartbeat interval
Each range covers all 60 whole-second offsets between a stored heartbeat and the detector’s recurring check. Threshold comparisons are strict, so a check exactly on the threshold does not transition state.
| Expected heartbeat | Late threshold | Late observed range | Late p95 | Down threshold | Down observed range | Down p95 |
|---|---|---|---|---|---|---|
| 1 min | 1.5 min | 1.5166666666666666 min to 2.5 min | 2.45 min | 2 min | 2.0166666666666666 min to 3 min | 2.95 min |
| 5 min | 7.5 min | 7.516666666666667 min to 8.5 min | 8.45 min | 10 min | 10.016666666666667 min to 11 min | 10.95 min |
| 10 min | 15 min | 15.016666666666667 min to 16 min | 15.95 min | 20 min | 20.016666666666666 min to 21 min | 20.95 min |
| 30 min | 45 min | 45.016666666666666 min to 46 min | 45.95 min | 60 min | 60.016666666666666 min to 61 min | 60.95 min |
| 60 min | 90 min | 90.01666666666667 min to 91 min | 90.95 min | 120 min | 120.01666666666667 min to 121 min | 120.95 min |
Implementation rule
late when elapsed > expected × 1.5; down when elapsed > expected × 2; evaluation every 60s
How the table was produced
2. Enumerate
It evaluates every whole-second scheduler phase from 1 through 60 seconds for each configured example interval.
3. Record
It records earliest, median, p95 and latest transition time for late and down states.
4. Fingerprint
The output stores the repository commit, source path, dirty state and SHA-256 of the tested implementation.
Interpretation and limits
This is implementation evidence, not a production response-time promise. Actual notification time includes more systems than the detector threshold.
Excluded from the model
- This table is derived from a source-code snapshot and is not a production latency measurement or service-level agreement.
- Whole-second scheduler phases are sampled; sub-second phase offsets are not enumerated.
- Network transit, database latency, process stalls, alert rendering and delivery-channel latency are excluded.
- The model starts from the last stored heartbeat timestamp and assumes the detector continues to run every configured check interval.
- The results do not measure third-party workflow reliability or customer outcomes.
Download the evidence
The structured dataset, row-level CSV, schema, reproduction note and integrity hashes contain no customer or workflow records. The current page may be regenerated; the dated version is retained as the immutable citation target.
Dataset JSONMethod, source fingerprint and rowsTiming CSVOne record per heartbeat intervalJSON SchemaMachine-readable field contractManifestArtifact sizes and hashesSHA-256 checksumsIntegrity verificationReproduction noteExact local generator entrypoint
Suggested citation
Laybats, Victor. “Heartbeat monitoring detection envelope.” Datvero Research, IVRYN, 9 Aug. 2026. https://datvero.com/research/heartbeat-detection-envelope/2026-08-09T14-21-08-656Z/2026-08-09T14-21-08-656Z/index.html