upstream connect error or disconnect/reset before headers.
I'm getting this error on several of my Railway apps
16 Replies
Project ID:
02ef1ec0-5369-470a-a05b-43cab5190b5b02ef1ec0-5369-470a-a05b-43cab5190b5b
Requests aren't reaching the containers at all so it's definitely a platform issue
hello, same
It seems to be recovering now
@thomas - issue with the edge router
Looks like the issue started at 20:00GMT
is it recovering?
looks like this was caught by a rule and we had something that resolved itself
@sam what region was this?
We had an application refuse a massive amount of traffic which pushed it back into the edge
This got around our DDOS filter because it was retrying the connection (not new incoming)
We've escalated this internally
sorry about the delay, it was EU
it fully recovered by 20:20GMT.
I think this was the issue I was referring to above, we are actively working on making sure it doesn't happen again. Feel free to call it out if it does.
great, will do. :) thanks for your help
Hi @sam , It seems it is happens again, I have two applications with the same issue
Project Id: 8becd5a8-7a8b-412f-963c-68e28567a1da and e12ed2b1-36ad-49bb-889a-b3a17a8dfd39.
I don't see any incident reported in the #🚨｜incidents channel, are you aware of it?
Sam doesn't work for railway, but the team is aware
I can confirm it has been happening since +40 minutes ago, and its still happening right now... a few seconds ago
I thought it was an external party issue
looks like this has been resolved, closing out 