Live-ops incident postmortems (2020–2025)
Pixelforge Games: docs & wiki, team chat and tickets (6 years)
Data mix
approximate, based on what's included- Documents
- Chat
- Tickets
Company archive in Gaming
Pixelforge Games · 51–200 employees · 6 years · 1.5K postmortems
Listed by Pixelforge Games
Based in Poland.
Full inventory ready
The owner has shared a file-level inventory, so we can send you the schema and samples quickly.
De-identified before delivery
Staff replaced with role labels; game names and hostnames tokenized
Owner-approved licence
The owner signs off on each buyer, scope and term in writing.
Six years of written postmortems, timelines and action items from live incidents on multiplayer mobile games run by a Polish studio.
Pixelforge writes a postmortem for each significant live incident: matchmaking outages, broken events, economy exploits, bad client releases. There are 1,486 of them here from 2020 to 2025, written in Markdown using a template that evolved over time. A typical document has a summary, timeline, player impact, contributing factors and action items. The action items are also tracked as Jira issues, and we include their completion status, which reveals how often follow-up work actually got done. The on-call Slack thread is attached for incidents after 2022. Quality varies. Major outages get several careful pages, while small incidents may only have a few lines. Early documents predate the template and tend to focus on what broke, not why. Game names, server hostnames and player numbers have been replaced or banded, so you won't be able to gauge absolute scale.
LogitAtlas