11 Replies
Project ID:
b0a7355b-b496-444f-bee2-d750f2625a71b0a7355b-b496-444f-bee2-d750f2625a71
please provide more info, what kind of site is this? what is your tech stack? etc?
My website is made in nextjs, it's back to normal, but I've been researching and apparently it's a container error. I was afraid that it was some kind of attack that my website might be receiving, or if it was a problem with the railway server
railway issue
same here. kinda urgent
team has been notified
team is looking into it
Seeing this issue too
seeing this issue as well, also a nextjs site
We isolated the issue to resource exhaustion on some us-east proxies. We've retroactively created an incident with this context.
Basically AWS SNS started hammering our proxies with a large number of connections solely in that region and it exhausted connections. We've shipped a mitigation, and also are adding more capacity to that region.
Traffic ingested from other edges (us-west/europe/asia) were unaffected.
https://railway.instatus.com/cln27mrdl75373bbofzz3mh17l
thank you for your fast feedback and transparency! good luck on this