Is https://www.google.com/jsapi down for maintence

[viper1884]

I noticed about 2 hours or so that my Google charts are no longer loading correctly, when i enter https://www.google.com/jsapi into my browser i sometimes get Server error, error code 502 bad gateway and chrome is showing the same errors when i'm debugging.

I assume its down for maintenance which is fine, but can someone confirm this?

also since its down i'm trying an event handler by doing 

var s = document.createElement('script');

s.setAttribute('src', 'https://www.google.com/jsapi');

s.setAttribute('type', 'text/javascript');

s.addEventListener('error', googleLoadError, false);

document.head.appendChild(s);

function googleLoadError() {

    var Message = "";

}

Is there a way to find the error code from the external script ?

[Mitchell Foley]

There is currently an outage, and it's being worked on right now.

-Mitch

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.
To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.

[Arshad Ahmadi]

We are seeing the exact same thing as well.
Mitch,
is there a web page that provides the status of this service?
Thanks,
Arshad

[viper1884]

Thanks for the quick update

[Jon Orwant]

There's no web page providing the status, but this outage is affecting multiple Google APIs (not just Google Charts), so expect this to be fixed very soon.

Jon

--

[Dan Denkijin]

This is happening to me right now, that is, google.com/jsapi is down, 502 error

On Tuesday, October 1, 2013 at 3:40:29 PM UTC-4, orw...@google.com wrote:

There's no web page providing the status, but this outage is affecting multiple Google APIs (not just Google Charts), so expect this to be fixed very soon.

Jon

On Tue, Oct 1, 2013 at 3:26 PM, Arshad Ahmadi <arsh...@gmail.com> wrote:

We are seeing the exact same thing as well.
Mitch,
is there a web page that provides the status of this service?
Thanks,
Arshad

On Tuesday, October 1, 2013 2:59:39 PM UTC-4, viper1884 wrote:

I noticed about 2 hours or so that my Google charts are no longer loading correctly, when i enter https://www.google.com/jsapi into my browser i sometimes get Server error, error code 502 bad gateway and chrome is showing the same errors when i'm debugging.

I assume its down for maintenance which is fine, but can someone confirm this?

also since its down i'm trying an event handler by doing 

var s = document.createElement('script');

s.setAttribute('src', 'https://www.google.com/jsapi');

s.setAttribute('type', 'text/javascript');

s.addEventListener('error', googleLoadError, false);

document.head.appendChild(s);

function googleLoadError() {

    var Message = "";

}

Is there a way to find the error code from the external script ?

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsub...@googlegroups.com.

[Rimon Erez]

Same Here!

[Ralf K]

Same here. At the same time I just restructured/rewrote my charts and was desperately trying to figure out what I did wrong ^^

[Brian Shreve]

I am having the same issue.  All of a sudden my site broke.  502 error.  I did not make any changes to the current code.

[Thomas P.]

Same here. No idea!  Any suggestions?

[Timothy Weidner]

I am seeing the same, sad that it's happening, but glad I'm not alone.

[Rowan Hale]

Same here, resulting in 502.

[Brian Shreve]

Well I dont think we all made a coding mistake at the same time, so I guess we wait? 

[Myhedin Zika]

Glad I'm not the only one having this problem lol :P 

[Bryan Swang]

We are in the process of upgrading to use https://www.gstatic.com/charts/loader.js since the rug was pulled out from the JSAPI link we were using

[Paul Rossmann]

Same!!!

On Thursday, January 31, 2019 at 4:17:18 PM UTC-5, Dan Denkijin wrote:

[caseym]

Are people seeing this issue using the current loading code?  We just updated ours and things seem to be working:

https://developers.google.com/chart/interactive/docs/basic_load_libs

[Nikhil Desai]

We have an app in production, which is affected by this problem. Is there anyone we can contact for support?

[Myhedin Zika]

    <script type="text/javascript" src="https://www.gstatic.com/charts/loader.js"></script>

I replaced it with this one, it works okay for me now

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.

To post to this group, send email to google-visua...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-visualization-api.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-visualizati...@googlegroups.com.

To post to this group, send email to google-visua...@googlegroups.com.

Visit this group at https://groups.google.com/group/google-visualization-api.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-visualization-api/42c99486-083c-4b2f-b185-af83405ffd72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bryan Swang]

This is working for me but causing me to unexpectedly update a lot of stuff I wasn't planning. 

[JENNIFER WOODSON]

I am also using this code, and my charts are displaying as expected; no errors.

[Prince 100]

If anyone out there is using an old version of ng-google-chart, here is how you can fix this:

• Download the latest build here: https://github.com/angular-google-chart/angular-google-chart
• Add this to your angular config:

angular.module('myapp', ['googlechart'])
  .config(function(agcLibraryLoaderProvider){
    // options: 'jsapi', 'gstatic', 'null' (not the value, the string 'null').
    agcLibraryLoaderProvider.setLoader("gstatic");
  })

[JENNIFER WOODSON]

From Daniel LaLiberte on a different thread (bold is mine):

Since 2015, we started releasing new versions of Google Charts on a new server, and the old server has remained static ever since then.  However, the old server will be turned off entirely at the end of this quarter, so that means everyone using any versions on the old server will be forced to migrate to the new server.

Fortunately, we will be able to automatically redirect all requests to the new server, which means that all versions of Google Charts that have been loaded via the jsapi loader will effectively be automatically updated to the current version, which is v46.

So you won't have to make any changes to your code to be affected by this update, but you may need to update how you are using Google Charts due to differences in the versions, or you may select one of the other versions that are available.  

You can check how your charts will appear once this update occurs by following the instructions on how to update your loader at:   https://developers.google.com/chart/interactive/docs/basic_load_libs#update-library-loader-code

The last version released to the server where jsapi loads from was v41, and the same version (or nearly so) was also frozen on the new server.   It might be best to try that version, if v46 is not working for you.  Other versions you can use on the new server are 42, 43, 44, 45, 45.1, 45.2, and 46.  You can review all the changes in each subsequent version at:  https://developers.google.com/chart/interactive/docs/release_notes#february-23-2015

Also, in preparation for this turndown of the old server, there will be short periods of outages, maybe up to a few hours, during which the UDS server is "drained" of all requests to determine if there are any further unknowns.  You may have noticed one already.   You can avoid these outages by updating to the new loader, as linked to above.

-- 

Daniel LaLiberte

[Thomas P.]

seems to be fixed :)

[Kraig Hufstedler]

Back up here too. Do we need to stop using the /jsapi url or will it be redirected in the future?

On Tuesday, October 1, 2013 at 1:59:39 PM UTC-5, viper1884 wrote: