Post-incident wrap-up #38
Dota 2
The most recent tracked incident was a positive warning alert triggered by sustained conditions. Across the visible window, the game added 1,130 reviews, the current 1-hour directional delta sits at 7, and the incident peak reached 66 in 1 hour. 1 earlier incident have already resolved.
Incident opened Mar 27, 2026, 10:20 PM and resolved Mar 28, 2026, 6:26 AM.
Peak tier reached: WARNING.
Reported score change during incident window: 0.0%.
Estimated time to peak: -3694 m.
Estimated time to resolve: 8 h 6 m.
Before / after
Window from Mar 27, 2026, 11:14 AM to Mar 28, 2026, 9:18 AM.
Score before
81.0%
Score now
81.0%
Change
0.0%
Reviews added
1,130
Peak velocity
363/h
Composite impact score
low (32)Tier severity
+14
Review volume delta
+9
Peak velocity
+8
Score movement
+0
Resolution duration
+1
Likely cause ranking
Probabilities are heuristic and derived from approved tag assignments, classifier confidence, and editorial overrides.
100%
Sustained positive flow indicates sentiment recovery.
Incident FAQ
Auto-generated summary designed for quick sharing, operations handoffs, and SEO-friendly incident context.
What happened?
Dota 2 entered a positive warning incident with 1,130 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 32/100 (LOW).
What are the most likely causes?
Positive Turnaround 100%
Is it resolving?
Resolved after 8 h 6 m with stabilized current sentiment state.
How far did sentiment move from normal?
Score moved by 0.0 points, from 81.0% to 81.0%. Peak velocity reached 363 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.
Mar 25, 2026, 8:46 AM
Peak pressure window
Peak tier reached WARNING.
Mar 25, 2026, 12:48 PM
Baseline divergence
1h direction velocity ran at 0.74x slot baseline.
Mar 27, 2026, 10:20 PM
Incident opened
Model opened a positive warning incident via sustained trigger logic.
Mar 27, 2026, 10:20 PM
Likely cause: Positive Turnaround
Sustained positive flow indicates sentiment recovery. (alerts.trigger_type)
Mar 28, 2026, 6:26 AM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Recovery tracking
Forecast ETA to normalize sentiment: Now (HIGH confidence)
Velocity is already within the stabilization band, so sentiment appears normalized.
Time to peak
-3694 m
Time to resolve
8 h 6 m
Score at start
81.0%
Score at peak
81.0%
Uplift
0.0 pt
Recovered +24 h
n/a
Recovered +7 d
n/a
Recovered +30 d
n/a
Sentiment stabilised
Yes
Alert timeline
Escalation history across active and resolved incidents for this game.
Started Mar 27, 2026, 10:20 PM
Peaked at warning severity
Mar 25, 2026, 10:48 AM
Incident opened at warning severity
Mar 27, 2026, 10:20 PM
Trigger: sustained
Resolved
Mar 28, 2026, 6:26 AM