Scheduled for February 14, 2025 at 11:00 PM – February 15, 2025 at 2:00 AM
Affects
Edge Network
Under maintenance from 11:00 PM to 2:00 AM
TCP Proxy
Under maintenance from 11:00 PM to 2:00 AM
Completed
February 15, 2025 at 2:00 AMCompleted
February 15, 2025 at 2:00 AMMaintenance has completed successfully
In progress
February 14, 2025 at 11:00 PMIn progress
February 14, 2025 at 11:00 PMMaintenance is now in progress
Update
February 14, 2025 at 11:00 PMPlanned
February 14, 2025 at 11:00 PMWe will be provisioning more domains for TCP Proxy allocations. During this time the new domain may not proxy traffic while the global TCP Proxy system picks up these changes. We expect this window to only be a few minutes.
All existing TCP Proxy domains will continue to work. Connections may be closed due to reloads though and reconnecting will work. This is expected behaviour whenever we have pushed updates to this service in the past.
These changes will allow us to live reload more configs in the future, minimizing the needs for "hard reloads" which may drop connections. We recommend people use the private network when possible, for which this is a non-issue.
Planned
February 14, 2025 at 9:44 PMPlanned
February 14, 2025 at 9:44 PMA note; this will only, potentially, affect services which are dialing a Railway database from OUTSIDE Railway, via the TCP proxy (viaduct.rlwy.net, monorail.rwly.net, etc)
Private network connections (myservice.railway.internal) will be unaffected
