too busy

[kgib91]

regardless of the specified user-agent, virtually every call is "too busy"; can we just pay for API that isn't going to be "too busy" virtually every time its called? out of the 5 coins I am monitoring, Helium is the only one failing constantly; If you do not want people aggregating real-time stats just let us know. Don't write a document telling people they can use the API.

I implemented a wait for "comeBackInMs" (which is not always present.) immediately after waiting, it says again "comeBackInMs" which an even longer timestamp and still no data. This is silly.

[madninja]

1. File against blockchain-http repo since ETL is not "the api but the backing store
2. There is an ongoing set of issues with the API taking too much load right now. I wish we could make the API none free to avoid the endless API span the api providers are seeing.
3. Ideally we wouldn't have a centralized api with as many features as it does today. Other coins don't have the same api features. Not making an excuse for the current state of the api
4. Yes there are paid API providers to hit with requests or direct SQL access for maximum access to data.

Totally agree the current state is far from ideal. If you're looking for short answers. Use a paid provider with sql access to avoid spamming APIs as badly as most scripts are doing today.

[federicorojas11]

I'm having the same issue... The API response sometimes gives 429 error, and sometimes 503... And sometimes work as expected. Hopefully this will work better in the future... The api is awesome anyway, I would love that it works properly