6 months ago
https://thecaravanstorage.co.uk/ unable to access it. Railway dashboard seems fine
Accessing from UAE (Etisalat) if that helps.
curl https://thecaravanstorage.co.uk/ seems to work on my pc
but opening via browser doesn't..
Getting 408 timeout.. See screenshot
18 Replies
6 months ago
I'm seeing the same errors on our production servers
6 months ago
Multiple sites are down.. All requests to railway are timing out with 408.. & I have a client demo in like a few hours..
6 months ago
Their support is this. It's potentially not triggering their logging because normal http requests still work, it must be something with the browser
6 months ago
everything loads on my end <:Hmmmmm:891565000068587551>
6 months ago
Tried 4g as well. not loading. & also tried via a github codespace. Something is acting up
Very weird that curl to that link works..
6 months ago
If I VPN to canada, your site stops working. It might be something with DNS proxies
6 months ago
some of our services are offline too
6 months ago
experienced this yesterday, some of my dev services experiencing 408 after deployment.
6 months ago
I can't access your site https://thecaravanstorage.co.uk/ when I VPN to canada but it works if I access it from Australia
6 months ago
Interestingly my logs are showing 499 errors which is a nginx error
6 months ago
same, having issues on all *.railway.app
6 months ago
Will someone from @railway please stand up!?
6 months ago
i have 408 errors in the browser on mine after a redeploy with literally no changes to the frontend. (i just have frontend and backend in the same repo and have auto deploys from github) backend is fine (can make requests from postman)
frontend is killing me
isaiahbuilds
i have 408 errors in the browser on mine after a redeploy with literally no changes to the frontend. (i just have frontend and backend in the same repo and have auto deploys from github) backend is fine (can make requests from postman)frontend is killing me
6 months ago
after a few more redeploys its working again. i think they had an issue which they resolved.
5 months ago
!s
Status changed to Solved noahd • 6 months ago
