All features
Intelligence

Latency and availability anomaly detection without thresholds

Thresholds are guesses that go stale. PulseTrace learns what normal looks like for each monitor and signal — latency by region, availability, flapping — and opens an anomaly episode when a value steps outside its own baseline.

Baselines are per monitor and per signal, so a chatty endpoint's normal never hides a regression on a quiet one. An anomaly is tracked as one episode from open to close, with its score and confidence, rather than a stream of point alerts; when it ends you get one recovery, not fifty.

Latency baselines are on Team; Pro adds availability and per-signal detection plus flapping detection, and sensitivity is adjustable per monitor for the cases where you know better than the model.

  • Per-signal baselines — latency, availability, flapping.
  • Episodes, not noise with score, confidence and severity.
  • Tunable sensitivity per monitor.
  • Incident rules can open incidents from anomalies.
latency · anomaly episode

How it works

  1. 1Enable anomaly detection on a monitor (on by default on Team+ for latency).
  2. 2The model learns a baseline from recent checks per region and signal.
  3. 3A sustained departure opens an episode, alerts your destinations and closes itself on recovery.

Plan availability

Latency baselines on Team and above · availability, per-signal and flapping detection on Pro and above.

Compare plans →

Monitor types that use it

Questions about anomaly detection

How long until a baseline exists?
A few hundred checks per region — a day at 1-minute checks, a couple of hours at 15 seconds. Until then the monitor reports but doesn't flag anomalies.
Can I turn it off for a noisy endpoint?
Per monitor, yes — or lower the sensitivity so only large departures open an episode.