(503) Server Unavailable. This distribution exceeded the limit on requests per second.

I am always well below the Binance IP limit and when I surpass it I receive a different type of error. Also, I am not restarting the EC2 instance and I am not getting a new IP, just restarting my bot application gets rid of the issue, that's weird I've been trying to troubleshoot this for weeks. Issue is very similar to this one. https://stackoverflow.com/questions/75153460/how-do-i-fix-this-invalid-json-error-message-from-binance

This is not something you can control on your side. As the error message says you need to reach out to the app owner in this case Binance so they can address the issue of exceeding requests per second on their distribution or direct you to another endpoint. an except from "https://github.com/binance/binance-spot-api-docs/blob/master/rest-api.md" appears to show they have multiple endpoints that each have their own infrastructure behind them, so if one endpoints generates the error, you may be able to try another endpoint. Perhaps the behavior you are seeing is from a fresh dns resolution that resolves to a different distribution that isn't experiencing congestion, but that is just speculation. "The following base endpoints are available:

https://api.binance.com
https://api1.binance.com
https://api2.binance.com
https://api3.binance.com
https://api4.binance.com

All endpoints are equal in functionality. Performance may vary between the base endpoints and can be freely switched between them to find which one works best for one's setup."

The issue I am having is related to the only futures trading endpoint they provide https://fapi.binance.com.

The thing that seems very weird to me is that I can get rid of the issue simply by closing and re opening my application, that is why I believe the problem is on my side.

It would be very useful to know a little bit more about this type of error, what does it mean and when does it trigger. I could find very little information online