I’m receiving the following error from the address lookup service I’m using: “The remote server returned an error: (509) Bandwidth Limit Exceeded.” Two days have passed and there’s been no change. I can get a response from the browser on the same computer, but unfortunately I’m getting the error from the application. Do you have any ideas?
We are having issues with massive abusers of the API and experimenting with measures to get them under control. You might have been temporarily caught up in this. Should be better by now.
In any case: please make sure to read and and follow the TOS and use our services with care and consideration. In particular, if you plan to put an app out there you want to make money with, use a commercial geocoding alternative or host yourself. Thank you.
Hi there. I am also experiencing this issue. I had assumed it must have been because something went wrong with the code I use to rate limit. I have been using Nominatim for a few years and have always tried to take care to comply with the rate limit. I am glad to hear that it’s possible I was not blocked through my own fault. I would also be grateful for any subsequent updates on this. Thank you.
If you want to use Nominatim in an app, it’s really easy to set up your own copy rather than use the OSMF’s “free” one. I needed to do that for some testing I was doing that resulted in a diary entry, and didn’t need to comment on the Nominatim installation itself because what was documented “just worked”.
Well, if you still have issues, then you need to supply a bit more information then “it’s not working”. At a minimum we’d need: kind of requests you are sending, referrer, user agent. Also: where the requests are coming from and how many requests you usually send and when was the last time you had a successful request gone through.
Make sure you can really answer these questions. For example, I can’t find the query pattern of the original post anywhere in the logs.
NB: we’ve just lifted restrictions some more. Please try again before posting here.
Just for the record both the Nominatim and Photon instances used by Vespucci to provide (manual) search are fully configurable Advanced preferences - Vespucci
Reverse geocoding worked flawlessly for a week after our last correspondence. However, for the past day, despite significantly reducing the number of queries (less than 5 per minute), I’ve been receiving the error “System.Net.WebException: Remote server returned an error: (403) Forbidden”. I would appreciate your support regarding this issue.