Upstream results·2,807 series·Upstream results cached for up to 12 hours; refreshed on visits

BOOM

BOOM answers a different question from the general-purpose leaderboards: how do TSFMs behave on messy production monitoring data with spikes, heavy tails, and regime shifts? For observability workloads, this is the benchmark that actually looks like the job.

Page data loaded 10/27/2026

What this benchmark answers

How do models behave on observability telemetry instead of academic datasets?

Methodology

Models are ranked on real observability time series using CRPS for probabilistic quality and MASE for point accuracy, aggregated across production telemetry collected from real infrastructure workloads.

toto_2.0_2.5b ranks first with CRPS 0.35, followed by toto_2.0_1b (0.35) and toto_2.0_313m (0.35).

16 of 23 ranked entries in the model directory · Lower is better

Top 12 of 23 results. The full table is below.

Rankings

CRPS vs MASE

Directory model (filled)Not in directory (outline)

Full results

Model
10.349
20.349
30.351
40.363
50.375
60.377
70.382
80.392
9
moirai_2_small
0.427
100.428
110.436
120.442
130.447
140.451
150.455
16
timer
0.639
170.643
180.649
19
visionts
0.673
20
autoarima
0.736
21
seasonalnaive
1.00
22
autotheta
1.02
23
autoets
1.98

Why observability data is different

Production monitoring series have characteristics that academic benchmarks rarely capture: heavy-tailed distributions from traffic spikes, regime shifts when deployments change system behavior, irregular sampling from agent collection windows, and strong multivariate coupling between infrastructure metrics. BOOM uses 2,807 real series from Datadog across infrastructure, networking, database, security, and application domains to stress-test models on data that looks like what SRE teams actually see.

CRPS vs MASE in BOOM

CRPS (Continuous Ranked Probability Score) evaluates the full predictive distribution — it rewards models that produce well-calibrated uncertainty, not just sharp point estimates. MASE complements this with a scale-free point accuracy measure. If a model ranks well on CRPS but poorly on MASE, it is producing good uncertainty bands but inaccurate central forecasts; the reverse means sharp predictions with unreliable confidence intervals.

How to interpret it

  • —BOOM is the benchmark to prioritize when your inputs look like production telemetry.
  • —CRPS rewards calibrated uncertainty, not just sharp point estimates.
  • —Large ranking changes between BOOM and general-purpose benchmarks are a useful routing signal.

Frequently asked questions

What is the BOOM benchmark?
BOOM is a forecasting benchmark by Datadog that evaluates time series foundation models on 2,807 real observability time series from production infrastructure. It uses CRPS and MASE as primary and secondary metrics.
Why does BOOM rank models differently from FEV Bench?
BOOM uses production telemetry data with heavy tails, regime shifts, and irregular sampling — characteristics rarely found in academic datasets. Models optimized for clean series often struggle on this workload, leading to significant ranking differences.
What does CRPS measure?
CRPS (Continuous Ranked Probability Score) evaluates the full predictive distribution, rewarding models that produce calibrated uncertainty estimates. Lower CRPS is better.
Is BOOM relevant if I am not in observability?
If your data has similar characteristics to production telemetry — spiky, heavy-tailed, with regime changes — BOOM rankings can be more informative than general-purpose leaderboards even outside of observability use cases.

Related reading

Compare with other TSFM benchmarks

FEV Bench

How well does a model generalize to unseen real-world forecasting tasks?

GIFT-Eval

Which models stay strong across heterogeneous datasets and probabilistic settings?

Impermanent

Does model performance hold up as real time passes and the data distribution shifts?

ARFBench

Which multimodal models can reason about anomalies, timing, magnitude, and cross-series structure in production telemetry?

TIME

How do models behave across realistic tasks and different temporal patterns?

QuitoBench

Does a model remain strong across easy and difficult forecasting regimes?

Sources