Limited number of connections

[JMGarc]

Hi,
I've made 4 requests and getting: "Too many requests, please try again later."

[djdmg]

Hello,

I have the same issue, i think the server is maybe overloaded.

Best regards
Dim

[Brian-Weloba]

Same here

[rezarahiminia]

2.500.000 request per match
Because the server is free, I cannot get a better server
2GB Ram server 1core cpu

[klevisndoka]

2.500.000 request per match Because the server is free, I cannot get a better server 2GB Ram server 1core cpu

@Raminmr totally understand that since the API is free, it is impossible to guarantee 100% uptime but at least would it be possible to limit requests per IP/per minute or per hour. I think this would reduce drastically the overload.

Unfortunately we can't help you with PR since your source code is not shared.
Hope you will find an workaround for this problem.

[avivbarniv]

2.500.000 request per match Because the server is free, I cannot get a better server 2GB Ram server 1core cpu

2,500 request per match per all users?
Im trying to get the bydate endpoint and also get 429

[arwinsf]

If it would be possible to secure more stable uptime, but have less requests per user, that everyone would agree and live with it. Something like 1000 requests per 30 min, but a lot better uptime or something

[rezarahiminia]

The number of requests for each ip 3000 in 15 minutes

[rezarahiminia]

During games, the number of requests on the server is very high.
8000 requests per second

[JMGarc]

8000 requests per second it's a lot. How many users in average are making requests per match

[MartinLodahl]

3000 requests per 15 minutes.

Is above 3 requests a second. (15*60 = 900)
If there's anyway you can rate limit drastically, it should make it more stable.

[MartinLodahl]

If it would be possible to secure more stable uptime, but have less requests per user, that everyone would agree and live with it. Something like 1000 requests per 30 min, but a lot better uptime or something

Do you even need 30 requests a minute?
Having a live score that's 30/60 seconds behind isn't insufficient for most usecases

[DrCuddless]

I get match and standing updates every 5 mins, one each. I feel like that is more than enough, why would need a second by second count? I understand wanting to have the latest information ASAP but this is a free api, give it some slack. Literally 100 requests per hour would be more than enough for me.

[arwinsf]

Same here. I would be okay with about 750-1000 requests per ip per hour instead of 3000. My use case is a chat bot, but even if it isn't, it's gonna be plenty of updates. Besides, I believe that this will gain more traction over time with more and more people using it, and I don't see stability improving from here when nothing gets adjusted.