Hi Freddy,

First, you need to know what error requests you are making. To do that, you should turn on full logging for a few minutes. That will show you every request in the logs that you are making. Then you can browse the FAQ area for explanations (if not obvious) of why a request is considered broken/bad. In that case, you should mark it on your side to not try again OR if it is good, to refresh it once or twice (because there are rare instances where we cannot capture a working site/page).

Yes, you are most likely using the embedded method (not advanced API), if you followed one of the guides for integrating with phpLD. Unfortunately, there is no easy way in this case to curb/limit bad requests or too many fetches (as it won't cache locally).

We tried for a very long time to get phpLD to integrate our service with their script but they are planning to launch their own service and haven't really taken our request seriously. So the functionality there is limited for now. Ideally, we would like to find someone qualified enough to write a fully functional module to integrate our service with caching, pro features, etc. That is a goal of ours for this year.

That said, however, by turning on full logging; you may discover a fixable reason you are making too many requests. If it is because of traffic, then that's great because you should be monetizing that traffic. But if it is because of some cron job or broken script, then perhaps it can be corrected.