> For the complete documentation index, see [llms.txt](https://gyrinx.gitbook.io/gyrinx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gyrinx.gitbook.io/gyrinx/operations/incidents.md). # Incident Reports Write-ups of production incidents: what broke, why, and what changed as a result. They exist so the next person to meet a similar failure starts with what we learned rather than from scratch. ## What belongs here * The failure mechanism, in enough detail to recognise it again. * Reasoning behind the fixes, especially where an obvious-looking option was rejected. * Diagnostic steps that turned out to matter, including the misleading ones. ## What does not **This repository is public.** A good incident report describes how a system failed; it must not double as instructions for making it fail again. So these write-ups deliberately leave out: * Specific thresholds, limits and capacity figures. * The exact composition of allow and deny lists. * Any description of how a control could be circumvented. * Current weaknesses and where cover is thin. That detail is real and worth recording — it lives in the private runbook and in the cloud console, not here. When a report needs to refer to it, it says so and stops. If you are writing one of these, the test is: *could a reader use this to hurt us more efficiently than they could without it?* If yes, generalise until the answer is no. The mechanism is the lesson; the numbers are not. ## Reports * [Crawler overload — 6 August 2026](/gyrinx/operations/incidents/2026-08-06-crawler-overload.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gyrinx.gitbook.io/gyrinx/operations/incidents.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.