Database for weezticket was hit by unusual CPU load at 15:38. Origin not yet identified.
everything going slower and slower, we take the decision at 15:58 to initiate a reboot with failover to switch the load on our replica.
Everything is restored as usual and is working as usual since 16:00.
We will keep diging to find the root cause, and avoid the incident to reproduce again.
An incident is ongoing on WeezTicket database (impacting all weezticket components).
More info to come asap.