needs to be run in dev tools on localhost or a https website with location allowed

This occurs on Mac too.

I'm running:

OS Version: 10.11.6
Chrome version: Version 59.0.3071.115 (Official Build) (64-bit)

As described, usually occurs in the AEST afternoons (around 2-ish till 6-ish).

I get this same error on my production SSL site that uses a Lets Encrypt Certificate.  Also i get the error using a self signed certificate with chrome version 59-62.  Firefox, safari all work fine.

Did a bit of digging.  It appears the API key limit was exceeded (presumably there's one embedded in Google Chrome).

{
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "dailyLimitExceeded",
    "message": "This API requires billing to be enabled on the project. Visit https://console.developers.google.com/billing?project=77185425430 to enable billing.",
    "extendedHelp": "https://console.developers.google.com/billing?project=77185425430"
   }
  ],
  "code": 403,
  "message": "This API requires billing to be enabled on the project. Visit https://console.developers.google.com/billing?project=77185425430 to enable billing."
 }
}

Can confirm that this is related to Chrome's internal api key used for google maps geo location running out of daily quota.  The issue stopped occurring at 12 am PST.  Please fix this.

https://www.chromium.org/developers/how-tos/api-keys

Thank you for reporting. We have adjusted API limits that should ease this immediately. Our monitoring is clearly not sufficient and we will follow up with process improvements to avoid this recurring.

Started getting this a couple of days ago on Chromium/Ubuntu. Other browsers work fine.

I've been using the machine to develop software that uses Google Maps API. reinstalled the whole os and it worked again for a short while now failing again.

The internal API key runnig out of quota seems logical to my behaviour.

Quick fix or a workaround would be great!

Version 60.0.3112.78 (Developer Build) Built on Ubuntu , running on Ubuntu 17.04 (64-bit)

#11, thank you for reporting this again.  I've looked and do see UMA reporting errors roughly a week after #9.  So, we will be looking again at this issue.

However, this issue is about Chrome's API keys (not chromium), so I want to be clear on expectations.

daily and 100second quota were adjusted. 

 Issue 814100  has been merged into this issue.

this is happening again, but only in Canary in the afternoon in Australia, the error message is different, just reports a timeout

pkasting@, could you take a look please?

before you fix this, it's a good way to reproduce https://bugs.chromium.org/p/chromium/issues/detail?id=542923

I reported the latest problem with Canary timing out back on Feb 22, it's still happening

@18: Not sure why I'm looped in here; I don't know anything about geolocation or quotas.

Geolocation is now timing out in Chrome Stable 65.0.3325.146, try google maps on the web

In a development website with HTTPS I always get that error.

Geolocation error: Network location provider at 'https://www.googleapis.com/' : Returned error code 403

Chrome: Version 71.0.3578.98 (Official Build) (64-bit)
OS: MacOS

ERROR
{code: 2, message: "Network location provider at 'https://www.googleapis.com/' : No response received."}

Using https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API jsFiddle example, works in Firefox.