Thanks, but links wouldn't be that helpful since the client-side code works just fine and the only sign of a server error is the message "Sorry we couldn't find that". The code and API key also hasn't changed so I thought people on this group might have run into the same general issue. Like tons of other developers we're using the Geokit plug-in for Rails, which handles sending the URL and parsing the response. Some other posts mentioned that Google might decide to start blocking keys or IP addresses, so I was hoping someone from Google might chime in on how to find out if that's the case here.
Thanks Dan On Oct 14, 5:24 pm, Gregory Short <[email protected]> wrote: > On Oct 14, 2009, at 3:59 PM, madfishmonger wrote: > > > > > We have a web site deployed on development machines, a test server, > > and a production server. All of them have been working fine for months > > until sometime this morning they all started getting back 610 errors > > from the geocoding service. Our client-side GMap2 code and maps still > > work fine, but the server-side http requests all fail now. We haven't > > changed the code or our keys, so how do I find out what's going on? We > > were supposed to go live today but this is blocking us. > > Have you double-checked your turboencabulator? > > Failing that, I suggest these two links: > > http://groups.google.com/group/Google-Maps-API/web/why-including-a-li...http://groups.google.com/group/google-maps-api/web/suggested-posting-... > > -G --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
