» Published on
A scheduled network configuration change affecting the internal DNS resolution services used by customer databases was mistakenly deployed ahead of schedule. We have promptly reverted this change, and the situation is back to normal. Applications that had already performed DNS resolution to access their database and had the results cached were not affected by this incident.
» UpdatedThe fix was applied on the 2 regions. Databases are accessible again.
» UpdatedWe're currently facing an issue related to access of the databases on the osc-fr1 and osc-secnum-fr1 regions. A fix is currently being applied
» Updated