title: Different errors (quota, disabled, bad API key, or none) when loading Google Maps API JavaScript
body: <p>We ported our site to Google maps, but we get different errors when loading a map using the JavaScript Maps API (v3 of course). Other times the map loads correctly. The two most prominent errors are:</p>
  
  <blockquote>
    <p>"Google has disabled use of the Maps API for this application. See the
    Terms of Service for more information
    <a href="http://www.google.com/intl/en_US/help/terms_maps.html" rel="nofollow">http://www.google.com/intl/en_US/help/terms_maps.html</a>." (JS Alert)</p>
  </blockquote>
  
  <p>And:</p>
  
  <blockquote>
    <p>"This site has exceeded its daily quota for maps. If you are the
    creator of this site, please visit the documentation to learn more."
    (this is a DOM overlay)</p>
  </blockquote>
  
  <p><strong>Live minimal example</strong>: 
  This code is not yet live but there's a minimal example here: <a href="http://mappat.com/maptest.php" rel="nofollow">http://mappat.com/maptest.php</a>. It is simply Google's own Hello World example with our key filled in and even that gives problems.</p>
  
  <p><strong>Network traffic inspection</strong>: 
  I noticed the first error is shown when 'AuthenticationService.Authenticate' fails (returns [0,5,0]), the second when 'QuotaService.recordEvent' returns [0,null,0]. These are remote calls from within the SDK and I don't know if these details are relevant.</p>
  
  <p><strong>What we tried</strong>: 
  Billing is enabled by the way and we stay way below our quota limits. I tried a lot of things already, new key, waiting a  few days, turning the Maps API off and on again in the console, etc. I filled in the allowed referrers but also left it open to allow others. No difference.</p>
  
  <p>I don't dare to start a new project in de dev console because this whole thing started when I did actually just that because I had (different) problems with the server-key. That server part is now working flawlessly btw, kind of ironically. </p>
  
  <p>[<strong>Edit</strong>: I just tried to leave out the API key when loading the JS maps file, which, fingers crossed, seems to work. But now the server-side calls to places/searchtext start to give random "The provided API key is expired." errors, again (same reason we created the new project). Coincidence? Also, I don't like this option, especially with regards to the future (reaching 25k, going beyond and going Business Account)].</p>
  
  <p>So, I'm stuck. Hence my first SO question ever. Could it be that we are blacklisted? Perhaps because of the duplicate project? Is there a way to find that out and/or to get us 'reset'? Or am I simply overlooking something? </p>
  
  <p>Any help is appreciated because until we solve this, this is a deal-breaker.</p>
  
  <p><strong>Sidenote</strong>: I also filed a <a href="https://code.google.com/p/gmaps-api-issues/issues/detail?id=6756&amp;q=apitype%3aJavascript3%20type%3aDefect%20key&amp;sort=-stars&amp;colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Internal%20Stars%20Project%20Apitype" rel="nofollow">bug report</a> because I think giving random errors on itself is not expected behaviour. It's up to the dev team to decide if they agree. If not, we still have a problem, hence this SO question.</p>