22 days ago
Hi team, our Binance API requests intermittently receive "HTTP 418 IP bans" on Railway. All three static outbound IPs are Shared.
Our services made only 29 read requests that day, and the failed job was blocked on its first request. We suspect other traffic sharing the IPs?
How can we identify the affected IP? Does Railway offer exclusive outbound IPs, or would we need a dedicated gateway?
2 Replies
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Binance blocks Railway IP addresses, and those restrictions are controlled entirely by Binance. Changes on Railway won't resolve it, so please contact Binance support about the block and their access requirements.
We don't offer dedicated (unshared) outbound IPs on any plan. Static Outbound IPs are shared by design, and we can't attribute the traffic behind a given address.
Status changed to Awaiting User Response Railway • 22 days ago
brody
Binance blocks Railway IP addresses, and those restrictions are controlled entirely by Binance. Changes on Railway won't resolve it, so please contact Binance support about the block and their access requirements. We don't offer dedicated (unshared) outbound IPs on any plan. Static Outbound IPs are shared by design, and we can't attribute the traffic behind a given address.
22 days ago
Okay. Thanks!
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Solved Railway • 22 days ago