IssueTracker

Thanks for your suggestion! We are currently evaluating this request, but do not have any plans to implement it at the moment. Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.

One nice way to handle this would be to return the current count with the response. "OVER_QUERY_LIMIT" can be a couple things. Either over the QPS limit, or over the daily limit. If the response actually told me where I was at for the day it would be extremely valuable. You are keeping track of it so just give it to us with each response. Thx.

Although the initial request was for Geocoding API I think it should be extended for all Maps APIs.

From 11460:

Part of producing a useful map is providing a good user experience.  To the best of my knowledge, there is currently no way for javascript to detect when the 25,000 API loads per day limit is reached and the map stops working.

Here is my stack overflow post on this issue.
http://stackoverflow.com/questions/42228701/how-can-my-code-detect-when-google-map-25-000-api-load-limit-is-reached

I wish to provide a 'least bad' experience for my users by displaying a message telling them why the map stopped working if my map hits this limit.

Others have asked the same question on SO.

Google might have provided a partial solution.  Here is a page that Google apparently posted in June 2017.  
See https://developers.google.com/maps/documentation/javascript/error-messages

The page lists various error messages including OverQuotaMapError.  

If you scroll to the bottom of the page there is a link with advice for how to catch "authentication" errors with your javascript.

+1
StackOverflow: https://stackoverflow.com/questions/46185596/googles-geocode-api-get-remaining-quota-balance

+1
StackOverflow: https://stackoverflow.com/questions/46290759/google-maps-geocoding-api-usage-limit

Would it be possible to get a list of all remaining API quotas from an endpoint?  Just a simple JSON/XML response of api-name: #remaining

Here is a Google + GIS wildland fire map I produced.  Due to all the CA fires this map has got a ton of hits on social media and my IP address hit the 25,000 limit around 6pm Pacific time yesterday and today.

https://mappingsupport.com/p/gmap4.php?ll=38.427302,-122.450782&z=10&t=h,VIIRS_fire_detection,MODIS_from_GeoMAC&q=https://propertylinemaps.com/p/public_land_map/USA/USA_wildland_fire_3.txt

Initially  the map opens and few seconds later the map goes away and the screen displays:

"Oops! Something went wrong.
This page didn't load Google Maps correctly. See the JavaScript console for technical details."

When my users - many of whom have been evacuated from their home - see that message they have no clue what it means.  

Google - listen up!!!  That is an absolutely terrible user experience.   It cannot be impossible for you to give us a simple way to fail gracefully with our own error message when we hit the 25,000 wall.

Sorry for the inconvenience but our free tier has no way to inform you when you are getting close to the limit. Once you enable billing, you can set budget alerts.

OK.  If it impossible to to give us a way so our apps can detect when the 25,000 limit is getting close, is it possible for google to give our apps a way to detect when the 25,000 is actually reached so our apps can fail gracefully by displaying our own error message?

I did enable billing on my account and my users quickly chipped in $ so my wildland fire map will keep working.  However I would still like to know the answer to the question I posed above.

Seems like I'm not the only one, who needs a programmatical way of checking quotas (in my case geocoding). Until now there is no solution for this. My alternative solution is:

1) use another geocoding api without limitations
2) if 1)  does not find a result then use Google Maps geocoding service

Regarding 1) I'm planning to use Gisgraphy with OpenStreetMap

+1 StackOverflow:
https://stackoverflow.com/questions/50801501/how-can-i-get-my-current-quota-usage-in-google-programmatically-in-java

This is nuts.. this problem is only going to get worse as you make payment a requirement at the end of this month.

Why can't you just fire an event at, say 80% quota, and 100% quota so we can fail gracefully? Seems making Google Maps a pay service was not well thought out.

Leaflet... here we come.

@Al..., it was perfectly thought out.  If the end user has no way of knowing programmatically if they're over their quota till they get the bill, then Google's found a quick and dirty way to get paid.