Hi there, we have contacted Starlink and according to their employees, they have engaged in talks with Google and are working on resolving this blocking issue. It should be fixed within a few days.

Trust me, we are taking this seriously, I almost fell out of the window trying to set up Starlink in our office for testing, but, unfortunately, we are on a different ground station than you guys, so, to our dismay, Windy worked without any problems on it.

Due to on our partner's discontinuation of data provisioning we are receiving no radar data for Mainland China and some parts of India. We are working on fixing this issue, but we currently have no timeframe for its resolution.

We are very sorry for any inconvenience this is causing you.

If you read the discussions here, radar "forecasting" is a very controversial feature. That's due to it not really being a forecast. Instead, it's just an extrapolation, where we take the current images from a radar, calculate the movement vectors of different features and show how the situation could look if the features kept moving in the same direction and at the same speed during the next hour.

However - it will not show new phenomena that could emerge and it assumes that they will not disappear. It's a feature that is really popular in some regions, where it is a good predictor of rain or thunderstorms which are coming in the next hour. However, in other regions, with different geography, it can be less useful. For example, it's good for people who live in a single spot and know how storms tend to behave as they approach from different directions. However, without this local knowledge, you really cannot rely on it even within a 1h timeframe. A 3 hour radar extrapolation would basically be complete fiction.

Hi, as for ECMWF, the 1800Z forecast was imported pretty much on time. The 0000Z forecast is expected to be available at the standard time of about 8:00 UTC. As for the Australian radar, we will take a look, thanks for bringing it to our attention!

Hello, we have just released version 51 in which premium users can pick their default forecast model for point forecast. For now, it's only available on our web application, but we expect that next week, this version should roll out to mobile apps too.

Instead of map layers, some users of our Maps Forecast API might see fallback tiles with "No Data" text on them. We have identified the source of the issue and are working on fixing it.

We are on the path to fetching Chinese radar data from another source. It should be done within at most a few days, hopefully it could be in the next 24 hours.

We have received the 06Z forecast and it is available via our website and apps. We are currently waiting for the 12Z forecast and we will see how the situation will normalize on ECMWF's side

@Aleksei-Iakovlev Hey there :) Unfortunately, we primarily use Google Cloud and their CDN to host Windy. I think you could find their IP ranges somewhere, but it would be very dynamic and there would be a lot of them, so it's not a sustainable solution.

As for domain mask, I'm not 100% sure if I understand what you're referring to, but allowing windy.com and all its subdomains should be enough, we don't use 3rd party partners or tracking within our apps or website. If you need a list of subdomains, I'm afraid I wouldn't be able to provide them, since we do reserve the right to move our services around and frequently do precisely that.

@S-G-17 Hi, yes, unfortunately, our maps are based on quite old OpenStreetMaps labels. We have an ongoing update project, we hope that within a few months it should be done and the labels should reflect current OpenStreetMap data.

Hello, this is unfortunately related to China's Great Firewall, which blocks the IPs of our provider. We used to have a workaround implemented for Chinese users, but due to extreme amounts of abuse it has received in the past few months and the large amount of work it took to maintain it, we had to make the difficult decision to discontinue it. Especially after our tests showed that only some Chinese users could access Windy through it anyway, since some providers or provinces already blocked even this workaround. We are very sorry about that. For now, the only thing we can recommend is using a VPN.

Hello, this is unfortunately related to China's Great Firewall, which blocks the IPs of our provider. We used to have a workaround implemented for Chinese users, but due to extreme amounts of abuse it has received in the past few months and the large amount of work it took to maintain it, we had to make the difficult decision to discontinue it. Especially after our tests showed that only some Chinese users could access Windy through it anyway, since some providers or provinces already blocked even this workaround. We are very sorry about that. For now, the only thing we can recommend is using a VPN.

Hello, just to check - in "Settings for location forecast," did you also switch the tiny toggle that's to the left of the "Always open as" setting? It needs to be switched on so that your settings are respected. With the toggle enabled (white background) it works for me.

Screenshot 2026-08-10 at 10.38.41

@admin1031 Hi, yes, we try to let our Chinese users to access Windy.com even though there are some restrictions on Chinese government's side. That means that access from China is unfortunately much slower than we'd like it to be. VPNs should make it faster, as long as their exit nodes are (obviously) outside of the PRC.

Hello, we have just released version 51 in which premium users can pick their default forecast model for point forecast. For now, it's only available on our web application, but we expect that next week, this version should roll out to mobile apps too.

@Aleksei-Iakovlev Hey there :) Unfortunately, we primarily use Google Cloud and their CDN to host Windy. I think you could find their IP ranges somewhere, but it would be very dynamic and there would be a lot of them, so it's not a sustainable solution.

As for domain mask, I'm not 100% sure if I understand what you're referring to, but allowing windy.com and all its subdomains should be enough, we don't use 3rd party partners or tracking within our apps or website. If you need a list of subdomains, I'm afraid I wouldn't be able to provide them, since we do reserve the right to move our services around and frequently do precisely that.

Hello, you had a typo in the email domain, but I found your account and logged it out from everywhere

We have received the 06Z forecast and it is available via our website and apps. We are currently waiting for the 12Z forecast and we will see how the situation will normalize on ECMWF's side

Due to power issues in ECMWF, he we have not received the 2026-06-28T0600Z reftime. Thus, ECMWF forecasts are working from slightly outdated data. We are sorry for the issue, but there is nothing we can do about it.

Once the reftime is published, we will import it ASAP. Current ECMWF status is available at https://status.ecmwf.int/

Hi, if I might offer a suggestion - Windy's sister company, Meteoblue, does offer an API for historical forecast and observation data going all the way to 1940. It's available here - https://www.meteoblue.com/en/historyplus. However, the service is paid. Even a single run of ECMWF is quite large (in the terabyte range). Due to that, storing historical data gets very expensive, very fast.