Your screenshot shows a new volume migration attempt is already underway. If it does not complete, you can retry by changing the Postgres service's region back to US West in the service's Settings, then selecting Southeast Asia again to trigger a fresh migration.

Hey @noahd, I switched back to US West and migrate again to Singapore and still I'm getting an error about migration.

Hi Neil, thanks for retrying and confirming it still fails. I dug into this: your database itself is healthy and online in US West, and no data is at risk. The only thing failing is the region move.

The migration copies your volume's data to Singapore, and that copy step is hitting a platform-side error, which is why it stops around 95% with 0 bytes copied no matter how many times it's retried. More retries on your end won't clear it, so please leave the Postgres service on US West for now and hold off on switching the region again.

I've escalated this to our engineering team to fix the copy on our side and complete the move to Singapore for you. I'll update you here as soon as they've made progress. Sorry for the friction on this one.

Thank you, dizzydes90. I appreciate you looking into this and keeping me updated. Please let me know once there’s any progress on the migration to Singapore.