Hello,

I received this email for my Postgres service:

"Your Railway service will be affected by an infrastructure maintenance event.

• Resource: Project: - / Service: Postgres / Environment: development
• Duration: 10 minutes from time of this notification
• Impact: Service will be offline"

In this specific case the impacted database was in my development environment, so the impact was limited. However, I would like to better understand how Railway handles this operationally:

• Was this immediate maintenance behavior related to the fact that the service was in a development environment?
• Does Railway distinguish between development and production environments when triggering infrastructure maintenance?
• Can the same type of immediate downtime happen to production Postgres services as well?
• If yes, is there any scheduling mechanism, maintenance window configuration, or advance notice policy for production workloads?

My concern is mainly around customer communication and operational planning: if a production database can go offline with only immediate notice, that leaves no real time to warn customers or prepare mitigation.

I’m not complaining about this specific event, since it only affected development, but I’d appreciate clarification on whether this is expected behavior only for dev or also for production services since we cannot afford any sudden downtime.

Thank you