Datacake - Notice history

We have identified and fixed the underlying issue, which was caused by a database having issues. We have replaced this database with another instance and the service is back online.

To ensure such outages do not happen again, we will continue making our infrastructure more robust and fail-safe.

We have identified and fixed the underlying issue, which was caused by a database having issues. We have replaced this database with another instance and the service is back online.

To ensure such outages do not happen again, we will continue making our infrastructure more robust and fail-safe.

We have identified and fixed the underlying issue, which was caused by a database having issues. We have replaced this database with another instance and the service is back online.

To ensure such outages do not happen again, we will continue making our infrastructure more robust and fail-safe.

We have identified and fixed the underlying issue, which was caused by a database having issues. We have replaced this database with another instance and the service is back online.

To ensure such outages do not happen again, we will continue making our infrastructure more robust and fail-safe.

We have identified and fixed the underlying issue, which was caused by a database having issues. We have replaced this database with another instance and the service is back online.

To ensure such outages do not happen again, we will continue making our infrastructure more robust and fail-safe.

On December 8, several of our services experienced a brief period of instability due to an issue originating from our database provider. The incident began at 11:42 UTC and services recovered by 11:51 UTC.

What happened
Our vendor identified the root cause as a failure in their backend node replacement service. This failure caused delays in deploying new nodes, which led to performance issues and affected tasks related to DNS updates, including node replacements.
The impact was limited to databases whose nodes had recently been replaced or newly created, for example after forking or scheduled maintenance.

Resolution
The vendor has identified and fixed the underlying issue in their node replacement service. Once the affected database recovered, all Datacake services returned to normal operation and have remained stable since.

Next steps
We are continuing to work with the vendor to ensure the issue is fully understood and that safeguards are in place to prevent a recurrence.

All systems continue to be stable, so we are marking this incident as resolved. Our database vendor has acknowledged the issue as originating on their end and is continuing to investigate the root cause.

We’ve identified the root cause as an issue with one of our database providers. The affected database has recovered, and all services are fully back online.

While we continue to monitor the situation, we’re working closely with the vendor to understand what happened and to prevent future occurrences. We excuse any inconvenience caused and appreciate your patience.