Anyway, one of our customers - representing a company in Germany I think - filed a bug report that said something like "Weather module hasn't updated since January". They'd been going to their fancy intranet home page and seeing the same weather for months at a time.

And this bug report just sat there. For a mixture of technical and political reasons, there seemed to be nobody in the European office able to pick up this report and do anything meaningful with it. We knew about it, we knew that what we were serving to paying customers was hopeless, but we somehow couldn't get our hooks into the right point in the Weather feed to figure out where it was going wrong. Or, collectively, we didn't care enough.

There were various technical and structural factors making it difficult to fix. Weather feeds were known to be problematic (still are I guess) and this code would have been surprisingly low-level C/C++ with custom serialisations and limited logging. Structurally there were problems in getting attention from a team in California to support a problem experienced by a different team in London, especially since it affected relatively few users - a tension in supporting paid products in a company that is focused on non-paying users at far greater scale.

(I am assuming this bug would have needed some actual development work - I don't recall, but I think we were familiar enough with common ops problems that it wasn't just a question of kicking one of our own feed servers.)

But I do think there was an issue about lack of concern - at heart we didn't have enough confidence in our own product to motivate the personal pain of working through these problems and getting them solved. I think that, if you had gathered us together and asked our collective opinion, we would have suggested that this customer would be better off not using our product at all - it simply wasn't ever likely to be good enough. Once you reach that way of thinking about your own product, it becomes extremely hard to countenance fixing the most difficult problems with it.

I've sent feedback and error reports about this repeatedly, and even had a friend that knows someone that works on Maps pass it on to them directly. It's never been fixed, and I've basically just given up on it at this point. It's really shown me how impossible it is to get any kind of support from Google for even an extremely obvious, straightforward issue.

In the end what worked for me was registering as google maps client/customer, reproducing the issue via API, and then reporting it as an API issue. The underlaying data was fixed within a day or two, and I got my emails answered by google engineer within (literally) minutes.

I recently moved, and found out that virtually every single web site from my credit cards to my bank to the library uses Google to verify address entry on the fly. The problem is that Google's database entry for my address is wrong. So any time I try to enter the address "123 Oak Street, Apartment Q" Google unhelpfully corrects it on the fly to "Oak Street, Suite 1." No amount of keyboard jockeying can override Google's on-the-fly autocorrection.

The solution I eventually came up with was to turn off javascript, then enter my correct address, then turn javascript back on to finish the rest of the form.

Of course, there's no way to contact Google about its error. Maybe in Google Maps? I dunno. How do you find an address that Google Maps doesn't know to tell it that the address it has is wrong?

(please do not take this as an endorsement of google maps support, merely an anecdote of what did work for me that I hope might help you)

With Apple, I've submitted perhaps 5 corrections for 5 different (usually minor) problems in 5 years. Problems like a place claims to take Apple Pay when it doesn't. Or the actual place is across the street from where Maps claims it is.

In each case, Apple sends back a notification within 2-3 weeks saying they've fixed the problem, and when I've checked, it has always been resolved. Pretty happy with the service.