# Managing incidents Incident management is a critical component in maintaining the operational integrity and reliability of Web3 applications. It entails the prompt identification, assessment, and rectification of issues to avert their recurrence. The significance of this process in the web3 cannot be underestimated. While audits are very important before going to production, the risk of incidents is still imminent. Proper incident response and management is vital. Not only does effective incident management minimize service downtime and ensure security; it also plays a vital role in preserving and enhancing the trust of the user community. In the dynamic and often unpredictable realm of web3, where new vulnerabilities can emerge rapidly, the ability to efficiently manage and resolve incidents reinforces user confidence and fosters a more secure and stable environment for digital transactions and interactions. Of course incidents are not only exploits, but incidents can also be pure service downtime. While blocktorch aims at equipping web3 engineers with tools for developing secure and robust applications and increase collaboration between security auditors and engineers, we also want to give our users the best possible toolkit to [troubleshoot](/use-cases/managing-incidents/troubelshooting.md) in case of incidents and problems as well as making sure they do not happen again. > "Instead of proactively knowing about any issues arising in any piece of our stack we had to purely rely on the audits, and wait for our community to flag issues in our Discord. With blocktorch we were able to turn this process around and manage reliability proactively." --- # Agent Instructions: 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: ``` GET https://docs.blocktorch.xyz/use-cases/managing-incidents.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.