Update - Google Cloud is starting up systems in batches out of precaution. We're pushing to be first in line but we are not the only one. We will try to keep you posted on the progress. Expectation is still that we are back to normal by tonight.
Feb 27, 2026 - 21:31 CET
Update - After close communication with Google Netherlands, we learned that the issue is mitigated and that a restart procedure is soon to be started. We are careful with being positive and wait further updates. We will share next updates as soon as possible.
Feb 27, 2026 - 20:11 CET
Update - We are still waiting for more information about the situation. The disturbance impacts multiple companies using the Google Bare metal solutions. We continuously follow up the latest status as much as we can. Our sincere apologies for the situation.
Feb 27, 2026 - 19:39 CET
Update - We are still waiting with deciding on the failover to our DR environment. The reason is the protection of data consistency and the risks we take for the period after the switch.
We are in close touch and escalated via all possible options with our Google Cloud contacts.
Feb 27, 2026 - 18:30 CET
Update - We are continuing to work on a fix for this issue.
Feb 27, 2026 - 18:00 CET
Update - We decided to put our Disaster Recovery process into motion and switched over to Frankfurt. This gives a slight decrease in performance. We will keep you posted on the progress.
Feb 27, 2026 - 17:46 CET
Update - We are in close touch with people from Google Cloud, trying to identify the root cause.
Feb 27, 2026 - 17:21 CET
Identified - All production database servers went for a hard reboot, including one of the acceptance servers. We are waiting to finish up the booting process to continue investigation and to be able to start up the databases as soon as possible.
Feb 27, 2026 - 17:15 CET
Investigating - We are currently experiencing issues with production databases. This has all priority it requires, more updates soon.
Feb 27, 2026 - 16:51 CET