I’ve been working on a side project called OutageScope, a community-driven server status tracker focused mainly on games and online services.
The idea came from a very simple frustration:
When a game isn’t working, most “status” sites only tell you yes or no — whether it’s down. But as a gamer, that’s rarely enough. Sometimes login fails, matchmaking breaks, or only certain regions are affected, and existing tools don’t really capture that well.
So instead of building another generic downtime checker, I tried a different approach:
Let players report issues directly
Analyze report spikes over time (last hour, last 24 hours)
Combine community data with pattern detection, instead of relying on a single signal
Show a clear status so players can quickly tell whether it’s a widespread issue or something local
The goal isn’t to replace official status pages, but to give players a faster, more realistic picture of what’s happening — based on what other players are experiencing right now.
This is still early and very much a work in progress. I’m especially interested in feedback around:
How useful community-reported data feels vs official sources
What kind of status details gamers actually care about
Any pitfalls you see with a community-driven model like this
If you’ve built something similar, worked on monitoring systems, or just play online games a lot, I’d love to hear your thoughts.
Checkout: https://outagescope.com/