Just as I was going to reply, I decided I better double check that we're not doing any other API calls on our site. As it turns out, a new feature was just released that was flooding Google with requests.. Damn rookie developers. :)
So, problem addressed by re-engineering that feature. Thanks all for the help! On May 7, 2:11 am, Rossko <[email protected]> wrote: > > So to address this, we > > switched the lookup to be done via javascript (i.e. coming from the > > registrant's IP address) to limit the # of requests coming from our > > servers. We continued to use our registered API key on these > > requests. > > And, does that work ? > > > Also, some of our requests are going through, but the % > > that are being accepted has dropped around 80%. > > Is that from server(s) or client? Your key can't be 80% acceptable so > we can rule that out. It does sound like a rate issue, but you've > given us no idea what sort of rate and volume you are handling. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps API" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-maps-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
