Comment Comment by jstastny Seems to be fixed now -- it has switched to different geocoding API. parent jstastny 5 years ago