Community-driven detection
Every status update on Downtester starts with player reports. When you report a problem — connection failure, login issue, lag, matchmaking error, or disconnection — your report joins a pool of signals from other players experiencing the same thing. We don't scrape third-party APIs or rely on official announcements. Our data comes directly from the people playing the game.
Adaptive thresholds
Not every game has the same player base. A spike of 10 reports for a small indie title is significant, while the same number for a game with millions of players is noise. Downtester assigns each game a size category (mega, AAA, popular, mid-tier, indie, micro) and adjusts detection thresholds accordingly. This means we can detect outages early for smaller games without flooding larger titles with false alarms.
Status levels
Based on report volume, velocity, and diversity, each game is assigned one of these statuses:
Operational
No significant reports. Servers appear to be running normally.
Minor Issues
A small number of reports have come in. We're monitoring but no widespread problem is confirmed.
Degraded / Having Issues
Report volume has crossed the threshold for this game's size category. Multiple players are confirming problems.
Major Outage
High-confidence detection of a widespread problem. Report volume is well above normal and reports are coming from multiple independent players.
Confidence scoring
Every status assessment comes with a confidence percentage. This score reflects how certain we are that the detected status is accurate. It factors in the number of unique reporters, geographic spread, report velocity (how fast new reports are arriving), and consistency across issue types. A high confidence score means many independent players are reporting the same class of problem within a short window.
Time windows and freshness
We evaluate reports across three windows: last 15 minutes, last hour, and last 24 hours. The 15-minute window catches active, ongoing issues. The hourly window identifies trends. The 24-hour window provides context — if a game had 50 reports earlier but none in the last hour, we mark it as "previously impacted" rather than "down." Reports older than 24 hours are excluded from status calculations entirely.
Spam prevention and rate limiting
To keep reports genuine, each user can only submit one report per game within a cooldown period. We also track unique reporters separately from total report count — a single person submitting repeatedly won't inflate the numbers. IP-based and session-based deduplication ensures that the report count reflects real affected players.
Player count data
For games on Steam, we pull live player counts to add context to outage reports. If a game has 50,000 players online and 3 reports, that's likely background noise. If a game has 500 players and 3 reports, that's a meaningful signal. Player count data also powers the trending and popular pages, showing you which games people are playing right now.
Coverage
Downtester covers thousands of games and services. Our database includes titles from every major platform — PC, PlayStation, Xbox, Nintendo, and mobile. New games are added automatically from IGDB metadata, so coverage begins before a game even launches. When servers go live on day one, Downtester is ready to track reports.
A note on transparency: Downtester is not affiliated with any game publisher or platform. Our status assessments are based entirely on player-submitted reports and public data. We don't receive advance notice of maintenance windows or planned downtime. What you see on Downtester is what real players are experiencing, processed through our detection algorithm in real time.