Incident #61
The most recent tracked incident was a negative warning alert triggered by sustained conditions. Across the visible window, the game added 292 reviews, the current 1-hour directional delta sits at 53, and the incident peak reached 52 in 1 hour. 1 earlier incident have already resolved.
Alert explainability
This negative pressure alert is currently warning because the last-hour direction delta reached 53 reviews (53 over 6h), with 31.9x baseline intensity, evaluated under sustained conditions and stale references.
Direction: Negative
Current tier: WARNING
Peak tier: WARNING
Model: V2
Trigger: sustained
Freshness: stale
1h direction delta: 53
6h direction delta: 53
Baseline multiple: 31.9x
Score change (6h): 0.0%
Open since: Apr 12, 2026, 7:27 PM
Resolved at: Apr 12, 2026, 8:09 PM
Window end: Apr 12, 2026, 7:46 PM
Confidence score
HIGHBefore / after
Window from Apr 12, 2026, 1:24 PM to Apr 13, 2026, 8:08 AM.
Score before
71.0%
Score now
71.0%
Change
0.0%
Reviews added
292
Peak velocity
28/h
Counterfactual baseline
Observed velocity is clearly above expected baseline, indicating sustained pressure.
Velocity 1h
Observed 27.5
Expected 16.4
Delta +11.0 (1.67x)
Score sensitivity
Observed 71.0%
Expected 71.0%
Delta 0.0 pt
Negative share
Observed 28.7%
Expected 28.7%
Delta -0.0 pp
Composite impact score
low (17)Tier severity
+14
Review volume delta
+2
Peak velocity
+1
Score movement
+0
Resolution duration
+0
Likely cause ranking
Probabilities are heuristic and derived from approved tag assignments, classifier confidence, and editorial overrides.
100%
Sustained negative flow indicates prolonged audience dissatisfaction.
Incident FAQ
Auto-generated summary designed for quick sharing, operations handoffs, and SEO-friendly incident context.
What happened?
Gray Zone Warfare entered a negative warning incident with 292 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 17/100 (LOW).
What are the most likely causes?
Patch Backlash 100%
Is it resolving?
Resolved after 42 m with stabilized current sentiment state.
How far did sentiment move from normal?
Score moved by 0.0 points, from 71.0% to 71.0%. Peak velocity reached 28 reviews/hour.
Does it resemble a broader cluster?
No related incidents were detected across connected titles in the current comparison window.
External trigger timeline
Correlates model milestones with seasonal overlap and cause evidence to explain likely trigger context.
Apr 9, 2026, 12:00 AM
Seasonal overlap: Steam Hidden Object Fest 2026
Official Steam themed fest.
Apr 12, 2026, 1:24 PM
Peak pressure window
Peak tier reached WARNING.
Apr 12, 2026, 7:27 PM
Incident opened
Model opened a negative warning incident via sustained trigger logic.
Apr 12, 2026, 7:27 PM
Likely cause: Patch Backlash
Sustained negative flow indicates prolonged audience dissatisfaction. (alerts.trigger_type)
Apr 12, 2026, 8:08 PM
Baseline divergence
1h direction velocity ran at 31.93x slot baseline.
Apr 12, 2026, 8:09 PM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Anomaly explanation tree
Structured reason tree showing what opened the alert, what confirmed it, which factors reduced confidence, and how likely causes were assigned.
1) Opened by
Burst velocity anomaly
Baseline multiple 31.93x exceeded opening threshold.
Directional pressure (1h)
Direction delta 53 and share 0.29 informed open decision.
2) Confirmed by
Tier progression
Current tier: warning, peak: warning, trigger: sustained.
Score trend confirmation
6h score change at 0%.
3) Confidence dampeners
Freshness gate
Freshness state is stale.
Direction coherence
Negative coherence maintained; no dampener from direction flip.
4) Tag assignment outcomes
Patch Backlash
64% confidence from 2 evidence items and 1 rules.
Evidence provenance
Audit view of the concrete signals, rule identifiers, and evidence sources that contributed to this incident interpretation.
Core signals
Direction delta 1h
53
alerts.metadata.current_metrics.direction_delta_1h
Short-window directional review acceleration used in live alert scoring.
Direction share 1h
0.29
alerts.metadata.current_metrics.direction_share_1h
Directional concentration used to distinguish coordinated or concentrated pressure.
Baseline ratio 1h
31.93
alerts.metadata.current_metrics.slot_baseline_ratio_1h
Observed velocity relative to expected slot baseline for this game/time bucket.
Score change 6h
0
alerts.metadata.current_metrics.score_change_percent_6h
Medium-window score movement used for sustained confirmation.
Applied rules
Cause evidence trail
Patch Backlash
SUSTAINED
alerts.trigger_type
Sustained negative flow indicates prolonged audience dissatisfaction.
Patch Backlash
false
seasonal_events
No PATCH event overlap detected.
Why this moved
TRIGGER
Prolonged negative sentiment — 53 biased reviews over 6 hours — 31.9x the expected rate — opened a warning alert.
SEVERITY
The incident peaked at warning tier within the first hour. It ran for 1h total.
RECOVERY
Score has not meaningfully changed since resolution — sentiment appears stable.
CONTEXT
The sustained pattern suggests broad organic audience discontent: the signal built steadily over hours rather than spiking in a single burst.
Recovery tracking
Forecast ETA to normalize sentiment: Now (MEDIUM confidence)
Velocity is already within the stabilization band, so sentiment appears normalized.
Time to peak
-363 m
Time to resolve
42 m
Score at start
71.0%
Score at worst
71.0%
Score drop
0.0 pt
Recovered +24 h
n/a
Recovered +7 d
n/a
Recovered +30 d
n/a
Sentiment stabilised
Yes
Incident velocity window
Alert timeline
Escalation history across active and resolved incidents for this game.
Started Apr 12, 2026, 7:27 PM
Opened at warning severity
Apr 12, 2026, 7:26 PM
Trigger: sustained
Peaked at warning severity
Apr 12, 2026, 7:46 PM
Resolved from warning severity
Apr 12, 2026, 8:08 PM
Portfolio blast radius
Isolated
No meaningful spread to other related titles right now.
Related active
0
Resolved (14d)
0
Impacted titles
0
Global active
0
No related active or recently resolved incidents were found.
