2 months ago
I'm unsure if this is related to the outage since it says all systems are operational now:
However, we still can't connect to the MongoDB, the deployment says it's online, but trying to access the database or backups gives the following error (attached).
Its not clear that this is affecting this part of the infrastructure since it only mentions slow deployments and network issues.
I did recieve an email saying that the MongoDB is under maintenance and will last 30 minutes, but it's been over an hour.
A little confused what is going on with the status saying all systems are operational.
Attachments
4 Replies
2 months ago
Hey! Apologies for the late response here. Are you still experiencing any issues? I believe this was related to an outage we experienced (https://status.railway.com/cmj89j6z2000qodpsfs4nc2gb).
Status changed to Awaiting User Response Railway • 2 months ago
ray-chen
Hey! Apologies for the late response here. Are you still experiencing any issues? I believe this was related to an outage we experienced (https://status.railway.com/cmj89j6z2000qodpsfs4nc2gb).
2 months ago
For me and many others, the connection to the database did not automatically restore. While I personally received an email about maintenance and no action required, the connection only restored after redeploying the database. This is likely what other people facing this issue has to do.
Status changed to Awaiting Railway Response Railway • 2 months ago
pp-tom
For me and many others, the connection to the database did not automatically restore. While I personally received an email about maintenance and no action required, the connection only restored after redeploying the database. This is likely what other people facing this issue has to do.
2 months ago
Unfortunately this did result in longer downtime as it wasn't clear on how to resolve this issue and it was just a finger in the air attempt to restore service.
pp-tom
Unfortunately this did result in longer downtime as it wasn't clear on how to resolve this issue and it was just a finger in the air attempt to restore service.
2 months ago
Sorry for the lack of clarity. We're seeing a manual re-deploy required for a subset of services and it looks like you were impacted by this :-/
Going to see how we can fix this moving forward and/or make the messaging much clearer. Thanks for the patience!
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved pp-tom • 2 months ago