diff --git a/ansible.cfg b/ansible.cfg
index 3709fb3..65af70e 100644
--- a/ansible.cfg
+++ b/ansible.cfg
@@ -4,3 +4,4 @@ interpreter_python=/usr/bin/python3
 gathering=smart
 fact_caching=jsonfile
 fact_caching_connection=ansible-facts.json
+callbacks_enabled = ansible.posix.profile_tasks
diff --git a/documentation/INCIDENTS.md b/documentation/INCIDENTS.md
index d24ce57..a70faf0 100644
--- a/documentation/INCIDENTS.md
+++ b/documentation/INCIDENTS.md
@@ -1118,3 +1118,34 @@ all updates where doing using the new "idempotent" `playbook_sysupgrade` (since
 * 2022.10.24 01:44 - 01:46: `gw-core01`
 => downtime of the accesspoints in the specified timeframe
 => downtime of `gw-core01` in the specified timeframe
+
+
+025 2022.11.19 04:00 (ANS) | (maintenance) (try to) steer clients into 5 GHz band
+---------------------------------------------------------------------------------
+
+---
+
+_this log entry was added way after doing the actual work.
+Please read it with a grain of salt_
+
+---
+
+**problem**:
+* (if i remember correctly) way more clients in the 2,4 GhZ band than in the 5 GHz band (3/4 to 1/4)
+
+**solution**:
+* halfe the transmit power in the 2,4 GHz band
+* increased transmit power in the 5 GHz band by 1 dBm
+* implemented by `5017cb5`
+
+**impact**:
+This restarted wifi on all APs at the same time.
+Downtime for all clients for a few seconds at 04:00 in the morning.
+
+**validation**:
+One day afterwards it seemed like there where more clients in the 5 GHz band (50/50), but the datarates dropped for most of them.
+
+**critisism**:
+* placement, transmit power and supported bands of the clients impact 5 GHz utilization
+* unsure what actually is the problem
+* also did not correctly validate for a few days