my mysql db is not coonecting to my api after the outage happened , it was working before
enzondev
FREEOP

a month ago

the error of the db at maglev.proxy.rlwy.net and on connection to api enzone-api-production.up.railway.app

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 27 days ago


sam-a
EMPLOYEE

a month ago

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.


Status changed to Awaiting User Response Railway 27 days ago


Status changed to Solved enzondev 26 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...