We experienced an issue with our WebApp on 2026-03-24 from around 9:30 to 11:00 CET. Our team has worked diligently to identify the root cause and implement a resolution. In this post-mortem, we want to share the details of what happened, why it happened, what we did to resolve it, and what we will do to prevent similar incidents in the future.
What happened?
We experienced service instability caused by a bug in a third-party dependency. This resulted in intermittent errors and degraded performance of the Web App.
Why did this happen?
A bug in a third-party dependency caused unexpected errors in our Web App, leading to occasional crashes. This issue was triggered under specific conditions that were not caught in prior testing.
What did we do?
We resolved the issue temporarily by implementing a safeguard and later by properly solving the issue with this dependency. Stability was restored once the temporary fix was deployed, with full recovery at around 10:40 CET.
What can we do to improve?
We will expand our test coverage to better capture edge cases, ensuring that unusual or unexpected scenarios, especially those that lead to this incident, are identified and prevented before deployment.
We apologize for any inconvenience this incident may have caused. We are committed to ensuring the stability and reliability of our services and will continue to take proactive measures to prevent similar incidents from happening in the future.
If you have any questions or concerns, please don't hesitate to reach out to our support team for assistance.