that incident has been resolved, looking at your http logs, it looks like your app itself is timing out

yep indeed its the app itself that is timing out, but because it cant contact the database, can you try to redeploy the database

Ok thanks, that seems to have worked! Was that down to the same issue or something else, I don't believe I made any database changes?

just wanted to let you know ive had similar issues since the new proxy migration

same with brillew

<:joeshrug:1106998983676678244>

i can confirm the issue was not with the proxy, the issue was the application itself, in this case a database, that wasn't able to respond to the connection attempts

I haven't made any database configuration changes for the last couple of weeks and afaik it's just started today and other people were experiencing similar issues so I'm just surprised it's down the specific application, when you say the application itself is there something specific that was wrong that caused it to become unresponsive? (this is so I know in future for troubleshooting)

this was not anything you did, this was indeed an issue on our side

ahh ok, when you say application you're referring to Railway (not my application)?

kinda, its a bit complicated