14 days ago
for some reason since the last 15 minutes MongoDB doesnt respond anymore, tried restarting it but nothing works, anyone has the same issue or know how to solve this ?
11 Replies
14 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
14 days ago
this started a few minutes after 19:00 while nothing changed on my side
14 days ago
it looks like after you updated the usage of Memory + CPU trippled on all instances
14 days ago
We've had an incident today that has caused sporadic timeouts (https://status.railway.com/cmltkyu8905sl13amlju6j5yh) - are you still seeing issues? If so, please provide a link to your service and we can investigate further.
Status changed to Awaiting User Response Railway • 14 days ago
14 days ago
Yes still having issues, link to my service: https://railway.com/project/66f300b3-397e-4083-a248-83e77ed36fdc?environmentId=25f338c8-b4d1-4814-a166-f2799805cfb6
i can share some screenshots if needed as well , i tried restarting / redeploying mongoDB but it seems to immediately start using heavy CPU + memory compared to before
Status changed to Awaiting Railway Response Railway • 14 days ago
14 days ago
I cannot connect to any of my Postgres DBs
johndavi
I cannot connect to any of my Postgres DBs
14 days ago
"Hostname not found" -- this is ridiculous at this point the past three days
sam-a
We've had an incident today that has caused sporadic timeouts (https://status.railway.com/cmltkyu8905sl13amlju6j5yh) - are you still seeing issues? If so, please provide a link to your service and we can investigate further.
14 days ago
please let me know if you have found anything as of yet
14 days ago
We just fixed it for you but for some who were also seeing impact. Apologies, we had an incident affecting the TCP proxy and edge network that caused connection timeouts - this is now resolved as of 21:19 UTC.
We also ack the last set of impact, it was an intermittent DDoS, to summarize we had SYN attacks to some workloads. You may have had Cloudflare in front of your app, however, non WAF workloads could have affected the availability. As such we have implemented short terms measures to prevent this moving forward. Since then we've expanded interconnect capacity with new peering and Direct Connect, deployed per-container eBPF firewalls, hardened our edge, and built continuous connectivity monitoring between hosts. We're also rolling out a WAF for all customers, edge-level protection against malicious request patterns across all plans.
Status changed to Awaiting User Response Railway • 14 days ago
13 days ago
Got it thanks alot appreciate the help!
Status changed to Awaiting Railway Response Railway • 13 days ago
Status changed to Solved sam-a • 13 days ago