TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: We screwed up with the Google Maps API and now have a significant bill

18 pointsby griffoaabout 4 years ago
We recently found that requests using our Google Maps API key was blocked by Google due to an unpaid bill, so we now owe Google $20.000.<p>What happened was that at some time around the end of 2019 the credit card expired and nobody noticed it. The API just kept on working for our services, so we assumed everything was fine and we were probably within the free tier. The card was added and account configured by someone not working on the project anymore.<p>Then recently the service just stopped working and after a bit of digging around, we found that the account had racked up a bill of $20.000 since the end of 2019. Slowly and steady each month. It was nice enough of Google to give us quite the credit period there, but as it turns out after inspecting the cost breakdown, someone else must have been using the key since a lot of the requests were to API endpoints totally unrelated to the services we provide.<p>We screwed up big time by having an unrestricted key configured. It was setup in 2017 way back when things were free, so I doubt anybody actually thought about abuse of the key at that time, but none the less, here we are having our key abused.<p>Do we even have a chance here? Did anyone get into a similar situation? I would be grateful for a little bit of advice about how to approach Google. I realize this is our fault, but at the same time, it seems we never got any payment reminders or notifications that we had bills overdue - at least we cannot find them anywhere.

9 comments

core-questionsabout 4 years ago
Time to get a lawyer, pore through the terms of service, etc.<p>A broken &#x2F; blocked key should not result in this happening. It&#x27;s a failure of the software. You should also be able to get the IPs that your account was connecting from, and disavow those that are not yours.<p>Divest yourself from Google and don&#x27;t pay the bill if there&#x27;s any way out of it.
评论 #26442694 未加载
ubermanabout 4 years ago
I&#x27;m sorry this happened to you. Many people were shocked at their map api bill following google making it a paid service. We certainly did and now we don&#x27;t use them any more.
评论 #26440452 未加载
ancymonabout 4 years ago
I&#x27;ve had unintentional usage for few hundreds dollars. After explaining the situation and setting API limits the bill was cancelled. Your situation seems a bit different. But maybe explaining the situation and asking for help first is the best option.
pkrotichabout 4 years ago
Initially, I was like $20 is not significant- then I realized it’s $20k. That’s a lot of overdue bills without service getting disabled.<p>I would negotiate for reduction based on the fact that you didn’t get any notifications.
spaceflunkyabout 4 years ago
I used to work on the Google Maps API.<p>I can help. How can i get in touch with you?
评论 #26444317 未加载
评论 #26444271 未加载
andrefuchsabout 4 years ago
Find out who used your key without permission and make them pay their share of the bill.
brudgersabout 4 years ago
Why can’t the business pay the bill?
ttfxxccabout 4 years ago
It&#x27;s way cheap to just use the unofficial api with proxies and caching.
olivierduvalabout 4 years ago
It&#x27;s sad for you and I hope that you will find a way to manage this problem with Google...<p>However, I&#x27;m quite shocked when you write &quot;when things were free, so I doubt anybody actually thought about abuse of the key at that time&quot; It look like - for you - having something free mean having something you can use without any care! From my point of view, if someone give me something for nothing, I will thank and try to use it wisely... But maybe I didn&#x27;t understand what you meant
评论 #26444142 未加载
评论 #26447693 未加载