The database load has returned to normal and production cluster performance is stable.

We have scaled up the production database instance to provide additional capacity and improve stability.

Performance has recovered, and we are continuing to monitor the system closely. In parallel, we are investigating the root cause of the database load spikes to determine whether further corrective measures are required.

We identified elevated CPU load on the production database as the cause of the degraded performance.

The high load was related to the number of concurrent database connections.

We are currently experiencing degraded performance on our production cluster, resulting in increased response times.

The issue appears to be related to database connections. We are actively investigating the root cause and working to restore normal performance.

Dashboard statistics will get repaired with the next Hanko Cloud Console release in a few days. Thank you for your patience.

Since the Hanko v3 release, statistics in the Hanko Cloud dashboard have not been displayed reliably. Affected metrics may show a value of 0, even when usage data is available.

The following metrics are affected:

• Total users
• Monthly active users
• Sign-ups

Authentication services and user data are not affected. The issue is limited to the statistics displayed in the dashboard.

We are aware of the problem and are working on a fix.

The issue has been resolved.

Google and GitHub sign-in for the Hanko Cloud dashboard should now work as expected again. Customer projects were not affected.

We apologize for the inconvenience.

We have confirmed that customer projects are not affected by this issue.

The issue is limited to Google and GitHub sign-in for the Hanko Cloud dashboard. Signing in via email continues to work and can be used as a workaround while we investigate the cause.

We are currently investigating an issue with social sign-in using Google and GitHub.

At the moment, users may be unable to sign in to Hanko Cloud using Google or GitHub as an identity provider. Signing in via email continues to work and can be used as a workaround.

We are also investigating whether this issue may affect customer projects using Google or GitHub sign-in. We will provide an update as soon as we know more.

We apologize for the inconvenience.

Nodes were unresponsive due to a memory exhaustion cascade. We increased the number of nodes and were able to resolve the issue.

Some Hanko Cloud projects on the Free plan may not be responsive due to scheduling issues in the production cluster.

Updating all Hanko projects to the recent version at once caused the Free plan nodes to fail the restart scheduling. After increasing the cluster's resource limits, things are under control now. We will switch to a batched update approach to avoid this issue from now on.

Projects in the free plan are not reachable.

Services are up and running again.

Planned cluster updates have caused severe service interruptions.

The problem has been resolved.

The problem is identified to be a memory issue with an internal component. We have fixed the the problem, and will continue to monitor the situation.

We are encountering some issues with our infrastructure. We are looking into the issue.

All systems are normally operational.

We experienced a disruption of some of the service.

All systems are normally operational.

We experienced a disruption of some of the service.

All systems are normally operational.

We experienced a disruption of some of the service.

The issue has been fixed.

Some users are encountering {title: "unable to process request", details: "EOF", status: 400} issues when trying to initialize Passkey API actions.

Increased the minimal number of nodes, cluster is stable now.

Some Hanko Cloud projects suffered availability issues on Saturday (status 503).

We've identified the issues to be caused again by the Autoscaler that has been overzealous when downscaling nodes. Additional changes were made to the cluster config and the cluster is now stable.

Fine-tuning of the autoscaler has resolved the issue.

Hanko Cloud Free projects suffered frequent availability issues this week (status 503).

We've identified the issues to be caused by the autoscaler that has been overzealous when downscaling nodes that run Free projects. Changes were made to the cluster config and we are monitoring the results.

If your app / service is impacted by this, please consider upgrading to Hanko Cloud Pro, as those projects run on dedicated nodes that are not affected by the incorrect behavior of the autoscaler.