[osc-fr1] A DB node is misbehaving

» View Event Details | Created Mon, 03 Jun 2024 16:41:00 +0000

Resolved

All databases are up and running. If you still have issues please contact us via the support.

Posted: Mon, 03 Jun 2024 17:45:00 +0000

Update

Almost all databases have been restarted, our operators are working on restarting the remaining ones.

Posted: Mon, 03 Jun 2024 17:20:00 +0000

Update

Databases are currently restarting on the impacted node.

Posted: Mon, 03 Jun 2024 17:00:00 +0000

Investigating

One of our database server is mis-behaving. Our operators have been paged. The server will be restarted. Databases on a starter plan will face downtime during this operation. Databases on a business plan will failover to their secondary instance without downtime.

We will keep you updated

Posted: Mon, 03 Jun 2024 16:41:00 +0000

[osc-fr1] A DB node is misbehaving

» View Event Details | Created Mon, 10 Jun 2024 15:05:00 +0000

Resolved

All databases are up and running. If you still have issues please contact us via the support.

Posted: Mon, 10 Jun 2024 15:58:00 +0000

Update

All databases have been restarted. We are now executing post-incident checks.

Posted: Mon, 10 Jun 2024 15:34:00 +0000

Update

Databases are currently restarting on the impacted node.

Posted: Mon, 10 Jun 2024 15:20:00 +0000

Investigating

One of our database server is mis-behaving. Our operators have been notified.

The server will be restarted. Databases on a starter plan will face downtime during this operation. Databases on a business plan will failover to their secondary instance without downtime. We will keep you updated

Posted: Mon, 10 Jun 2024 15:05:00 +0000

[osc-fr1] A DB node is misbehaving

» View Event Details | Created Wed, 12 Jun 2024 19:40:00 +0000

Resolved

All databases are up and running. If you still have issues please contact us via the support.

Posted: Wed, 12 Jun 2024 23:01:00 +0000

Update

All databases have been restarted. We are now executing post-incident checks.

Posted: Wed, 12 Jun 2024 20:49:00 +0000

Update

The server is being restarted and databases are being restarted.

Posted: Wed, 12 Jun 2024 20:27:00 +0000

Investigating

One of our database server is mis-behaving. Our operators have been notified. The server will be restarted. Databases on a starter plan will face downtime during this operation. Databases on a business plan will failover to their secondary instance without downtime. We will keep you updated

Posted: Wed, 12 Jun 2024 20:10:00 +0000

[osc-fr1] Impossible to provision new databases or change database plan/version

» View Event Details | Created Mon, 17 Jun 2024 08:13:00 +0000

Resolved

The incident is now considered closed. If you are still experiencing problems, please contact our support team.

Posted: Mon, 17 Jun 2024 09:29:00 +0000

Update

All databases are now up and running, plan changes and version upgrades have also been applied. we're currently performing post-incident checks.

Posted: Mon, 17 Jun 2024 08:56:00 +0000

Update

The root cause was identified and a corrective operation was carried out. The databases that were stuck in a provisioning state are now being processed.

Posted: Mon, 17 Jun 2024 08:24:00 +0000

Investigating

It is currently impossible to provision new databases or change plans/versions. Our operators are currently carrying out investigations.

Posted: Mon, 17 Jun 2024 08:13:00 +0000

[osc-fr1] A DB node is misbehaving

» View Event Details | Created Thu, 20 Jun 2024 10:19:00 +0000

Resolved

All databases are up and running. If you still have issues please contact us via the support.

Posted: Thu, 20 Jun 2024 13:00:00 +0000

Update

All databases have been restarted. We are now executing post-incident checks.

Posted: Thu, 20 Jun 2024 10:43:00 +0000

Update

The server is being restarted and databases are being restarted.

Posted: Thu, 20 Jun 2024 10:30:00 +0000

Investigating

One of our database server is mis-behaving. Our operators have been notified. The server will be restarted. Databases on a starter plan will face downtime during this operation. Databases on a business plan will failover to their secondary instance without downtime. We will keep you updated

Posted: Thu, 20 Jun 2024 10:19:00 +0000

[osc-fr1/osc-secnum-fr1] Problems accessing databases

» View Event Details | Created Mon, 24 Jun 2024 08:13:00 +0000

Resolved

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.

Posted: Mon, 24 Jun 2024 08:42:00 +0000

Update

The fix was applied on the 2 regions. Databases are accessible again.

Posted: Mon, 24 Jun 2024 08:25:00 +0000

In Progress

We'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

Posted: Mon, 24 Jun 2024 08:13:00 +0000

[osc-fr1] A DB node is misbehaving

» View Event Details | Created Sat, 29 Jun 2024 14:40:00 +0000

Resolved

The incident is now considered resolved. If you still experience issues, please contact our support team.

Posted: Sat, 29 Jun 2024 15:00:00 +0000

Update

Most databases are back online, we take care of databases that have not been restarted automatically, and perform post-incident checks.

Posted: Sat, 29 Jun 2024 14:51:00 +0000

Update

Databases hosted on this node are being restarted. Only databases using a Starter plan are affected.

Posted: Sat, 29 Jun 2024 14:51:00 +0000

Investigating

A database node became unreachable due to a problem with our infrastructure provider. This node is currently being rebooted.

Posted: Sat, 29 Jun 2024 14:40:00 +0000