Post-incident wrap-up #18
Slay the Spire 2
The most recent tracked incident was a negative warning alert triggered by sustained conditions. Across the visible window, the game added 6,865 reviews, the current 1-hour directional delta sits at 403, and the incident peak reached 403 in 1 hour. 1 earlier incident have already resolved.
Incident opened Mar 21, 2026, 8:22 AM and resolved Mar 21, 2026, 9:10 AM.
Peak tier reached: WARNING.
Reported score change during incident window: -2.5%.
Estimated time to peak: -61 m.
Estimated time to resolve: 48 m.
Before / after
Window from Mar 20, 2026, 8:30 PM to Mar 21, 2026, 8:12 PM.
Score before
81.0%
Score now
78.0%
Change
-3.0%
Reviews added
6,865
Peak velocity
496/h
Composite impact score
moderate (50)Tier severity
+14
Review volume delta
+20
Peak velocity
+11
Score movement
+5
Resolution duration
+0
Likely cause ranking
Probabilities are heuristic and derived from approved tag assignments, classifier confidence, and editorial overrides.
Incident FAQ
Auto-generated summary designed for quick sharing, operations handoffs, and SEO-friendly incident context.
What happened?
Slay the Spire 2 entered a negative warning incident with 6,865 additional reviews in the tracked window.
How severe was it?
Incident remained in warning severity without crossing critical threshold. Composite impact score is 50/100 (MODERATE).
What are the most likely causes?
Patch Backlash 100%
Is it resolving?
Resolved after 48 m with still elevated current sentiment state.
How far did sentiment move from normal?
Score moved by -3.0 points, from 81.0% to 78.0%. Peak velocity reached 496 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, 7:21 AM
Peak pressure window
Peak tier reached WARNING.
Mar 21, 2026, 8:22 AM
Incident opened
Model opened a negative warning incident via sustained trigger logic.
Mar 21, 2026, 9:09 AM
Baseline divergence
1h direction velocity ran at 5.04x slot baseline.
Mar 21, 2026, 9:10 AM
Incident resolved
Incident exited alert thresholds and moved to resolved state.
Mar 21, 2026, 8:00 PM
Likely cause: Patch Backlash
Sustained negative flow pattern. (alerts + classifier v2 migration backfill)
Recovery tracking
Forecast ETA to normalize sentiment: Now (HIGH confidence)
Post-incident behaviour is close to expected baseline levels.
Time to peak
-61 m
Time to resolve
48 m
Score at start
81.0%
Score at worst
79.0%
Score drop
2.0 pt
Recovered +24 h
-2.0 pt
Recovered +7 d
n/a
Recovered +30 d
n/a
Sentiment stabilised
No
Alert timeline
Escalation history across active and resolved incidents for this game.
Started Mar 21, 2026, 8:22 AM
Incident opened at warning severity
Mar 21, 2026, 8:22 AM
Trigger: sustained
Peaked at warning severity
Mar 21, 2026, 8:45 AM
Resolved
Mar 21, 2026, 9:10 AM