» Published on
We would like to add some details about this incident: Our protection mechanisms for this type of attack were partly ineffective because IP blocking rules for malicious addresses had been deleted during previous maintenance operations. We've put these rules back in place and ensured they are now permanent. Procedures have also been put in place to respond more quickly to similar attacks by identifying the problematic IP addresses and adding them to the protection mechanism. Other architectural changes are ongoing to improve the platform's resilience to these types of issues.
» UpdatedIncident is now considered resolved.
» UpdatedMitigation has been setup, situation is stable for more than 40 minutes. We're keeping an eye on the situation.
» UpdatedSituation is currently back to nominal performance, our team is still working on it.
» UpdatedA second wave of instability happened, the root cause seems to be a DDoS attack impacting our network. We're working on mitigating the attack.
» UpdatedSituation seems to be better, we're still analyzing the cause of this slowdown.
» UpdatedOur probes have raised an alert concerning the network access to the region.
Our team has been alerted, we are analysing the problem.
Access to hosted application on the region osc-fr1 is slow
» Updated