# Teku Incident Report - TEMPLATE DD Month YYYY ## Description Brief description of the issue. Should mention the affected version, the error identified and a quick summary of the cause. When applicable, it should also link to the GitHub issue. [Link to GitHub issue](https://github.com/Consensys/teku/issues/xxxx) ## User Impact What users are impacted? Everyone? Only users using a specific option? This section should give an idea of how many users are impacted by the issue. ## Timeline (all times in UTC) This is an example of a timeline - `2024-10-08 09:29` Release announced - `2024-10-08 02:14` First user reported issue on Discord - `2024-10-08 02:56` Issue confirmed by the Teku team - `2024-10-08 15:14` Announcement posted on #teku-public and #besu-teku - `2024-10-08 16:06` Raised PR fixing the issue - `2024-10-08 16:13` Started release pipeline for 24.10.1 - `2024-10-08 22:45` Updated release notes to include a known issue. - `2024-10-02 09:15` Teku 24.10.1 released ## Root Cause Analysis This section should include a description of issue, how it ocurrs and some details around the investigation. ## Resolution This section should include the steps required to fix the issue. If applicable it should also link to the Pull Request with the fix. It should also mention in what versionof Teku the fix is available. [Link to Pull Request fixing issue](https://github.com/Consensys/teku/pull/xxxx) ## Lessons Learned This section should include everything we learned from this incident. The most important thing are the actions we are going to take to prevent it from ever happening again.