a month ago
Hi, we haven't made any code changes that would case this error for requests, almost all requests are returning 499. What should I do? Is there something down?
5 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 30 days ago
a month ago
Seems to have started working again
andremaytorena
Seems to have started working again
a month ago
The 499 error is a timeout issue. Probably just needed to close out and reopen
andremaytorena
a month ago
Hey — quick question before I dig.
What’s this running on — Railway, or something else? And what’s the stack on the server (Node, whatever)? Want to make sure it lines up before I say something useful.
andremaytorena
Seems to have started working again
a month ago
Glad it’s working again.
For next time — what I do on my Railway apps so this doesn’t blindside me:
- When half the UI dies, check if any routes still 200 fast. If yes, it’s hung paths (→ 499), not “Railway is fully down.”
- Hit one slow route and watch deploy logs live — silent app vs slow DB/auth tells you where to dig.
- Keep a cheap
/healthz(or similar) and poke it when users scream. Fast health + slow/auth= auth/DB, not the whole box. - Note region + any Cloudflare/proxy so you’re not guessing hops.
That’s the playbook I use. Stack details help if you want something more specific to your setup.