» Published on Thu, 06 Mar 2025 10:18:00 +0000

• Resolved

  The incident is now considered as over.

  » Updated Thu, 06 Mar 2025 17:51:00 +0000

• In Progress

  We are still making operations on this server. Restart of databases is planned in a few minutes

  » Updated Thu, 06 Mar 2025 17:30:00 +0000

• Update

  The node in question is still causing issues. We have identified the root cause and are currently working on it. This will require restarting the affected VM. Customers with a Business plan will not be impacted, while customers with a Starter plan will experience a few minutes of downtime

  » Updated Thu, 06 Mar 2025 17:02:00 +0000

• Resolved

  All checks are OK. The incident is now considered as over on our side.

  » Updated Thu, 06 Mar 2025 11:20:00 +0000

• Update

  All databases are up and running. Our operators are entering post incidents checks. If you still have issues with your database please contact us via the support.

  » Updated Thu, 06 Mar 2025 11:16:00 +0000

• In Progress

  Databases are currently being restarted on the impacted database hosting node.

  » Updated Thu, 06 Mar 2025 10:49:00 +0000

• In Progress

  The database hosting node has been restarted. Databases will restart soon on the impacted hosting node.

  » Updated Thu, 06 Mar 2025 10:29:00 +0000

• In Progress

  We are restarting the impacted database hosting node.

  » Updated Thu, 06 Mar 2025 10:22:00 +0000

• Investigating

  One of our database hosting node is misbehaving. Our team has been alerted.

  » Updated Thu, 06 Mar 2025 10:18:00 +0000