Helpdesk Access Issues

The maintenance event that caused a database node to restart has been addressed. Our maintenance exclusion workaround is in place and is preventing other clusters from restarting unexpectedly. Everything is stable at this time. We will take the necessary steps to ensure this does not happen again in the future.

The unexpected maintenance that triggered a database restart has paused. We have introduced a workaround that should prevent other clusters from undergoing the same issue. Everything appears stable for now.

We will post another update if there are any changes or in two hours.

We have found that an unexpected maintenance event caused some of our database nodes to restart. While they were coming back online, the customers assigned to the nodes could not access the service.

Our team is keeping a close eye on the system to make sure everything returns to normal.

We will share another update within the next 30 minutes or as soon as we confirm full restoration.

Our monitoring systems have detected potential access problems affecting a subset of users. We are actively investigating the root cause and working to restore full service as quickly as possible.

We will provide an update within the next 30 minutes or as soon as we have more information.