Hi Korina, we need to be able to defend the rest our site when it does happen again. There must be some way we can identify it and do something else?

Hi Korina,

With the Windy Auth API offline it caused catastrophic issues to our application, basically making it totally unusable. We need to be able to handle this so if it happens again our web app can continue to work, but without Windy.

Could your developers please let us know how best to identify if the Auth API is not working (the same as yesterday) so that we can put in some defensive code?

Thanks

Euan

Even though this has been resolved, it would be useful to acknowledge that the AUTH was unavailable this morning. It might help others with any support cases that came in.:

This morning between around 11am GMT and 11:37 the Windy API Auth went offline.

https://api.windy.com/api/map-forecast/v2/auth

In Chrome browsers this was visible in the console as:
Access to XMLHttpRequest at 'https://api.windy.com/api/map-forecast/v2/auth' from origin X has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

In FireFox:

In Fiddler, it was shown as:
The server encountered a temporary error and could not complete your request.Please try again in 30 seconds.

At 11:37 GMT the Auth began working again.