A change in the backup configuration of the V2 database resulted in the generation of an unwanted read and write lock for a few minutes.
Our administrators canceled the operation very quickly to stop the process and come back to a normal situation.
We apologize for the inconvenience.