Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for PostgreSQL
    • Restoring a Managed Service for PostgreSQL cluster after running out of free storage space
    • You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled
    • Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created
    • Resolving issues with updating configurations of clusters with `local-ssd` disks
    • Resolving the issue of cluster storage overflow with WAL logs
    • Resolving the `psql error could not translate host name to address nodename nor servname provided, or not known` error
    • Resolving the `Unrecognized configuration parameter stats_temp_directory` error
    • Resolving the `max_connections conn_limit is too high` error
    • Resolving the `Must be superuser to create this extension` error
    • Fixing the `terminating connection due to administrator command` and `ERROR: odyssey: remote server read/write error` errors
    • Resolving the `422 UNPROCESSABLE ENTITY The specified extension <'ext_name'> is not present in shared_preload_libraries` error
    • How `Conn limit` works
    • How to set up SQL query filtering
    • How to enable SQL query logging

In this article:

  • Issue description
  • Solution
  1. Managed Service for PostgreSQL
  2. Managed Service for PostgreSQL cluster switches to `UNKNOWN` once created

Managed Service for PostgreSQL cluster switches to UNKNOWN once created

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution

Issue descriptionIssue description

Trying to create a cluster with the b1.nano host class fails, and the cluster switches to the UNKNOWN status.

SolutionSolution

It may take a long time to deploy a cluster with this host type. This is because of too low percentage of guaranteed CPU uptime: 5% for b1.nano. Clusters with this host type have two vCPUs with the guaranteed uptime of 5% and 2 GB RAM.

One cannot consistently forecast the behavior for the guaranteed CPU uptime of less than 50%. Generally speaking, creating clusters with b1.nano host classes is a longer process because of limited resources used for deploying components to the hosts.

When creating your clusters, you might want to opt for choosing more powerful configurations with CPU uptime of more than 50%, such as c3-c2-m4.

Alert

The b1.nano host class is currently being discontinued. You will not be able to create a new cluster with this host class.

You can view the up-to-date list of host classes here.

Was the article helpful?

Previous
You are unable to delete your Managed Service for PostgreSQL cluster in the `DEAD` status if it has deletion protection enabled
Next
Resolving issues with updating configurations of clusters with `local-ssd` disks
© 2025 Direct Cursus Technology L.L.C.