Post-incident wrap-up #22
Team Fortress 2
The most recent tracked incident was a positive warning alert triggered by sustained conditions. Across the visible window, the game added 290 reviews, the current 1-hour directional delta sits at 117, and the incident peak reached 117 in 1 hour. 1 earlier incident have already resolved.
Incident opened Mar 21, 2026, 1:43 PM and resolved Mar 21, 2026, 2:57 PM.
Peak tier reached: WARNING.
Reported score change during incident window: 0.0%.
Estimated time to peak: -61 m.
Estimated time to resolve: 1 h 14 m.
Before / after
Window from Mar 21, 2026, 2:33 AM to Mar 22, 2026, 2:03 AM.
Score before
91.0%
Score now
91.0%
Change
0.0%
Reviews added
290
Peak velocity
102/h
Composite impact score
low (18)Tier severity
+14
Review volume delta
+2
Peak velocity
+2
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 positive recovery pattern.
Incident FAQ
Auto-generated summary designed for quick sharing, operations handoffs, and SEO-friendly incident context.
What happened?
Team Fortress 2 entered a positive warning incident with 290 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 18/100 (LOW).
What are the most likely causes?
Positive Turnaround 100%
Is it resolving?
Resolved after 1 h 14 m with stabilized current sentiment state.
How far did sentiment move from normal?
Score moved by 0.0 points, from 91.0% to 91.0%. Peak velocity reached 102 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 19, 2026, 12:00 AM
Seasonal overlap: Steam Spring Sale 2026
Official Steam seasonal sale.
Mar 21, 2026, 12:42 PM
Peak pressure window
Peak tier reached WARNING.
Mar 21, 2026, 1:43 PM
Incident opened
Model opened a positive warning incident via sustained trigger logic.
Mar 21, 2026, 2:30 PM
Baseline divergence
1h direction velocity ran at 24.58x slot baseline.
Mar 21, 2026, 2:57 PM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Mar 21, 2026, 8:00 PM
Likely cause: Positive Turnaround
Sustained positive recovery pattern. (alerts + classifier v2 migration backfill)
Recovery tracking
Forecast ETA to normalize sentiment: Now (HIGH confidence)
Velocity is already within the stabilization band, so sentiment appears normalized.
Time to peak
-61 m
Time to resolve
1 h 14 m
Score at start
91.0%
Score at peak
91.0%
Uplift
0.0 pt
Recovered +24 h
0.0 pt
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 21, 2026, 1:43 PM
Incident opened at warning severity
Mar 21, 2026, 1:43 PM
Trigger: sustained
Peaked at warning severity
Mar 21, 2026, 2:06 PM
Resolved
Mar 21, 2026, 2:57 PM