Your Postgres service currently has no volume attached in the production environment, and the previous volume is no longer present in the project. Changing a service's region is a user-initiated action, and we are not able to restore data lost as a result. We're sorry we can't do more here.

we have a paid plan where isa our backups?

Volume backups are stored on the volume they belong to, so when the volume was lost during the region change, any backups on it were lost with it. There is no separate copy we can restore from in this case.

please connefct me to a real person\

please connect me to a real support person

We understand this is a difficult situation for a production store. The previous replies are accurate: the volume that held your Postgres data was lost during the region change, and we are not able to recover data lost as a result of that action. We are sorry we cannot do more.

that makes no sense when there is no warning showed while changing the region, no warnings about that backups are gonna be gone with just changing the region of database.

We have noted the feedback about the region-change flow not warning about the impact on volumes. The data from the previous volume is not recoverable.

please check if it's possible to get a backup from previous region postgres, ask a technical person this is production database

There was never a volume, so there were never any backups. For data persistence, use a volume at the correct mount point going forward.

so simple is that? hole prod database is gone and railway does not have anything? with a paid plan. and all you can do is saying sorry while your dashboard shows 0 warning during just changing a region of databse

Since you explicitly set up the database without a volume, we couldn't have warned you. Apologies, we cannot do more here.