Incident #211
The most recent tracked incident was a negative warning alert triggered by combined conditions. Across the visible window, the game added 330 reviews, the current 1-hour directional delta sits at 14, and the incident peak reached 105 in 1 hour. 1 earlier incident have already resolved.
Before score
35.0%
Current score
34.0%
Change -2.9%
Review velocity
105 reviews
May 3, 2026, 7:36 AM - May 3, 2026, 9:36 AM
Cause confidence
Review Manipulation (92% confidence)
Quick summary
What happened?
The most recent tracked incident was a negative warning alert triggered by combined conditions. Across the visible window, the game added 330 reviews, the current 1-hour directional delta sits at 14, and the incident peak reached 105 in 1 hour. 1 earlier incident have already resolved.
How bad was it?
Peak tier: WARNING. Review velocity spiked to 105 reviews. Score moved -2.9%. Resolved in 1 hours.
What triggered it?
Likely causes: Review Manipulation, Patch Backlash. Trigger type: combined. See the timeline tab for event-level detail and patch notes.
Where to go next?
Opened: May 3, 2026, 8:37 AM
Resolved: May 3, 2026, 9:48 AM
Peak severity: warning
Score change: -2.9%
Trigger: combined
Before / after
Window from May 2, 2026, 9:02 PM to May 3, 2026, 10:18 AM.
Score before
34.0%
Score now
34.0%
Change
0.0%
Reviews added
330
Peak velocity
101/h
Common questions
Quick answers about what happened and why.
What happened?
BidKing:η«ζδΉη saw a sudden spike in negative reviews. 330 additional reviews were posted during the tracked window.
How severe was it?
This was a moderate incident that stayed below the most extreme thresholds.
What caused it?
Review Manipulation (59%), Patch Backlash (41%)
Is it over?
It ended after 1 h 11 m. The review score has since stabilized.
How much did the review score change?
The score moved by 0.0 points, from 34.0% to 34.0%. At its busiest, the game received 101 reviews per hour.
Were other games affected too?
No related incidents were detected for other games in the same time period.
Opened: May 3, 2026, 8:37 AM
Resolved: May 3, 2026, 9:48 AM
Peak severity: warning
Score change: -2.9%
Trigger: combined
Incident velocity window
Impact 0.0%