» Published on Tue, 21 Oct 2025 16:00:00 +0000

• Resolved

  All affected databases are now fully operational.

  » Updated Tue, 21 Oct 2025 19:21:00 +0000

• Update

  Fix applied. Our operators are restarting all databases owned by this failed host.

  » Updated Tue, 21 Oct 2025 17:20:00 +0000

• Update

  We’ve identified the root cause. The affected host needs to be restarted once more to fully apply the fix.

  » Updated Tue, 21 Oct 2025 16:44:00 +0000

• Update

  Our operators are always restarting all databases owned by the failed host.

  » Updated Tue, 21 Oct 2025 16:41:00 +0000

• Update

  Almost all databases are restarting. Our operators are handling the last ones and running post incident checks.

  » Updated Tue, 21 Oct 2025 16:11:00 +0000

• Investigating

  One of our database hosting node is misbehaving. Our team has been alerted. The host is being restarted, We'll then restart all database instances. Databases with a business plan should not have faced any downtime and failover to a secondary instance. Starter plan databases will be reachable again once an operator completes the process. We will keep you updated

  » Updated Tue, 21 Oct 2025 16:00:00 +0000