We are investigating an Issue with AlloyDB for PostgreSQL

The issue with AlloyDB for PostgreSQL has been resolved for all affected users as of Thursday, 2023-03-30 18:40 US/Pacific. We thank you for your patience while we worked on resolving the issue.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Engineers have mitigated the issue for new clusters created from restores as of Thursday, 2023-03-30 07:10 US/Pacific. The issue should be recovered for most customers, however Engineering is taking additional steps to ensure a full recovery for all affected customers, an ETA has not been determined on when this work will be fully completed. We will continue to provide updates on any changes and will provide more information by Thursday, 2023-03-30 21:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: Customers can re-restore from the same backup and potentially delete the old broken one.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Engineers have mitigated the issue for new clusters created from restores as of Thursday, 2023-03-30 07:10 US/Pacific. The issue should be recovered for most customers, however Engineering is taking additional steps to ensure a full recovery for all affected customers, an ETA has not been determined on when this work will be fully completed. We will continue to provide updates on any changes and will provide more information by Thursday, 2023-03-30 18:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: Customers can re-restore from the same backup and potentially delete the old broken one.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Engineers have mitigated the issue for new clusters created from restores as of Thursday, 2023-03-30 07:10 US/Pacific. The issue should be recovered for most customers, however Engineering is taking additional steps to ensure a full recovery for all affected customers, an ETA has not been determined on when this work will be fully completed. We will continue to provide updates on any changes and will provide more information by Thursday, 2023-03-30 18:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Engineers have mitigated the issue for new clusters created from restores as of Thursday, 2023-03-30 07:10 US/Pacific. Mitigation work is still underway for restored clusters that were previously affected. We do not have an ETA for mitigation of previously affected clusters. We will provide more information by Thursday, 2023-03-30 15:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Engineers have mitigated the issue for new clusters created from restores. Mitigation work is still underway for restored clusters that were previously affected. We do not have an ETA for mitigation of previously affected clusters. We will provide more information by Thursday, 2023-03-30 13:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Mitigation work is currently underway by our engineering team and is taking longer than initially expected. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2023-03-30 12:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2023-03-30 09:30 US/Pacific. We will provide more information by Thursday, 2023-03-30 10:30 US/Pacific. Diagnosis: Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Customers will see an internal error (error code: 13) when they try to create an instance. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2023-03-30 09:00 US/Pacific. We will provide more information by Thursday, 2023-03-30 09:30 US/Pacific. Diagnosis: Customers will see an internal error (error code: 13) when they try to create an instance. Customers will experience this issue when they try to create a primary instance in a cluster that was restored. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: Mitigation work is currently underway by our engineering team. The mitigation is expected to complete by Thursday, 2023-03-30 09:00 US/Pacific. We will provide more information by Thursday, 2023-03-30 09:30 US/Pacific. Diagnosis: None at this time. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: We are experiencing an issue with AlloyDB for PostgreSQL. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-03-30 05:00 US/Pacific with current details. Diagnosis: None at this time. Workaround: None at this time.

Summary: We are investigating an Issue with AlloyDB for PostgreSQL Description: We are experiencing an issue with AlloyDB for PostgreSQL. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2023-03-30 04:30 US/Pacific with current details. Diagnosis: None at this time. Workaround: None at this time.