To restore connectivity when cluster creation or network operations fail in
AlloyDB for PostgreSQL, you can diagnose and resolve common Virtual Private Cloud (VPC)
peering, IP address range, and Private Service Connect configuration
errors.

## NETWORK_NOT_PEERED

This error occurs when you haven't created a VPC peering
with Service Networking.

To resolve this error, set up peering between Service Networking and the
specified VPC. For more information, see
[Enable private services access](https://docs.cloud.google.com/alloydb/docs/configure-connectivity.md.txt).

## NETWORK_PEERING_DELETED

This error occurs when the VPC peering that was present earlier is now deleted.

To resolve this issue, set up peering between Service Networking
and the specified VPC. For more information, see
[Increase private services access address space](https://docs.cloud.google.com/alloydb/docs/private-ip-space-increase.md.txt).

## NETWORK_NOT_FOUND

This error occurs when the network with the name that was specified during
cluster creation isn't found.

To resolve this issue, verify that the specified VPC network is correct.

## RANGES_EXHAUSTED

This error occurs when VPC peering doesn't have enough IP range space available
in the IP reservation that is assigned to the VPC peering.

To resolve this issue, increase the private services access address space. For
more information, see [Increase private services access address space](https://docs.cloud.google.com/alloydb/docs/private-ip-space-increase.md.txt).

To provide sufficient address space for AlloyDB, we recommend
that you use a prefix length of 16 or less, with a minimum size of /24.

## SERVICE_NETWORKING_NOT_ENABLED

This error occurs when the Service Networking API isn't enabled in
your Google Cloud project.

To resolve this issue, [enable the required APIs](https://docs.cloud.google.com/alloydb/docs/quickstart/create-and-connect.md.txt#before-you-begin).

## NETWORK_NOT_IN_CONSUMERS_PROJECT

This error occurs when the network specified during cluster creation is not in
your Google Cloud project.

To resolve this issue, verify that the specified VPC network is correct.

## NETWORK_NOT_IN_CONSUMERS_HOST_PROJECT

This error occurs when the Shared VPC network specified during cluster
creation isn't in your host project.

To resolve this issue, verify that the specified VPC network is correct.
For more information, see [Shared VPC](https://docs.cloud.google.com/vpc/docs/shared-vpc.md.txt).

## HOST_PROJECT_NOT_FOUND

This error occurs when the Shared VPC host project is not found.

To resolve this issue, verify that the specified VPC network is correct.
For more information, see [Shared VPC](https://docs.cloud.google.com/vpc/docs/shared-vpc.md.txt).

## CONSUMER_PROJECT_NOT_SERVICE_PROJECT

This error occurs when the specified Shared VPC isn't attached to the
AlloyDB project.

To resolve this issue, verify that the specified VPC network is correct.
For more information, see [Shared VPC](https://docs.cloud.google.com/vpc/docs/shared-vpc.md.txt).